Skip to content
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

sometimes fb_inet_server gets hung for startup [CORE5450] #5721

Closed
firebird-automations opened this issue Jan 11, 2017 · 5 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Ray Holme (rholme)

Using Apache Tomcat and doing a restart- occasionally get message in log that cannot get a connection to server.

a) isql works fine (using local connection); NOT if use remote connection

b) problem goes away after 1/2 hour or so (for the patient)
AND
reboot of machine solves problem more quickly

c) problem shows up in the OS log files as the inet service is being rejected
- I am "assuming" too many hits in a short period of time

I see this VERY occasionally on my Fedora box. The first time, I was doing something else and happened to wait.
The second and ... times I found out reboot solved the problem.
Then I found the problems in the log file (I will add more here if and when I get the error again) as I do NOT have a real recent example.
Yesterday this happened on another system, this time a MAC. The person was in a rush so I did not delve into the logs and get examples of the messages.
BUT reboot solved the problem.

I suspect a race condition is happening where Tomcat is hitting the server with multiple requests for connections in a short time but have no way to prove that.
I certainly have no idea why this happens sometimes and not more frequently, but I restart the web server quite a few times before it happens again.

Will try to add exact message from log when I can.

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Confirm that you use classic server with xinetd listener.

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

This really seems to be an issue which should be discussed in the Support mailing list and not here.

There are several possible areas which need to be explored before a tracker case is warranted.

@firebird-automations
Copy link
Collaborator Author

Commented by: Ray Holme (rholme)

Apologies, this might be an xinetd daemon issue. Checking.
Please close this report.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant