Kbase 19762: SonicMQ: What happens When a Client Using ActiveX Crashes?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/3/2001 |
|
SUMMARY:
This solution applies to SonicMQ Versions 2000.x and 3.x.
When a client using the ActiveX control crashes without properly
closing a connection, you must restart the broker to make the client
work properly again.
EXPLANATION:
Because the ActiveX control is using the JavaSoft Plug-in the
Java Virtual Machine (JVM) associated with the control is still up and
connected to the broker even though the client has crashed. This leaves the ActiveX control connected to the broker with the client's client ID.
When you shut down the broker, the connection is broken. Now when you
restart the broker, there are no existing client IDs and the client connects successfully.
This is a common issue in the Microsoft Visual Basic (VB) Developer because the JVM is associated with the Developer process, not the application's. When the application ends, control returns to the Developer which is still running, as is the JVM.