|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
AMQ8043, trying to connect to AIX MQ5.2 |
« View previous topic :: View next topic » |
Author |
Message
|
MWChapel |
Posted: Tue Aug 28, 2001 10:00 am Post subject: |
|
|
Newbie
Joined: 27 Aug 2001 Posts: 1
|
when tying to connect to an AIX 5.2MQ i get this stack trace:
2001.08.27 11:13:20.829 com.tivoli.tes.server.mqseries.MQServerManager addRemoteChildHelper LocalCLI Handler mqtest1/mms
moke1.dev.tivoli.com_9990 security/SuperAdministrators/John D. Super com.ibm.mq.MQException: Completion Code 2, Reason
2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:166)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.j
ava:196)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.ja
va:213)
at com.ibm.mq.StoredManagedConnection.(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:150)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:560)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:509)
at com.ibm.mq.MQQueueManager.(MQQueueManager.java:330)
at com.tivoli.tes.server.mqseries.TESQueueManager.(TESQueueManager.java:82)
at com.tivoli.tes.server.mqseries.ManagedQMNode.getQueueManager(ManagedQMNode.java:688)
at com.tivoli.tes.server.mqseries.ManagedQMNode.getConfig(ManagedQMNode.java:653)
at com.tivoli.tes.server.mqseries.ManagedQMNode.setupQueueManager(ManagedQMNode.java:122)
at com.tivoli.tes.server.mqseries.ManagedQMNode.(ManagedQMNode.java:106)
at com.tivoli.tes.server.mqseries.MQServerManager.addRemoteChildHelper(MQServerManager.java:912)
at com.tivoli.tes.server.mqseries.MQServerManager.addRemoteChild(MQServerManager.java:389)
On the server AMQERR01.LOG I get this message:
08/28/01 11:16:56
AMQ8043: Non runtime application attempted to connect to runtime only queue
manager.
EXPLANATION:
A non runtime application attempted to connect to a queue manager on a node
where support for non runtime applications has not been installed. The connect
attempt will be rejected with a reason of MQRC_ENVIRONMENT_ERROR.
ACTION:
If the node is intended to support only runtime applications, investigate why a
non runtime application has attempted to connect to the queue manager. If the
node is intended to support non runtime only applications, investigate if the
base option has been installed. The base option must be installed if non
runtime applications are to run on this node.
-------------------------------------------------------------------------------
and this message:
AMQ6174: The library /usr/mqm/lib/amqzxmr0 was not found. The queue manager
will continue without this module.
EXPLANATION:
The dynamically loadable file /usr/mqm/lib/amqzxmr0 was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
-------------------------------------------------------------------------------
I'm not sure what im missing, I run the same codepath against a Windows 2000 MQServer install and it works just fine, only when i run it against the AIX server.
these are the packages i have installed on the server:
mqm.Client.Bnd 5.2.0.0 C MQSeries Client Bundle
mqm.Server.Bnd 5.2.0.0 C MQSeries Server Bundle
mqm.base.runtime 5.2.0.0 C MQSeries Runtime for Client and
Server
mqm.base.samples 5.2.0.0 C MQSeries Samples
mqm.base.sdk 5.2.0.0 C MQSeries Base Kit for Client and
Server
mqm.client.rte 5.2.0.0 C MQSeries Client for AIX
mqm.gateway.rte 5.2.0.0 C MQSeries Internet Gateway -
Runtime
mqm.gateway.rte.data 5.2.0.0 C MQSeries Internet Gateway -
mqm.msg.en_US 5.2.0.0 C MQSeries Messages - U.S. English
mqm.server.rte 5.2.0.0 C MQSeries Server
mqjava.base 5.2.0.0 C MQSeries classes for Java
mqjava.jms 5.2.0.0 C MQSeries classes for Java
Message Service
any help would be appreciated.....
|
|
Back to top |
|
 |
bower5932 |
Posted: Tue Aug 28, 2001 1:20 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
A co-worker of mine was having the same problem. She had to do the following to get around it:
- logon as root
- make sure no MQSeries processes are running
(ps -ef | grep -i mq)
- remove all semaphores that show root:mqm or mqm:mqm ownership
(to show: ipcs -s | grep mqm, to remove: ipcrm -s xxxx where xxxx is
the semaphore id)
- logoff as root
- re-install the code
My co-worker re-ipled in between the logoff and re-install. I
don't think it is necessary. |
|
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
|
|
|
|