durable messages: clientId already in use problem
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Matt_Helgren
Posted On:   Tuesday, February 5, 2002 05:39 PM

Having a problem receiving durable messages
after the client disconnects and reconnects. Oustanding messages dont seem to be delivered. Wondering if this is because I'm not specifying the clientid. When I force the clientid to be the same between client runs I then get an exception of "clientid already in use". Seems like swiftmq is not noticing when my client goes away abrubtly. Any thoughts?

Re: durable messages: clientId already in use problem

Posted By:   Andreas_Mueller  
Posted On:   Wednesday, February 6, 2002 12:02 AM

You must set a client id, otherwise a random one is generated and the reconnect will not work.


"Client Id in use" is caused when the connection lost isn't detected by the router (half open sockets). This will be detected on the next keep-alive interval (set for the JMS listener) and the connection is dropped then. Either you wait a bit more until the next keep-alive (60s per default) or you decrease the keep-alive interval to, say 10s.
About | Sitemap | Contact