Timeout warnings in the Sun ONE MQ log

Question

I am running Sun ONE MQ 3.0.1 Enterprise Edition
with Windows 2000 Advanced Server. In the log excerpt below, there are warnings referring to 'Timeout' in reaching states. Does anyone know
what causes this? These timeout warnings are throughout the log.
[14/Sep/2003:05:56:33 EDT] [B1066]: Closing: [email protected]:-1->httpsjms:-1888930781. Count=11
[14/Sep/2003:05:56:40 EDT] [B1066]: Closing: [email protected]:0->httpsjms:0. Count=12
[14/Sep/2003:05:56:40 EDT] WARNING [B2051]: Removing IMQConn[AUTHENTICATION REQUESTED,[email protected]:-1,null]:state[AUTHENTICATION REQUESTED]. Timeout in reaching state AUTHENTICATION RESPONSED within 180 seconds.
[14/Sep/2003:05:56:50 EDT] [B1065]: Accepting: [email protected]:-1->httpsjms:-1888930779. Count=11
[14/Sep/2003:05:57:00 EDT] [B1065]: Accepting: [email protected]:-1->httpsjms:-1888930778. Count=10
[14/Sep/2003:05:57:00 EDT] [B1066]: Closing: [email protected]:-1->httpsjms:-1888930778. Count=9
[14/Sep/2003:05:57:02 EDT] [B1065]: Accepting: [email protected]:0->httpsjms:0. Count=11
[14/Sep/2003:05:57:02 EDT] [B1066]: Closing: [email protected]:0->httpsjms:0. Count=11
[14/Sep/2003:05:57:02 EDT] WARNING [B2051]: Removing IMQConn[CONNECTED,???@null:-1,null]:state[CONNECTED]. Timeout in reaching state INITIALIZED within 180 seconds.
[14/Sep/2003:05:57:07 EDT] [B1066]: Closing: [email protected]:0->httpsjms:0. Count=12
[14/Sep/2003:05:57:07 EDT] WARNING [B2051]: Removing IMQConn[CONNECTED,???@null:-1,null]:state[CONNECTED]. Timeout in reaching state INITIALIZED within 180 seconds.

Answer 1

The broker generates these warning when it expects certain
protocol from the client but does not receive it in the 180 second
reply window. When this occurs the connection to the client is
closed by the broker.
For example when a client makes a connection to the broker
the broker sends an AUTHENTICATE_REQUEST to the client.
The client should reply with an AUTHENTICATE response.
If the broker does not receive that response in 180 seconds
it generates the warning you are seeing and closes the connection for the client.
What can cause a client not to respond? If it is on a very heavly
loaded system it may not repond in time - but 180 seonds is a
long time. But given you are using the HTTPS service it is
possible the https servlet is the slow point given it may be
processing many clients. The broker could potentially be the
problem if it is heavly loaded or the host it is running on is
heavily loaded. You should rule all these out first.
To debug this you might try increasing the timeout to see
if that helps the situation:
# timeout in seconds in waiting for client hello and response to
# authentication request on a connection
imq.authentication.client.response.timeout=180
Chris
http://wwws.sun.com/software/products/message_queue/