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 » WebSphere Message Broker (ACE) Support » what trace is on my new configmgr

Post new topic  Reply to topic
 what trace is on my new configmgr « View previous topic :: View next topic » 
Author Message
sangminli
PostPosted: Sun Jan 31, 2010 1:11 am    Post subject: what trace is on my new configmgr Reply with quote

Voyager

Joined: 26 Aug 2008
Posts: 75
Location: Hangzhou, China

the story is like this:
I just created a new configmgr on the AIX machine, and when I use mqsi command, it would generate some 0 size files in /var/mqsi/common/log, and especially when I use mqsilistaclentry, it would generate a trace.txt file in that directory.
I didn't turn on any trace on the configmgr.
There are three things I do trying to turn off whatever possible trace on the configmgr:
(1) mqsichangetrace BMSGD0Q4_C_DV0 -t -b -l none
(2) stop configmgr, issue the below cmd, and start the configmgr again:
mqsiservice BMSGD0Q4_C_DV0 -r Trace=none
mqsiservice BMSGD0Q4_C_DV0 -r TraceSize=""
(3) stop configmgr, and setup the mqsiprofile, and set the below env, then start the configmgr:
export MQSI_UTILITY_TRACE=none
export MQSI_UTILITY_TRACESIZE=0

But none of them work. I still get this kind of 0 size empty files in the dir:
-rw-rw---- 1 xmgbrk mqbrkrs 0 Jan 31 02:25 BMSGD0Q4_C_DV0.mqsilistaclentry.userTrace.bin.0
-rw-rw---- 1 xmgbrk mqbrkrs 0 Jan 31 02:25 BMSGD0Q4_C_DV0.mqsilistaclentry.trace.bin.0

And for the trace.txt, I guess it is for cmp api trace, as I can get some clues from the content, just post part of it as reference:
2010-01-31 02:44:52.0425 main........... i: Configuration Manager Proxy - Basic Information:
Code:
System CLASSPATH = /opt/IBM/mqsi/6.1/classes:
/opt/IBM/mqsi/6.1/classes/jplugininternal.jar:
/opt/IBM/mqsi/6.1/classes/javacompute.jar:
/opt/IBM/mqsi/6.1/classes/bipobserver.jar:
/opt/IBM/mqsi/6.1/classes/eglistener.jar:
/opt/IBM/mqsi/6.1/classes/jmsconnmgr.jar:
/opt/IBM/mqsi/6.1/classes/jmsclient.jar:
/opt/IBM/mqsi/6.1/classes/emailnodes.jar:
/opt/IBM/mqsi/6.1/classes/mail-1.4.jar:
/opt/IBM/mqsi/6.1/classes/activation-1.1.jar:
/opt/IBM/mqsi/6.1/classes/jdbcnodes.jar:
/opt/IBM/mqsi/6.1/classes/JDBCType4ConnFactory.jar:
/opt/IBM/mqsi/6.1/classes/JDBCType4EGListener.jar:
/opt/IBM/mqsi/6.1/classes/JDBCType4DbaseMgr.jar:
/opt/IBM/mqsi/6.1/classes/JDBCType4XAHandler.jar:
/opt/IBM/mqsi/6.1/classes/JDBCType4SinglePhaseTrxn.jar:
/opt/IBM/mqsi/6.1/classes/xahandler.jar:
/opt/IBM/mqsi/6.1/classes/xarecovery.jar:
/opt/IBM/mqsi/6.1/classes/localtrxn.jar:
/opt/IBM/mqsi/6.1/classes/bootstrap.jar:
/opt/IBM/mqsi/6.1/classes/esql2java.jar:
/opt/IBM/mqsi/6.1/classes/webservices.jar:
/opt/IBM/mqsi/6.1/classes/wsdl.jar:
/opt/IBM/mqsi/6.1/classes/ldapSecurityProvider.jar:
/opt/IBM/mqsi/6.1/classes/httpConnector.jar:
/opt/IBM/mqsi/6.1/classes/jms.jar:
/opt/IBM/mqsi/6.1/classes/jruncompute.jar:
/opt/IBM/mqsi/6.1/classes/config.jar:
/opt/IBM/mqsi/6.1/classes/configutil.jar:
/opt/IBM/mqsi/6.1/classes/derby.jar:
/opt/IBM/mqsi/6.1/classes/ConfigManagerProxy.jar:
/opt/IBM/mqsi/6.1/classes/derbynet.jar:
/opt/IBM/mqsi/6.1/classes/derbytools.jar:
/opt/IBM/mqsi/6.1/classes/derbyrun.jar:
/opt/IBM/mqsi/6.1/classes/derbyclient.jar:
/opt/IBM/mqsi/6.1/classes/vfdmftcore.jar:
/opt/IBM/mqsi/6.1/classes/bipbroker.jar:
/opt/IBM/mqsi/6.1/classes/biptrace.jar:
/opt/IBM/mqsi/6.1/classes/CL3Export.jar:
/opt/IBM/mqsi/6.1/classes/CL3Nonexport.jar:
/opt/IBM/mqsi/6.1/classes/dhbbroker.jar:
/opt/IBM/mqsi/6.1/classes/dhbcore.jar:
/opt/IBM/mqsi/6.1/classes/ibmjsse.jar:
/opt/IBM/mqsi/6.1/classes/rmm.jar:
/opt/IBM/mqsi/6.1/classes/apihandler.jar:
/opt/IBM/mqsi/6.1/classes/SLEBase64.jar:
/opt/IBM/mqsi/6.1/classes/SequenceGenerator.jar:
/opt/IBM/mqsi/6.1/classes/XMLtest.jar:
/opt/IBM/mqsi/6.1/classes/activation.jar:
/opt/IBM/mqsi/6.1/classes/commons-codec-1.3.jar:
/opt/IBM/mqsi/6.1/classes/grsint.jar:
/opt/IBM/mqsi/6.1/classes/lm.jar:
/opt/IBM/mqsi/6.1/classes/mail.jar:
/opt/IBM/mqsi/6.1/classes/resolver.jar:
/opt/IBM/mqsi/6.1/classes/vbjorb.jar:
/opt/IBM/mqsi/6.1/classes/vbsec.jar:
/opt/IBM/mqsi/6.1/classes/xercesImpl.jar::
/opt/IBM/mqsi/6.1/classes/derby.jar:
/opt/IBM/mqsi/6.1/classes/ConfigManagerProxy.jar:
/opt/IBM/mqsi/6.1/classes/configutil.jar:
/usr/mqm/java/lib/com.ibm.mq.jar:
/usr/mqm/java/lib/connector.jar:
/opt/IBM/mqsi/6.1/messages:
/var/mqsi/common/wsrr:

Code:
System OS Name = AIX
System OS Architecture = ppc64
System OS Version = 5.3
System JRE Version = 1.5.0
System JRE Vendor = IBM Corporation
Configuration Manager Proxy API Version = 61
Configuration Manager Proxy SCCS Version = Config/com/ibm/broker/config/proxy/ConfigManagerProxy.java, CMP, S610, S610-L81015 1.91.1.2
com.ibm.broker.config.proxy.ConfigManagerProxy loaded from file:
/opt/IBM/mqsi/6.1/classes/ConfigManagerProxy.jar!
/com/ibm/broker/config/proxy/ConfigManagerProxy.class
com.ibm.broker.config.common.CommsMessage loaded from file:
/opt/IBM/mqsi/6.1/classes/config.jar!
/com/ibm/broker/config/common/CommsMessage.class
com.ibm.mq.MQEnvironment loaded from file:
/usr/mqm/java/lib/com.ibm.mq.jar!
/com/ibm/mq/MQEnvironment.class
java.lang.System loaded from file:
/opt/IBM/mqsi/6.1/jre15/ppc64/lib/vm.jar!
/java/lang/System.class
2010-01-31 02:44:52.0485 main........... { com.ibm.broker.config.proxy.MQConfigManagerConnectionParameters.MQConfigManagerConnectionParameters(
ip=, port=0, qmgr=BMSGD0Q6,
mqseClassname=null, mqseURL=null, sslCipherSuite=null, sslPeerName=null, sslKeyStore=null, sslTrustStore=null, sslCRLLdapList=null, sslCRLLdapCollection=null)
2010-01-31 02:44:52.0486 main........... } com.ibm.broker.config.proxy.MQConfigManagerConnectionParameters.MQConfigManagerConnectionParameters()
2010-01-31 02:44:52.0487 main........... { com.ibm.broker.config.proxy.ConfigManagerProxy.setRetryCharacteristics(maxWaitTimeMs=30000)
2010-01-31 02:44:52.0488 main........... } com.ibm.broker.config.proxy.ConfigManagerProxy.setRetryCharacteristics()
2010-01-31 02:44:52.0489 main........... { com.ibm.broker.config.proxy.MQConfigManagerConnectionParameters.getUserID()
2010-01-31 02:44:52.0520 main........... } com.ibm.broker.config.proxy.MQConfigManagerConnectionParameters.getUserID() userId=xmgbrk@meaisg05
2010-01-31 02:44:52.0521 main........... { com.ibm.broker.config.proxy.ConfigManagerProxy.getInstance(
sccsid=Config/com/ibm/broker/config/proxy/ConfigManagerProxy.java, CMP, S610, S610-L81015 1.91.1.2
cmcp={ ip=, port=0, qmgr=BMSGD0Q6, mqseClassname=null, mqseURL=null, channelName=SYSTEM.BKR.CONFIG, maxRetries=3,
requestQueueName=SYSTEM.BROKER.CONFIG.QUEUE, responseQueueName=SYSTEM.BROKER.CONFIG.REPLY, retryWaitMillis=3000, sessionID=null, userId=xmgbrk@meaisg05, deploy
ID=null })
...

I would guess someone is running a java cmp program that have trace on, but there are no mq connections on the qmgr.

Any advice is greatly appreciated. Thanks!

[edit] edited for readability. Next time do your own edit![/edit]
Back to top
View user's profile Send private message MSN Messenger
mqmatt
PostPosted: Mon Feb 01, 2010 5:55 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

All looks reasonably normal to me... internal files that are part of a broker's internal configuration directory, all part of the broker's trace infrastructure.
What's the problem?
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon Feb 01, 2010 6:55 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Perhaps the OP is wondering why zero length files are created even if trace is not switched on.
AFAIK, this is nothing to worry about and as stated this is normal behaviour. I can say that in the almost 8 years since I first started using Broker, I've only ever looked at the files in this directory a couple of times and was related to UserNameServer service traces.(V2.1)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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 » WebSphere Message Broker (ACE) Support » what trace is on my new configmgr
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.