Help Determine the Cause of Spontaneous Disconnections between a ZeroC Client and Server
On a regular basis a client disconnects spontaneously from a server running ZeroC ICE. Our current program/setup is used in many locations and only has problems in one place. My hope is by viewing the logged exceptions/stacktraces emitted by ZeroC ICE, you might be able to give us some insights into the problem, which may well be specific to a certain computer or the local network.
I have provided many details below to frame the problem. Let me know if you need anything else. There is already so much information to send that I didn't want to include anything extra unless asked.
At our facility we have a number of identical servers which run on RHEL7 and are written in Java. We also have a number of identical clients, in fixed locations, written in Java which connect to the servers. Each client runs on either RHEL7 OR Windows and only connects to a specific server.
Connections between client and server happen through ZeroC 3.6 using Glacier2. We also use IceStorm to allow servers to execute "callbacks" on the connected clients (this is initiated through IceBox). Our Clients and Servers use the 3.6 ACM system.
Each client and server is configured identically.
_Here is the client code which configures ACM in the client:
int ACMTimeout = sessionPrx.getACMTimeout();
router.ice_getConnection().setACM(new IntOptional(ACMTimeout), new Optional<>(ACMClose.CloseOff),
See attached server config files.
The problem only occurs for one specific client-server pair. The client spontaneously disconnects from the server (see log messages below).
Problem Server located at IPX and runs under RHEL7.
Problem Client located at IPY and runs under Windows.
**Client-side log messages
The messages written, client-side as configured by calling the method "properties.setProperty("Ice.LogFile",...)":
The messages which the icebox and glacier processes wrote to stdout/stderr at the time of the problem.