| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| JMS or MQI |
« View previous topic :: View next topic » |
| Author |
Message
|
| JLRowe |
 Posted: Fri Oct 12, 2007 6:20 am Post subject: |
 |
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
This rings a bell for me, I seem to recall seeing somewhere that the client and server handshake when a connection is made. The server will account for an older client by using the appropriate version of the wire protocol. Also, I know that new clients are backwards compatible with older versions of the server.
Going back to the original question, I would say in general JMS is a better choice as it is more abstract and deals with a lot of the lower level issues with MQ messages such as encoding, message formats and conversion.
As for performance I really don't see why JMS should be slower, except when you use JMS selectors to filter messages by property - MQ does not support indexing of properties and so traverses the queue looking for messages that match the selector.
| PeterPotkay wrote: |
This topic has come up on the list serve. An MQ Admin should be able to tell the MQ Client's MQ version either from the MQMD or from the connection handle.
Hursley is aware of the desire.
The topic of what needs to be distributed for Java MQ Clients has also been discussed.
http://www.mail-archive.com/mqseries@listserv.meduniwien.ac.at/msg09527.html
The fact that there can be a discussion at all is proof that the manuals are not clear on this point. And as zpat said, for years the MA88 support pack was the official way for JAVA apps to make MQ Client connections, and all they were was the jars. When IBM included those jars in the base product, there was never an announcement saying the jars alone wouldn't work.
I have dozens of apps developed during the MA88 days. Using just the jars they created the apps the official way, and have been working for years. You try telling those JAVA gurus that they now have to install a full client software, especially without any doc specifically saying the model has changed. They continue to use just the jars as they upgrade and there has never been a problem with functionality or support. |
|
|
| Back to top |
|
 |
|
|
|
|
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
|
|
|
|
