ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Conversation Sharing and Heartbeats

Post new topic  Reply to topic
 Conversation Sharing and Heartbeats « View previous topic :: View next topic » 
Author Message
SAFraser
PostPosted: Wed Nov 03, 2010 7:02 am    Post subject: Conversation Sharing and Heartbeats Reply with quote

Shaman

Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA

In some recent troubleshooting of channel timeouts after heartbeats went unanswered, we noticed something. It appears that when a heartbeat fails, the channel instance itself is torn down (not just a single conversation). So the channel count decreases by one but the connection count decreases by ten.

I guess this makes sense? The heartbeat operates at the instance level and not the conversation level?
Back to top
View user's profile Send private message
Michael Dag
PostPosted: Thu Nov 04, 2010 1:57 am    Post subject: Reply with quote

Jedi Knight

Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)

That would make sense, after all it's the client code handling the conversation sharing on the other end, not the individual threads, so if the heartbeat fails, the whole channel with all related converations fail.
_________________
Michael



MQSystems Facebook page
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
SAFraser
PostPosted: Thu Nov 04, 2010 2:49 am    Post subject: Reply with quote

Shaman

Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA

This leads me to the conclusion that conversation sharing is best implemented when the client is "reliable".

Our trouble began when our client app servers suffered continual CPU starvation. We would see an app server thread hang for >65 seconds, followed by an RC2009. Then our svrconn would throw an AMQ9271, svrconn timeout of 65 seconds, and the channel instance would get torn down -- taking all 10 conversations with it.

The app servers have since been tuned and patched. Still, I am hesitant to turn conversation sharing back on. We have sufficient maxChannels allowed and lots of yummy system resources available on our MQ servers.
Back to top
View user's profile Send private message
Michael Dag
PostPosted: Thu Nov 04, 2010 3:28 am    Post subject: Reply with quote

Jedi Knight

Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)

not only "reliable" also you have to look at "is it worth it" although conversations can be shared between threads if both or more threads are that active that the interfere with each other (i.e. they have to wait for each other to start sharing the same channel...) it's not worth it either as your performance of "busy" multi threaded clients will go down...
_________________
Michael



MQSystems Facebook page
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Conversation Sharing and Heartbeats
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.