ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » OPPROCS high after 3.6 jar file update

Post new topic  Reply to topic
 OPPROCS high after 3.6 jar file update « View previous topic :: View next topic » 
Author Message
chintu
PostPosted: Wed Jun 20, 2007 11:05 am    Post subject: OPPROCS high after 3.6 jar file update Reply with quote

Acolyte

Joined: 27 Dec 2004
Posts: 64
We were on
AIX 5.2
MQ 5.3.CSD12
WAS 5.0
WF 3.6( but using 3.4 classic jar files)

Last friday, we migrated our Production environment to WAS 6.0.2.5 and updated two J2EE applications that were using the 3.4 jars to use the WF 3.6 jar files. Since then we are seeing an increase in the number of bindings to some of the queues for the WF QMGR.


Here is a sample of what we are seeing:
echo 'display qstatus(EXCINPUTQ) type (handle) APPLTAG CONNAME'|runmqsc|grep -c EXCINPUTQ
10875
echo 'display qstatus(ADMINPUTQ) type (handle) APPLTAG CONNAME'|runmqsc|grep -c ADMINPUTQ
5437
echo 'display qstatus(RTSINPUTQ) type (handle) APPLTAG CONNAME'|runmqsc|grep -c RTSINPUTQ
5440


a)Is it ok to have such a hig OPPROCS count?

All of them point to "java". The processIds point to either of the 2 J2EE applications that are now using the 3.6 native jar files.
Both J2EE applications are custom webclients( wirtten using the WF API). There are no interactions to any queues or databases. Hence there is no chance that the code is not closing connections...etc.

We have not updated the MQ_INSTALL_ROOT websphere environment variable in WAS6 to point to the /usr/mqm. It is currently pointing to the MQ libraries that were installed with WAS.

b)Could this be an mq jar mismatch issue?

Thanks.
Back to top
View user's profile Send private message
hos
PostPosted: Thu Jun 21, 2007 4:02 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470
Hi,

I recommend to
- set MQ_INSTALL_ROOT to your external MQ installation
- apply the latest service pack on your external MQ installation
and retry.

If you still see this behaviour, you need to check whether it is really a connection leak or just an MQ performance optimization: wait 6 minutes and check the connections again.

If you're still having trouble, contact IBM's MQ support.
Back to top
View user's profile Send private message
chintu
PostPosted: Thu Jun 21, 2007 6:28 am    Post subject: Reply with quote

Acolyte

Joined: 27 Dec 2004
Posts: 64
hos, Thanks for you reply

In one of our lower environments, we migrated from MQ 5.3 CDS12 to 6.0.2.1. We then updated the MQ_INSTALL_ROOT to point to the MQ libraries in /usr/mqm. However we are still seeing this issue in that lower environment. I opened a PMR and the WF guru pointed me to
http://www-1.ibm.com/support/docview.wss?uid=swg1IY88954

This APAR is available in MQ 6.0.2.1 but we are still seeing this issue in an MQ6.0.2.1 environment.

The PMR has been transferred to MQ team...and they are still investigating this.

I will keep this post updated with their repsonse.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » OPPROCS high after 3.6 jar file update
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.