| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere MQ client goes slow when sharing connection |
« View previous topic :: View next topic » |
| Author |
Message
|
| ochocki |
 Posted: Mon Apr 22, 2013 7:05 am Post subject: Websphere MQ client goes slow when sharing connection |
 |
|
Novice
Joined: 05 Jan 2009
Posts: 10
|
Hi,
I'm using websphere mq v6 with a client (v7) that reads and writes to different queues on the same queue manager on multiple threads.
When I disable reading thread I can reach over 1000 transactions per second. When I turn it on I am able to process only about 200 transactions.
I think that using more connections would help (am I right?).
How can I configure number of connections on client and server side?
m. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Apr 23, 2013 5:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You get exactly one connection for each MQCONN you issue.
If you have one thread issuing an MQGET over that conn, another thread can not issue another MQGET over the same conn at the same time. Well, it can issue it, but it won't get a response back until after the first MQGET completes. |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Apr 23, 2013 7:23 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| mqjeff wrote: |
| You get exactly one connection for each MQCONN you issue. |
Correct, but only if you change SHARECNV to 0 from default of 10. Be aware that if you do that, then you lose new-in-V7 async functionality. Experiment with different values of SHARECNV to see which works best for you. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Apr 23, 2013 3:28 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mvic wrote: |
| mqjeff wrote: |
| You get exactly one connection for each MQCONN you issue. |
Correct, but only if you change SHARECNV to 0 from default of 10. Be aware that if you do that, then you lose new-in-V7 async functionality. Experiment with different values of SHARECNV to see which works best for you. |
The OP is using MQ v6 and v7. Client will use the lowest level protocol, v6, which does not support SHARECNV.
_________________
Glenn |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 24, 2013 3:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| gbaddeley wrote: |
| mvic wrote: |
| mqjeff wrote: |
| You get exactly one connection for each MQCONN you issue. |
Correct, but only if you change SHARECNV to 0 from default of 10. Be aware that if you do that, then you lose new-in-V7 async functionality. Experiment with different values of SHARECNV to see which works best for you. |
The OP is using MQ v6 and v7. Client will use the lowest level protocol, v6, which does not support SHARECNV. |
Even if they weren't, MQCONN will never return more than one connection, nor less than one connection if it returns a CC=0 and RC=0.
It may happen that it returns the same connection more than once on subsequent calls. That doesn't mean that it isn't returning one and only one connection each time you call it.
The point I was making is that you need to call MQCONN more than once if you want to do two things at once. |
|
| 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
|
|
|
|
