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 » Configuration Manager stops when connecting to Toolkit

Post new topic  Reply to topic
 Configuration Manager stops when connecting to Toolkit « View previous topic :: View next topic » 
Author Message
navjotkaur78
PostPosted: Wed Dec 31, 2008 2:23 am    Post subject: Configuration Manager stops when connecting to Toolkit Reply with quote

Apprentice

Joined: 09 Feb 2006
Posts: 31

WMB Version: 6.1.0.2
MQ version: 6.0.2.5

I have created the Broker and configuration manager on Linux. Now when i try to connect this config manager from my Windows Toolkit, it does not connect and in turn it stops the config manager on Linux. I was successfully able to connect to the Queue manager from my Windows machine..
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Dec 31, 2008 2:24 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Any errors from CM or queue manger? Any network issues?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
navjotkaur78
PostPosted: Sat Jan 03, 2009 8:15 am    Post subject: Reply with quote

Apprentice

Joined: 09 Feb 2006
Posts: 31

The error is from Config manager. This is not network issue because i am able to connect to Queue manager.

My syslog is showing the following exception:

Unexpected exception in ConfigurationManager class initialize method; exception text: 'java.lang.NoClassDefFoundError: com.ibm.mq.MQQueue', 'com.ibm.mq.MQQueue'. : CMSBRK1.agent: /build/S610_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp: 711: ConfigurationManager.initialize: CMSBRK1: CMSBRK1

I have compared the CLASSPATH variable with my previous working installation on Linux. All seems to be fine.

Thanks in Advance
Back to top
View user's profile Send private message
djeripo
PostPosted: Fri Jul 22, 2011 11:00 pm    Post subject: Reply with quote

Master

Joined: 25 Jan 2004
Posts: 225

Well,I too faced exact same problem.Only difference is my MQ is at level 7.After few hours of non stop struggle figured out, MQSeriesJava-7.0.1-3.i386.rpm is missing.Onlly after Installing that ,com.ibm.mq.jar along with other other jars were found at:
/opt/mqm/java/lib

Code:
[root@durga MQ]# rpm -ivh MQSeriesJava-7.0.1-3.i386.rpm
Preparing...                ########################################### [100%]
   1:MQSeriesJava           ########################################### [100%]
[root@durga MQ]# cd /opt/mqm/java/lib
[root@durga lib]# ls
CL3Export.jar                  com.ibm.mq.headers.jar     com.ibm.mq.pcf.jar        dhbcore.jar    jndi.jar             libPgmIpLayer.so
CL3Nonexport.jar       com.ibm.mq.jar        com.ibm.mq.postcard.jar   fscontext.jar  jta.jar              OSGi
com.ibm.mq.axis2.jar           com.ibm.mq.jmqi.jar        com.ibm.mq.soap.jar       jca            ldap.jar             providerutil.jar
com.ibm.mq.commonservices.jar  com.ibm.mqjms.jar          com.ibm.mq.tools.ras.jar  jdbc           libmqjbnd.so         rmm.jar

com.ibm.mq.defaultconfig.jar com.ibm.mq.jms.Nojndi.jar connector.jar jms.jar libmqjexitstub02.so soap
[root@durga lib]#

After that could successfully re-start configmgr.

Code:
[durga@durga ~]$ mqsistart CMGR01
WebSphere MQ queue manager running.
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

Jul 23 02:30:13 durga WebSphere Broker v6102[12520]: (CMGR01)[1]BIP8873I: Starting the component verification for component 'CMGR01'. : CMGR01.mqsistart: /build/S610_P/src/CommandLine/ImbCmdLib/ImbComponentVerification.cpp: 74: ImbComponentVerification::verify: :
Jul 23 02:30:14 durga WebSphere Broker v6102[12541]: (CMGR01)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6102; process ID 12546. : CMGR01.service: /build/S610_P/src/AdminAgent/ControlProcess/Linux/ImbControlService.cpp: 345: ImbControlService::StartNewAA: :
Jul 23 02:30:17 durga WebSphere Broker v6102[12546]: (CMGR01)[1]BIP8255I: User Name Services are disabled. : CMGR01.agent: /build/S610_P/src/UserGroup/UGClient/ImbSecClient.cpp: 101: ImbSecClient::ImbSecClient: :
Jul 23 02:30:19 durga WebSphere Broker v6102[12546]: (CMGR01)[1]BIP1003I: The Configuration Manager is available for use. : CMGR01.agent: /build/S610_P/src/Config/ImbConfigMgrAgent.cpp: 713: ImbConfigMgrAgent::employJavaConfigManager: :
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Configuration Manager stops when connecting to Toolkit
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.