| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Server Channels on OS/390 Connect and Disconnect (MQ v5.3) |
« View previous topic :: View next topic » |
| Author |
Message
|
| lhurtado |
 Posted: Thu Jan 15, 2004 7:26 am Post subject: Server Channels on OS/390 Connect and Disconnect (MQ v5.3) |
 |
|
Newbie
Joined: 15 Jan 2004
Posts: 8
Location: Peru
|
[color=darkblue][/color]
HI everybody, if anyone can help me with this problem:
We have two applications built on C++ which have a COM component. Both send messages to Host (OS/390). They follow the next sequence:
1st. Connect to QM
2nd. Open queues.
3rd. Send messages to Host using MQ Client.
4th. Use GET with WAIT
5th. Close Queues.
6th. Disconnect from QM.
In the logs of the application we can see only one connection and only one disconnection but in the CHIN of the host we have almost 16 connection/disconnections every 5 or 6 seconds.
We don't know where is the problem, we tried a connection and send messages with an other Visual Basic application and we don't have the same problem.
This is an example of what the log of the CHIN shows:
18.21.52 STC01741 +CSQX501I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW is no longer active
18.22.58 STC01741 +CSQX500I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW started
18.23.03 STC01741 +CSQX500I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW started
18.23.03 STC01741 +CSQX501I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW is no longer active
18.23.09 STC01741 +CSQX500I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW started
18.23.09 STC01741 +CSQX501I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW is no longer active
18.23.14 STC01741 +CSQX500I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW started
18.23.14 STC01741 +CSQX501I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW is no longer active
18.23.19 STC01741 +CSQX500I +Q131 CSQXRESP Channel SVRCONN.P.Q131.MW started
Any comments pls.
Thanks
Lisset.[size=9][/size][b][/b] |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Jan 15, 2004 9:04 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Are you absolutely certain that the application is following the logic you gave. Those mesages are the 'norm' for a client issuing a MQCONN followed by and MQDISC.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| lhurtado |
| Posted: Thu Jan 15, 2004 11:18 am Post subject: |
|
|
Newbie
Joined: 15 Jan 2004
Posts: 8
Location: Peru
|
Yes I'm absolutely sure about that.
We were doing some tests and we found something....
When the application component runs in MTS environment we have the problems with the several connections but if the component runs alone, without MTS, it connects to the host only once....
Lisset |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Jan 15, 2004 2:54 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
1. Run a recent service level of MQ
Originally we had a 'health check' thread in the mts layer which connected and disconnected to the server periodically. This later changed to connect and hold connection open and do mqinqs, and finally we got rid of it altogether.
2. MTS does 'cache' connections, so when you mqdisc we dont necessarily drop the connection, but the next mqconn will reuse it. The pooling is controlled by the com definitions as I understand it. |
|
| 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
|
|
|
|
