[W2003]: Broker not responding [AUTHENTICATE] for 120 seconds. Still trying

Question

Hello All ,
I am running Sun MQ 3.5 SP2. I get this error on sun mq from time to time. Once I get this error I an unable to communicate with the broker and the only way for me to recover if to issue a kill on the broker PID. Can some one please explain to me why this happens.
byw I tried the
telnet brokerhost brokerport and I got the serviices list.
However when i try imqcmd or even connect to the broker from the admin console i get the warning messages below.
Thx a lot for all the help
[W2003]: Broker not responding [AUTHENTICATE] for 120 seconds. Still trying...
[W2003]: Broker not responding [AUTHENTICATE] for 360 seconds. Still trying...
[W2003]: Broker not responding [AUTHENTICATE] for 840 seconds. Still trying...
Ajay

Answer 1

If you are running JDK1.5, there are vm commands which
can be used to get the same information ... let me know
General notes on sending a kill -QUIT
* you can not be running the broker in the background
or nohup'd (those block the delivery of the QUIT signal)
* you cant get the output from a broker that is started
by another process (such as the app server) because
those processes usually send stdout/stderr to dev/null
* the output from a kill -QUIT goes to stdout/stderr NOT
the broker log file (sorry we have no way to
intercept the information and log it)
* make sure you are sending it to the high level java process
(if you are using an older linux e.g. one that doesnt
have LWP's you may see lots of java processes)
To find the correct process:
- locate the imqbrokerd process
- find its children (with parent pid equal to the
imqbrokerd pid)
- kill the java process on that list
If killing the broker still doesn't work and you've checked
the above conditions ....something may be wrong or
deadlocked @ the vm level ...
- if so, what is the cpu doing when it occurs
- do you see anything if you ptrace the vm process