Author |
Message |
Topic: Server Connection Channels and the Channel Status Table |
WingCommanderBadger
Replies: 9 Views: 9270
|
Forum: General IBM MQ Support Posted: Fri Jul 09, 2010 3:50 am Subject: Re: Server Connection Channels and the Channel Status Table |
Yes I seem to recall that about setting KeepAlive on MQ Channels on z/OS.
Anyhow, thanks very much to all for your advice. |
Topic: Server Connection Channels and the Channel Status Table |
WingCommanderBadger
Replies: 9 Views: 9270
|
Forum: General IBM MQ Support Posted: Tue Jul 06, 2010 2:03 am Subject: Re: Server Connection Channels and the Channel Status Table |
The behaviour I'm now observing is that MQ doesn't seem to allocate Conversations per Channel in the status table in a consistent way. The default max number of Conversations per Channel is 10. So, ... |
Topic: Server Connection Channels and the Channel Status Table |
WingCommanderBadger
Replies: 9 Views: 9270
|
Forum: General IBM MQ Support Posted: Mon Jul 05, 2010 11:47 pm Subject: Re: Server Connection Channels and the Channel Status Table |
Jeevan - yes I'm already aware of this potential issue from my MQv6 days. We have KeepAlive=YES in all our Queue Manager's qm.ini files. I'm now wondering whether MQv7 offers a way of achieving this f ... |
Topic: Server Connection Channels and the Channel Status Table |
WingCommanderBadger
Replies: 9 Views: 9270
|
Forum: General IBM MQ Support Posted: Mon Jul 05, 2010 7:38 am Subject: Re: Server Connection Channels and the Channel Status Table |
Just realised, it's a new MQv7 feature: Sharing Conversations. When I set this value to 1 for the Server Connection Channel in question I see 24 entries in the table. Now I'm making some progress.... ... |
Topic: Server Connection Channels and the Channel Status Table |
WingCommanderBadger
Replies: 9 Views: 9270
|
Forum: General IBM MQ Support Posted: Mon Jul 05, 2010 7:14 am Subject: Server Connection Channels and the Channel Status Table |
Thanks for the response fjb_saper, however your reply seems to be talking a lot about MDBs which we're not using any more. Are you suggesting the rules for using MDBs and Spring DefaultMessageListener ... |
Topic: Server Connection Channels and the Channel Status Table |
WingCommanderBadger
Replies: 9 Views: 9270
|
Forum: General IBM MQ Support Posted: Mon Jul 05, 2010 6:42 am Subject: Server Connection Channels and the Channel Status Table |
My team is in the process of migrating a number of 'listener' style Java/JMS services from a WebSphere Application Server 6.1 platform using Message Driven Beans to a Tomcat 6.0.26 platform using Spri ... |
Topic: Orphaned Open handles to Queues on remote QueueManager |
WingCommanderBadger
Replies: 5 Views: 5691
|
Forum: IBM MQ Java / JMS Posted: Fri Mar 28, 2008 7:30 am Subject: TCP KeepAlive |
Don't forget that the actual config for the TCP KeepAlive settings are made at the O/S level. If I remember correctly, these values are much easier to change on Linux/Unix than on Windows. |
Topic: Channel Performance when putting messages to DLQ |
WingCommanderBadger
Replies: 4 Views: 4065
|
Forum: General IBM MQ Support Posted: Wed Aug 15, 2007 2:00 am Subject: Channel Performance when putting messages to DLQ |
Excellent advice NigelG!!
Thanks to you all for your help - very much appreciated. |
Topic: Channel Performance when putting messages to DLQ |
WingCommanderBadger
Replies: 4 Views: 4065
|
Forum: General IBM MQ Support Posted: Wed Aug 15, 2007 12:58 am Subject: Channel Performance when putting messages to DLQ |
A customer of ours recently overlooked clearing down one of their queues to the extent that it filled up and subsequent messages were then placed on the DLQ. I noticed that there appeared to be a sign ... |
Topic: IBM's JMS Implementation - Dead Letter Queue access |
WingCommanderBadger
Replies: 6 Views: 6348
|
Forum: IBM MQ Java / JMS Posted: Thu Apr 05, 2007 12:32 am Subject: IBM's JMS Implementation - Dead Letter Queue access |
OK, this is interesting but we get the same behaviour even when we don't use WebLogic and use a standalone Java/JMS Client instead. One thing I forgot to mention previously was that the Dead Letter Qu ... |
Topic: IBM's JMS Implementation - Dead Letter Queue access |
WingCommanderBadger
Replies: 6 Views: 6348
|
Forum: IBM MQ Java / JMS Posted: Wed Apr 04, 2007 4:03 am Subject: IBM's JMS Implementation - Dead Letter Queue access |
Our client wishes to use Weblogic App Server and claims that he cannot configure these values. What relevant part of the JMS API is exposed to an App Server that is not exposed to a programmer who jus ... |
Topic: IBM's JMS Implementation - Dead Letter Queue access |
WingCommanderBadger
Replies: 6 Views: 6348
|
Forum: IBM MQ Java / JMS Posted: Wed Apr 04, 2007 3:51 am Subject: IBM's JMS Implementation - Dead Letter Queue access |
I'm currently working with a client who will remotely access our Queue Manager using JMS. However, during testing we have noticed that there appears to be some default behaviour built into IBM's JMS I ... |
Topic: Max Qmanagers |
WingCommanderBadger
Replies: 8 Views: 5847
|
Forum: General IBM MQ Support Posted: Fri May 26, 2006 2:58 am Subject: Max Qmanagers |
Thanks for the advice - it's certainly something I'll consider. However I'd still like to know if there are any guidelines regarding max number of queue managers on a server. I can't seem to find any ... |
Topic: Max Qmanagers |
WingCommanderBadger
Replies: 8 Views: 5847
|
Forum: General IBM MQ Support Posted: Fri May 26, 2006 2:15 am Subject: Multiple Queue Managers per Machine |
Did anyone ever propose an answer to this question? I'm looking into an architecture (as proposed by a supposed Specialist MQ Consultancy) that may involve running several business-partner specific QM ... |
Topic: Where does my message go?! |
WingCommanderBadger
Replies: 19 Views: 15483
|
Forum: Clustering Posted: Fri Apr 07, 2006 6:15 am Subject: Where does my message go?! |
I believe it's still possible for messages that have arrived at a Primary QM but have not been taken off a queue to become 'marooned' when the Primary QM fails. However, all subsequent messages sent d ... |