-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HttpClient timeout (proxy firewall) -> locked database #293
Comments
@dizzzz Is this still a problem? |
yes ; during startup still 'something' makes a HTTP request.... |
actually... it is during database start... not shutdown ; I am wondering why I wrote this... |
So we could easily trace this with Wireshark, no? |
yes, that should be rather easy. somehow i never did it :-/ |
here it is:
response
I fear that one of these try to resolve the external URL instead of resolving it locally: monex
usermanager
exide
in the logs:
|
@dizzzz Okay, so er... it is a problem with an App? |
Looks like it.... |
Removing the |
Okay but that isn't the cause |
sure ; there is an ordering issue, where the console extension is not yet available when the RestXQtrigger is being initialised. Potential solution: move the console-extension into the exist-db core. @wolfgangmm agree? |
often exist-db shuts slowely down because of hanging locks:
The text was updated successfully, but these errors were encountered: