| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQ 7.0 Client Attachment Feature |
« View previous topic :: View next topic » |
| Author |
Message
|
| davexs2020 |
 Posted: Fri Nov 12, 2010 4:14 am Post subject: WMQ 7.0 Client Attachment Feature |
 |
|
Newbie
Joined: 07 Nov 2009
Posts: 9
|
Hi Gurus,
We have setup a server-connection channel in WMQ for z/OS with the following properties (some are default):
Channel name . . . . . . . . APP.SVRCONN
Disposition . . . . . . . . : QMGR WMQ1
Description . . . . . . . . : APP Server-Connection Channel
Disconnect interval . . . . : 0 0 - 999999 seconds
Put authority . . . . . . . : D D=Default, O=OnlyMCA
Default channel disposition : P P=Private, F=Fix shared, S=Shared
Maximum instances . . . . . : 999999999 0 - 999999999
Maximum client instances . : 999999999 0 - 999999999
Shared conversations . . . : 0 0 - 999999999
We also have Client Attachment Feature available.
+CSQX011I +WMQ1 CSQXGIP Client Attachment feature available
We have 1 publishing application on the z/OS side and 7 other subscribers (subscribing to MQ on z/OS) on z/Linux running RHEL with Apache Tomcat. The problem is only 6 of the 7 subscribers are being allowed to start a channel for MQ on z/OS. The 7th subscriber just waits until the one of the 6 other subscribers receive the message and disconnect (as shown on the z/OS logs below). All of the 7 subscriber applications were started at exactly the same time but only 6 subscribers started a channel.
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
+CSQX500I +WMQ1 CSQXRESP Channel APP.SVRCONN started
+CSQX501I +WMQ1 CSQXRESP Channel APP.SVRCONN is no longer active
All the 7 subscribers applications have almost the same code. Under CAF, i should be allowed any number of simultaneous instances of a server-connection channel that can be started (either from a single or multiple clients), am i right? What should I do to allow all of my 7 subscribers applications to start simultaneously? Is there some setting in CAF that I need to check? Please help.
Thanks.
Best regards,
Dave |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Nov 12, 2010 12:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
We also have Client Attachment Feature available.
+CSQX011I +WMQ1 CSQXGIP Client Attachment feature available |
If this is really a client / svrconn channel problem, verify with your IBM rep and open a PMR.
Keep in mind however that even without the CAF the zOS version of MQV7 will allow a very limited number of SVRCONN channels for remote admin. You seem to be hitting that limit 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Nov 14, 2010 3:36 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| We have 1 publishing application on the z/OS side and 7 other subscribers (subscribing to MQ on z/OS) on z/Linux running RHEL with Apache Tomcat. The problem is only 6 of the 7 subscribers are being allowed to start a channel for MQ on z/OS. The 7th subscriber just waits until the one of the 6 other subscribers receive the message and disconnect (as shown on the z/OS logs below). All of the 7 subscriber applications were started at exactly the same time but only 6 subscribers started a channel. |
I think the problem may lie in Tomcat. If MQ was limiting the number of connections you would see error messages in the z/OS log, &/or the client would be returned a ReasonCode when it makes the connection.
MQ does not have the concept of waiting on a connection request until something else disconnects.
_________________
Glenn |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 14, 2010 10:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The number 7 is suspicious.
I count 1 publishing and 6 subscribers being concurrently connected. This sounds awfully like the 7 client connections allowed for administration...
If we are talking about Tomcat, I'd check the max connections in the pool.
I have seen J2EE applications hit the max connections in the pool and wait until one frees up. You get a JMS error but no linked exception as the exception came from the J2EE layer and not from the provider...
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Nov 15, 2010 5:05 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| fjb_saper wrote: |
This sounds awfully like the 7 client connections allowed for administration...
|
The limit is 5 connections, and only to a channel called SYSTEM.ADMIN.SVRCONN.
From the MQ 7 Announcement Letter:
| Quote: |
| In this release, you can use the MQ Explorer to manage the z/OS® parts of your WebSphere MQ network without having to buy the WebSphere MQ for z/OS V7.0 Client Attachment Feature. This usage is restricted to five client connections and the channel name used must be SYSTEM.ADMIN.SVRCONN (which is the default that is configured for use with the MQ Explorer). |
http://www-01.ibm.com/cgi-bin/common/ssi/ssialias?infotype=an&subtype=ca&htmlfid=897/ENUS208-068&appname=usn&language=enus
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| davexs2020 |
| Posted: Mon Nov 15, 2010 7:54 am Post subject: |
|
|
Newbie
Joined: 07 Nov 2009
Posts: 9
|
| PeterPotkay wrote: |
The limit is 5 connections, and only to a channel called SYSTEM.ADMIN.SVRCONN.
|
Yup, you're right. This might mean that CAF is really enabled (as shown below in the z/OS logs during WMQ startup) in our shop since APP.SVRCONN works but with 6 simultaneous SVRCONN startup limitation.
We also have Client Attachment Feature available.
+CSQX011I +WMQ1 CSQXGIP Client Attachment feature available
| fjb_saper wrote: |
The number 7 is suspicious.
I count 1 publishing and 6 subscribers being concurrently connected. This sounds awfully like the 7 client connections allowed for administration...
|
I also thought that this is WMQ without CAF limitation but I can't find any 6 or 7 client-connection limitation in the manuals to prove this theory. As pointed out by PeterPotkay previously, the limit is 5 connections and only applies to SYSTEM.ADMIN.SVRCONN.
| fjb_saper wrote: |
If we are talking about Tomcat, I'd check the max connections in the pool.
I have seen J2EE applications hit the max connections in the pool and wait until one frees up. You get a JMS error but no linked exception as the exception came from the J2EE layer and not from the provider...
|
Hey, this might be the solution...  But I have no idea how to verify and fix this, can you please provide more details on how to check this in Apache Tomcat connection pool?
| gbaddeley wrote: |
I think the problem may lie in Tomcat. If MQ was limiting the number of connections you would see error messages in the z/OS log, &/or the client would be returned a ReasonCode when it makes the connection.
|
Is there anything I can do to check this further? Please help.
Thanks guys for all the ideas...  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 15, 2010 9:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The connection pool size is defined in JNDI. The connection factory is defined in JNDI and has a pool assigned to it. You have to look at your JNDI setup.
_________________
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
|
|
|
|
