|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Analyzing Connection statistics from runmqsc |
« View previous topic :: View next topic » |
Author |
Message
|
artrangan |
Posted: Mon Apr 16, 2007 6:07 pm Post subject: Analyzing Connection statistics from runmqsc |
|
|
Novice
Joined: 18 Mar 2007 Posts: 13
|
We have a JMS application that always creates non-transacted sessions --
Code: |
connection.createSession(false, Session.AUTO_ACKNOWLEDGE); |
However, when I run dis conn(*) all from runmqsc, I see some connections that appear to be transacted. For eg.
Code: |
AMQ8276: Display Connection details.
CONN(D24FB6450AEF442B)
EXTCONN(414D5143504D4F4D303031514D475230)
TYPE(CONN)
PID(30476) TID(526140)
APPLTAG(WebSphere MQ Client for Java) APPLTYPE(USER)
CHANNEL(CHANNEL.ABCD.SVRCONN) CONNAME(172.xx.xx.xxx)
CONNOPTS(MQCNO_SHARED_BINDING) USERID(mqm)
UOWLOG( ) UOWSTDA(2007-04-03)
UOWSTTI(19.29.46) UOWLOGDA( )
UOWLOGTI( ) URTYPE(QMGR)
EXTURID(XA_FORMATID[00000000] XA_GTRID[] XA_BQUAL[])
QMURID(0.58564222) UOWSTATE(ACTIVE) |
I am assuming this connection was initiated by a transacted session based on the UOWSTDA. First, is that a valid assumption ?
Some of these connections, like the one above, appear to be long running -- started 13 days back.
Any reasons why we should be seeing this kind of behavior ? Have verified that the only application accessing the QMgr from this IP is using non-transacted sessions.
Any help would be much appreciated.
Thanks,
Art. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Apr 16, 2007 7:31 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Remember that in JMS the way you build the session does not mean much.
The app server and the J2EE settings of the MDB will OVERRIDE your settings.
So if you want a non transacted session make sure that the method has the attribute of transaction not supported...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
artrangan |
Posted: Mon Apr 16, 2007 9:37 pm Post subject: |
|
|
Novice
Joined: 18 Mar 2007 Posts: 13
|
I am using a standalone application to connect to the Queue Manager and creating non-transacted sessions. Would the MQ JMS client code override these settings, by any chance ?
Thanks,
Art.
fjb_saper wrote: |
Remember that in JMS the way you build the session does not mean much.
The app server and the J2EE settings of the MDB will OVERRIDE your settings.
So if you want a non transacted session make sure that the method has the attribute of transaction not supported...
Enjoy  |
|
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Apr 17, 2007 6:32 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Couldn't really tell you as I never use non transacted sessions.
Transaction benefits are just too great to pass up....  _________________ 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
|
|
|
|