Server unexpectedly stopping TcpAcceptor

[SimonMartin]

Hi folks

We are using Ice 3.2.1

Our server runs for a period of time then we see something in STDERR like: "Network: stopping to accept tcp connections at .........." after which the server stops listening on the designated port (basically rendering it useless). A thread dump reveals that the server thread pool threads and connection manager threads are running as usual.

Any idea why this is happening? We have changed our Network Trace to 2 from 1 to see if there's anything else we can pick up to determine what is going on.

We are running the exact same process on different kit (on a different network) with no issues.

Is it possible that a low-level unhandled (or logged) error in the Ice runtime is causing the issue?

Many thanks
Simon

[benoit]

Hi Simon,

This is most likely a spurious wake-up problem with the JDK selector. Under rare circumstances, the Java selector select() method returns even if there are no FDs ready for reading. If select() returns an empty key set, Ice interprets it as "no activity" and shuts down the object adapters (as if Ice.ServerIdleTime was set to a non-0 value).

We have added a workaround for this JDK problem in Ice 3.3.x. I'll send you by email a patch for Ice 3.2.1.

Cheers,
Benoit.

[vitali]

I am having the same issue as described above.
How do I get a patch for 3.2.x?
Or better off, should I consider an upgrade to 3.3.x?

[bernard]

Hi Vitali,

Welcome to our forums! I will email you this patch together with patch instructions.

It could also make more sense for you to upgrade to the latest Ice version available, currently Ice 3.4.1.

Best regards,
Bernard