| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Timeouts for closing MQ JMS connections,sessions,consumers |
« View previous topic :: View next topic » |
| Author |
Message
|
| rrva |
 Posted: Sun Dec 05, 2010 10:56 am Post subject: Timeouts for closing MQ JMS connections,sessions,consumers |
 |
|
Newbie
Joined: 05 Dec 2010
Posts: 2
|
Hello!
For asynchronous MQ JMS message consumers and producers, I have seen code which starts a new thread to call close() on javax.jms.Session, Connection and MessageConsumer instances, supposedly because these calls can hang due to network problems. Are there no client-side timeouts for these calls? If so, where are they configured? Using WMQ 6.0.2.5.
Also when using CLIENT_ACKNOWLEDGE mode, what is the timeout for message.acknowledge() ? |
|
| Back to top |
|
 |
| rrva |
| Posted: Mon Dec 06, 2010 12:34 pm Post subject: Re: Timeouts for closing MQ JMS connections,sessions,consume |
|
|
Newbie
Joined: 05 Dec 2010
Posts: 2
|
Found out that MQ uses a SocketOutputStream when writing acks to the server. These calls are blocking. Bad.
Is the only way to make sure your processing isnt blocked by using a asynchronous message listener and let MQ commit the session if onMessage returns in a separate thread? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
