| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS Bindings Mode vs Client Connection & MaxMsg Length |
« View previous topic :: View next topic » |
| Author |
Message
|
| anderc1 |
 Posted: Wed May 03, 2006 11:53 am Post subject: JMS Bindings Mode vs Client Connection & MaxMsg Length |
 |
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
| When using a JMS Client connection, does it have the same 4MB MaxMsg Length limitation as that of a normal MQClient using MQSERVER client connection? Haven't seen this in Using Java manual specifically. Prod server came to a screaching halt today when a greater than 4mb message hit the queue. Got a Data length error when the app tried to get the message. All other messages piled up behind it. Suspect the developer used client connection rather than Bindings mode in app. App sits on server with Qmgr. |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed May 03, 2006 12:03 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
It depends on what the MAXMSGL is set to on SVRCONN channel also.
Having said that I don't have any idea if there is any difference between the message sizes between client and server bindings but I am pretty sure it is more than 4 MB for client bindings. I think you problem is with the settings on the SVRCONN channel. |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed May 03, 2006 3:06 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
MQSERVER Client connections are limited to 4Mb. Other Client connections, Client Table, Java, are limited to the value set in the channel.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| anderc1 |
| Posted: Thu May 04, 2006 6:17 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
Thanks for the responses. It just hit me to check queue usage and it shows that a java client is accessing the queue using a svrconn channel with the default 4mb. This channel was intended for another app on a remote system. I did increase the MaxMsg Length on the svrconn channel just to see if that's all it needs after a channel restart. Still going to make the developer correct his app. I've had the hardest time getting the developers to understand the difference between MQClient and MQServer. Now with them using JMS and WAS I'm about ready to jump out the window, which isn't that drastic considering I'm on the ground floor.  |
|
| 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
|
|
|
|
