Router log shows disconnect request when connecting from client.
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Garry_Larimore
Posted On:   Thursday, August 18, 2005 10:43 AM

We are having issues with the SwiftMQ router on the server disconnecting whenever we try to connect with a client application. For example, if I try to connect using SwiftMQ Explorer, the router log shows this: 2005-08-18 10:21:38.12/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.50.80.00 2005-08-18 10:21:38.278/sys$jms/INFORMATION/JMSConnection v500/10.50.80.00:3473/receiving disconnect request, scheduling connection close 2005-08-18 10:21:38.285/10.50.80.00:3473/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached 2005-08-18 10:21:38.290/sys$jms/INFORMATION/JMSConnection v500/10.50.80.00:3473/connection closed    More>>

We are having issues with the SwiftMQ router on the server disconnecting whenever we try to connect with a client application. For example, if I try to connect using SwiftMQ Explorer, the router log shows this:


2005-08-18 10:21:38.12/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: 10.50.80.00

2005-08-18 10:21:38.278/sys$jms/INFORMATION/JMSConnection v500/10.50.80.00:3473/receiving disconnect request, scheduling connection close

2005-08-18 10:21:38.285/10.50.80.00:3473/BlockingHandler/INFORMATION/Exception, EXITING: java.io.IOException: End-of-Stream reached

2005-08-18 10:21:38.290/sys$jms/INFORMATION/JMSConnection v500/10.50.80.00:3473/connection closed


This happens with another client that we use to connect to the router with also. I am not sending the disconnect request from the client, yet it shows up in the log and then an exception is thrown.


(Note: I tried searching the forum log database for an answer to this but it tells me that it is down for maintenance.)


Thank you - Garry

   <<Less

Re: Router log shows disconnect request when connecting from client.

Posted By:   Andreas_Mueller  
Posted On:   Thursday, August 18, 2005 11:15 AM

The above log entries could also be from the JNDI connection (it creates a JMS connection under the covers). If you close the JNDI context, the JMS connection is closed.


A regular close on a connection - by calling connection.close() - sends a disconnect request. A connection which is closed otherwise (killing the client) do not, of course. So this is a regular closed connection above and may be the JNDI connection.


What do you see at your client? Any exception?


May be this FAQ entry helps.
About | Sitemap | Contact