| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Channel Triggering |
« View previous topic :: View next topic » |
| Author |
Message
|
| JosephGramig |
 Posted: Tue Feb 04, 2014 7:59 am Post subject: |
 |
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
I also add the following stanzas:
| Code: |
CHANNELS:
MaxChannels=1000
MaxActiveChannels=1000
AdoptNewMCACheck=ALL
AdoptNewMCA=ALL
TCP:
KeepAlive=Yes
|
Doing this seems to provide more reliable channel operation. I'm ready to be corrected on the efficacy of doing this. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Feb 04, 2014 8:36 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| JosephGramig wrote: |
I also add the following stanzas:
| Code: |
CHANNELS:
MaxChannels=1000
MaxActiveChannels=1000
AdoptNewMCACheck=ALL
AdoptNewMCA=ALL
TCP:
KeepAlive=Yes
|
Doing this seems to provide more reliable channel operation. I'm ready to be corrected on the efficacy of doing this. |
We do this too. Depending on the role of the server we might have higher values for Max*Channels.
Seems odd to me that these are not the defaults in modern versions of MQ.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Feb 04, 2014 8:51 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| PeterPotkay wrote: |
| Seems odd to me that these are not the defaults in modern versions of MQ. |
The product is not packaged to be production-ready. Logs are also configured not-for-prod.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Thu Feb 06, 2014 2:07 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
I've seen a similar situation years ago. The way I understand it is that there is a very small window of opportunity (a few milliseconds) when it is possible for the queue manager to miss a trigger. The advice was to change TRIGINT(999999999) to a value of about 1 minute if I recall correctly. This means that the queue manager will check every minute if it have not maybe missed a trigger, and if found, fire the trigger. It did solve our problem.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| 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
|
|
|
|
