| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS using MQPUT1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| jase_t_thomas |
 Posted: Fri Feb 12, 2010 6:55 am Post subject: JMS using MQPUT1 |
 |
|
Newbie
Joined: 08 Feb 2010
Posts: 6
|
Hi all,
We are using a 3rd party product that uses JMS to communicate using MQ (7). We recently ran some MQ performance diagnostics against their application and noticed that one of the statistics - Put1Count - was showing a value corresponding to the response messages receives.
This looks like they (or JMS) are using MQPUT1. MQPUT1 is an inefficient way to post a message to a queue as it performs an open/close each time a message is sent.
Does anyone know if this is a characteristic of the JMS/MQ implementation? Or could a different JMS API call result in the better use of MQPUT? Or could configuration alter this?
We are looking at advising the provider to make modifications, in order to use MQPUT instead of MQPUT1. If anyone is aware of any guidelines/restrictions concerning JMS and MQ in this area, that would be much appreciated.
Thanks & Rgds,
J |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Feb 12, 2010 2:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This may greatly depend on the design followed by the 3rd Party.
They may use an anonymous (generic) producer and specify the destination on the send method... (hence an mqput1)...
Or create a destination specific producer (equivalent to an mqput)...
Depending on how they use the producer, changing from one to the other might become a bigger deal than what you are willing to pay for...
If their application (3rd Party) is providing the server, in a request / response model, using an anonymous producer and mqput1 makes total sense.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Fri Feb 12, 2010 4:04 pm Post subject: Re: JMS using MQPUT1 |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| jase_t_thomas wrote: |
Hi all,
We are using a 3rd party product that uses JMS to communicate using MQ (7). We recently ran some MQ performance diagnostics against their application and noticed that one of the statistics - Put1Count - was showing a value corresponding to the response messages receives.
This looks like they (or JMS) are using MQPUT1. MQPUT1 is an inefficient way to post a message to a queue as it performs an open/close each time a message is sent. |
"MQPUT1" is a normal design paradigm for a request processing application to send a reply message and its why the MQI call exists. This is based on the possibility that each requesting app may be using a different reply queue on different queue managers. Its particularly true if the response queues are dynamic and only exist for the life of one transaction. There is no point opening a response queue and holding it open (for multiple transactions) if there are potentially lots of response queues and each one may only be used once.
_________________
Glenn |
|
| Back to top |
|
|
| jase_t_thomas |
| Posted: Mon Feb 15, 2010 2:09 am Post subject: |
|
|
Newbie
Joined: 08 Feb 2010
Posts: 6
|
| Thanks for your responses both. It is clearer now. |
|
| 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
|
|
|
|
