Author |
Message
|
In_love_with_MQ |
Posted: Sat Nov 18, 2006 12:21 pm Post subject: Tool Kit always says bip0914e (eventhough QM AND LIS IS UP) |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
Hi ,
This issue seems to have been discussed a lot and i tried a lot of suggestions provided but no use .
Issue :
I have winXP prof and have WMB 6 and WMQ 6 ..
When i try to create a domain it always says bip0914e (QM DOWN OR LISTENER DOWN ) ..
Observations and TEST and certain suggestions from mqseries.net
=============================================
1)I am able to use RFHUTIL to connect to configmgr QMGR
SYSSTEM.BKR.CONFIG/TCP/localhost(1777)
so listener and QM is up
2) My settings are all correct hostname of localhost and port of 1777 on toolkit .
3) I tried some suggestions from mqseries.net
a) MCAUSER setting (No use)
b) createaclentry (no use)
c) start toolkit using command prompt and comainawareness = 0 etc (NO USE)
IS THIS ANY KNOWN BUG WHICH IS SOLVED IN SOME FIXES .
I HAVE SEEN MANY POSTS BUT NOTHING HAS ENDED IN SOME SOLUTIONS .
pLEASE LET ME KNOW IF ANYBODY HAS A SOLUTION . |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sat Nov 18, 2006 1:46 pm Post subject: Configmanager Proxy trace ... |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
com.ibm.broker.config.proxy.MQConnectionHelper.connectToMQ()
2006-11-18 21:32:19.0500 Thread-14...... { com.ibm.broker.config.proxy.MQConnectionHelper.connectToMQ()
2006-11-18 21:32:19.0515 Thread-14...... d[1]: MQSender
attempting to connect to XCM on host 'localhost:1777'...
2006-11-18 21:32:19.0578 Thread-14...... w: MQSender could not connect to the MQ Queue Manager; the Configuration Manager Proxy caught MQException reason code 2059
2006-11-18 21:32:19.0578 Thread-14...... com.ibm.broker.config.proxy.MQConnectionHelper.connectToMQ() threw an exception: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused. Stack trace follows.
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
As you can see the connection data being passes seems to be fine
attempting to connect to XCM on host 'localhost:1777'...
I dont understand why the failure of 2059 . XCM is running @ 1777 |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sat Nov 18, 2006 1:58 pm Post subject: i can connect to it via 5.o toolkit |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
I AM ABLE TO CONNECT TO THIS 6.0 CONFIG MANAGER using a 5.0 toolkit in the same machine .
So i beieve the toolkit 6.0 has some issue ......
Has anybody faced ths?????? |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sat Nov 18, 2006 3:04 pm Post subject: |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
TOOL KIT 6 TRACE
==================
09:32:19 [1163885539437] Thread: Thread-14, Object: com.ibm.mq.MQInternalCommunications@65bd65bd Queue Manager = ' '
TOOLKIT 5.0 TRACE
==============
09:59:41 [1163887181875] Thread: ModalContext, Object: com.ibm.mq.MQInternalCommunications@135074f1 Queue Manager = 'XCM '
In 6.0 trace , QM name is blank .
Why is this so .....
Any product developers or somebody who had faced these please let me know ... |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sat Nov 18, 2006 7:36 pm Post subject: HI |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
HI ,
ANY SUGGESTIONS ??????????? |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Nov 19, 2006 12:45 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
If you are using the toolkit 6.0 base I am not at all surprised. Upgrade to the latest fixpack for the toolkit and this too shall pass...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sun Nov 19, 2006 2:41 am Post subject: trying to upgrade to 6.0.0,2 |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
Hi
I am trying to Upgrade to 6.0.0.2 using RPU ...
I am seeing the longest upgradation in my life .........It is already 2 - 3 hours and still going on ......
Is there something wrong or RPU does it like this ... |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Nov 19, 2006 8:25 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
It does take a long time updating.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sun Nov 19, 2006 9:45 am Post subject: I am exahusted |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
Hi ,
After 4 hours long of upgradations ...
toolkit to 6.0.0.2 and brokes to csd 3
The error is still persisting ......
I am exhausted .........
IBM......................  |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sun Nov 19, 2006 10:11 am Post subject: trace after upgradation |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
Hi ,
I did a CMP trace and java client trace of toolkit and again i can see the same
05:41:45 [1163958105312] Thread: Thread-55, Object: com.ibm.mq.MQInternalCommunications@4b9c4b9c Queue Manager = ' '
QM name is blank .....
I tried to create another CMGR and tried to connect again the same error .
That means it is some bug as far i can see ....... |
|
Back to top |
|
 |
In_love_with_MQ |
Posted: Sun Nov 19, 2006 11:14 am Post subject: anybody has something to say abt this |
|
|
Acolyte
Joined: 10 Jul 2005 Posts: 70
|
Hi ,
Does anyone has something to say about this ?? |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Nov 19, 2006 2:31 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
PMR time  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|