Kbase P7795: Problems running SonicMQ client on an instable network
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
SonicMQ 3.5
SYMPTOM(s):
Problems running SonicMQ client on an instable network
SonicMQ client application stops responding
CAUSE:
Executing a QueueConnection.close() while the network is interrupted caused the client thread to block. A close call of the queue connection while the network connection is interrupted will cause the client thread to wait for the response from the broker. The response from the broker cannot come through until the network connection is alive again.
Also is it dangerous to have a stop or start of a Connection's delivery
of incoming messages inside the onMessage method because that also interacts with the broker on the existing but because of the network problem not responding connection.
FIX:
In our ReliableTalk example that we don't do a QueueConnection.close() that is why there in the onException method. Avoid any further tries to interact with the broker on the existing connection as soon as the network problem is detected
within the onException method.