Using jmqcmd to restart the broker on  customer  7.0 does not work. The broker
exits instead of restarting. This works on  customer  6.2.

To reproduce just run the broker from the command line and run
"jmqcmd restart bkr". The broker will exit.

N/A

  xxxxx@xxxxx   2001-05-04
Broker restart is handled by the shell script that runs the broker. If the
broker exits with 255 then the script restarts it. The problem is on Linux 7.0
even thought the broker is exiting with Sysmte.exit(255) the shell script
always gets '0' as the value for $?. Some observations:
1. I wrote a simple Java program that calls System.exit(255) and a simple
   shell script to run it and echo $?. This fails on RedHat 7.0 ($? is 
   always 0). It works on RedHat 6.2 ($? is 255). So the problem is not
   unique to the Broker.
2. I changed the shell script to run another shell script that calls
   'exit 255' and echo $?. This case works on RedHat 7.0. So the problem
   appears to be related to how the JVM implements System.exit().
Next step is to search for VM bugs that could explain this.


  xxxxx@xxxxx   2001-05-04 (later)
This is a RedHat 7.0 bug. See JDK bug 4388732. This is supposed to
be fixed in RedHat 7.1
Restart will stay broken on 7.0