Kbase 20203: SonicMQ: How to Avoid Terminating the Broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/6/2000 |
|
SUMMARY:
This solution applies to SonicMQ Version 2000.x. It offers a solution
to the problem where as soon as a terminal session to a UNIX machine is closed, a hangup signal is sent to the JVM that causes it to exit and terminate the SonicMQ broker or server session.
In this scenario, the following alert appears within the current
connection of the SonicMQ Explorer:
Connection to broker "<Brokername> " dropped ...
EXPLANATION:
The default shell script for UNIX starts the broker which presents an
output screen something like:
Starting broker "M5".
There is no limit on the number of concurrent
connections.
Interbroker is enabled.
Encryption with 56 bit key enabled.
Starting InterbBroker...
Continuing Interbroker...
SonicMQ Broker started, now accepting tcp connections
on port 2506...
The above error message appears as soon a you close the session.
SOLUTION:
Use "nohup" in front of the script. This avoids sending hangup signals to the JVM of SonicMQ.
For example, when you start the SonicMQ broker, use:
nohup startbr.sh
You can see if the broker is started by looking at the output file nohup.out which is generated by default.
This solution has been tested on Solaris, AIX and HP-UX 11.0.