| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Performance problem with MessageProducer.close() > 952 by |
« View previous topic :: View next topic » |
| Author |
Message
|
| jaxzin |
 Posted: Mon Aug 22, 2011 7:58 am Post subject: Performance problem with MessageProducer.close() > 952 by |
 |
|
Newbie
Joined: 07 Nov 2010
Posts: 3
|
| I'm finding that if my message data length exceed 952 bytes when enqueueing a message to WMQ 7, the performance of javax.jms.MessageProducer.close() suffers. When the length is 952 bytes, the method returns in ~10 ms, but if the length is 953 bytes or greater is takes > 200 ms to return. Anyone have an idea what might be happening? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Aug 22, 2011 8:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you need to close the producer every time, or can you make use of an anonymous producer? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jaxzin |
| Posted: Mon Aug 22, 2011 9:32 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2010
Posts: 3
|
| The usage is within a servlet request (user performs an action that queues a message) so leaving the producer open would result in the resources leaking. Or am I misunderstanding what you mean? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 22, 2011 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jaxzin wrote: |
| The usage is within a servlet request (user performs an action that queues a message) so leaving the producer open would result in the resources leaking. Or am I misunderstanding what you mean? |
Not necessarily. You would have to care to release the resource on passivate and reacquire it on activate... and of course release on close, finalize etc....
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sigormley |
| Posted: Tue Sep 13, 2011 7:37 am Post subject: |
|
|
Newbie
Joined: 24 Feb 2004
Posts: 6
|
Unless you're very careful, it's best to close off the JMS resources when you've finished with them, and let the app server cope with making your resource usage efficient.
Make sure you're running a 7.0.1.6 JMS client, there's a fix in it that might help, or try checking your networking parameters to make sure there's no delay when transmitting TCP packets (tcp_nodelayack?) - that 200ms sounds all too familiar... |
|
| 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
|
|
|
|
