|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Not able to connect to a QMGR |
« View previous topic :: View next topic » |
Author |
Message
|
mitul |
Posted: Tue Dec 28, 2004 9:11 am Post subject: Not able to connect to a QMGR |
|
|
Apprentice
Joined: 13 Jun 2002 Posts: 33
|
I have a QMgr created on an HP-UX machine.
I have a java application that tries to connect to the QMgr to get messages from the Q. Since the application is running on the same box, I am not specifying the hostname/port anywhere in the code.
I don't think that this also requires any configuration at the MQServer side.
Correct me if I am wrong.
When I try to run the code, it fails while trying to connect to the QMgr.
Fails with a reason code of 2059. i.e (QMGR NOT AVAILABLE)
But the QMgr is up and running. (verified with the dspmq command)
The id from which I am trying to run belongs to 'mqm' group. I have not given any explicit permissions on the QMgr and the other mq objects. Its just that I am part of mqm group as well as another group. So I think I have full access to my QMgr. Correct me if I am wrong.
I debugged the FDC and the ERR log created and here are the contents for the same -
/var/mqm/errors>vi AMQERR01.LOG
========================
Code: |
----- amqxfdcx.c : 671 --------------------------------------------------------
12/28/04 11:13:09
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3539.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 711 --------------------------------------------------------
|
/var/mqm/errors>AMQ03539.0.FDC
=======================
Code: |
+-----------------------------------------------------------------------------+
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- Tuesday December 28 11:13:02 EST 2004
Host Name :- lath06 (HP-UX B.11.11)
PIDS :- 5724B4102
LVLS :- 530.5 CSD05
Product Long Name :- WebSphere MQ for HP-UX
Vendor :- IBM
Probe Id :- XY079022
Application Name :- MQM
Component :- xtrAccessCtlMem
Build Date :- Sep 27 2003
CMVC level :- p530-05-L030926
Build Type :- IKAP - (Production)
UserID :- 00044017 (UNKNOWN)
Program Name :- java
Process :- 00003539
Thread :- 00000001
Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
Minor Errorcode :- OK
Probe Type :- MSGAMQ6119
Probe Severity :- 2
Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred
('13 - Permission denied' from shmat.)
FDCSequenceNumber :- 0
Arith1 :- 13 d
Comment1 :- '13 - Permission denied' from shmat.
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- Tuesday December 28 11:13:09 EST 2004
Host Name :- lath06 (HP-UX B.11.11)
PIDS :- 5724B4102
LVLS :- 530.5 CSD05
Product Long Name :- WebSphere MQ for HP-UX
Vendor :- IBM
Probe Id :- XC001009
Application Name :- MQM
Component :- xcsInitialize
Build Date :- Sep 27 2003
CMVC level :- p530-05-L030926
Build Type :- IKAP - (Production)
UserID :- 00044017 (UNKNOWN)
Program Name :- java
Process :- 00003539
Thread :- 00000001
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- xecI_S_NOT_INIT
Probe Type :- MSGAMQ6118
Probe Severity :- 2
Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred
(40806007)
FDCSequenceNumber :- 15
Arith1 :- 1082155015 40806007
+-----------------------------------------------------------------------------+
|
Surprisingly when I try to use the amsput and amqsget sample programs on the same QMgr and the Q, I am able to work fine with them.
This is what I am trying to do -
Code: |
if(qMgr!=null && qMgr.isConnected()) qMgr.disconnect();
qMgr = new MQQueueManager(in_managername);
|
Also I am trying to run the program like -
Code: |
nohup jreMQM -ms32m -mx128m -Djava.net.debug=all -Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB -D
org.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORBSingleton -DConfigFile=${GITD_RootDir}/resource/MQConfig.cfg -Dexceptionconfig=${GITD_RootDir}/resource/MQConfig.cfg cititru.interdict.mq.MQMessageHandler >>&! ${GITD_Dir}/logs/MQ.log &
|
Where jreMQM --> java
and cititru.interdict.mq.MQMessageHandler --> My Program
Pls help me in resolving this.
Thanks in advance.
Regards,
Mitul |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Dec 28, 2004 10:58 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
mitul |
Posted: Tue Dec 28, 2004 10:38 pm Post subject: |
|
|
Apprentice
Joined: 13 Jun 2002 Posts: 33
|
Peter,
Sorry for this. But actually I wasn't able to decide whether this is an administration issue or something wrong in my java program or the way I am running the Java program (memory heap and all).
Thats why I posted the message in both the forums -
1. General Support and
2. Java/JMS Support.
Regards,
Mitul |
|
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
|
|
|
|