A
Arun Kumar Mohapatra
Guest
If AppServer is running in Stateless mode then there might be, 2 possible reasons the agent hangs in SENDING state: 1) Client disconnects from broker without notifying or sending proper disconnect message to broker due to high latency in network or any type of network interruption or client crashed/killed. 2) Programming fault may cause a lot more data to be returned than expected, via the broker, from the AppServer to the client (for example: Temp-tables or datasets that contain many more records than expected), that makes the agent hangs in SENDING state for long time. If you are with the test environment then run AppServer with srvrLoggingLevel=3 in ubroker.properties allowed to see what procedures are running by the agents in the server log file by identifying the gent PID those are in SENDING state or we could use “pstack ” to verify the system calls also. What type of client are you using? And what is AppServer operating mode ? I think it is Stateless. As you said after the user get disconnected appserver remains in SENDING state, if that is the case we need to verify the client log also to see it is sending proper disconnect request or not. Will it be possible to provide all the logs for further analysis like client, broker and agent logs? And I think there is no configuration that could minimize or eliminate these hangs, that needs analysis of log files, after that we could suggest something.
Continue reading...
Continue reading...