| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Fastpath Binding |
« View previous topic :: View next topic » |
| Author |
Message
|
| psiracusa |
 Posted: Mon Feb 19, 2007 6:31 am Post subject: Fastpath Binding |
 |
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
According to IBM documentation, if you use fastpath binding no new agent is opened up to handle the connection, rather it will run in the same memory space as the queue manager as this. A few questions then:
1. By "no new agent is opened", is this referring to an additional amqzlaa0 process?
2. Would simply setting the MQIBindType to Fastpath in the qm.ini be enough to enable this or would you have to specify it in the connecting app as well?
3. I've set the MQIBindType in the qm.ini to Fastpath and opened up 20 new connections using the RFHUtil utility, and I don't see any additional processes being opened up, but then again, I couldn't get any additional MQ processes to open up without this parameter being set. Does anyone have any test scenarios that can be used to replicate the Fastpath and Standard binding behavior so that it can witnessed at a process or thread level? If not, how can this be tested? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Feb 19, 2007 6:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Don't use fastpath binding unless you absolutely have to.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| psiracusa |
| Posted: Mon Feb 19, 2007 6:51 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2006
Posts: 34
|
| It's a long story about why we were exploring this, but really now I'm just looking for these answers for academic reasons because I was unable to duplicate the described behavior, or what I thought was the described behavior in the manuals. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Feb 19, 2007 8:46 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
I am pretty sure you won't see additional processes starting. Part of the requirements for fastpath state
| Quote: |
The application must not have more than one thread connected to the queue manager at any one time.
|
Item 2 ) I believe you will need to change the CONNX in the application to tell it to use fastpath but I have never actually done this.
Fastpath it is not for the faint of heart and could cause your queue manager to fail if not done correctly but I suspect you already know this  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 20, 2007 4:19 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And to reiterate jeff's comment:
Don't use fastpath unless you absolutely have to.
This would entail huge amount of messages and very critical response time. And IBM should direct you to use it....
Otherwise you're just borrowing trouble... 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
