| Author |
Message
|
| texan |
 Posted: Thu Sep 08, 2005 7:30 am Post subject: Communicaton error |
 |
|
Acolyte
Joined: 25 Feb 2004
Posts: 74
|
We have a WF server installed on AIX box and Web client installed on another AIX. When I opened web client through URL, am getting following error:
FMC00013E Communication error - Failing Action: open, Reason Code: 2085, Failing Object: FMC.FMCGRP.EXE.
I have verified everything. This queue exists on Server and it is in FMCGRP cluster. Web client QM is also part of FMCGRP cluster.
When I checked AMQERROR01.log on web client, I am seeing following error:
AMQ9511: Messages cannot be put to a queue.
EXPLANATION:
The attempt to put messages to queue 'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue
manager 'QMXXXXXX' failed with reason code 2041.
ACTION:
Ensure that the required queue is available and operational.
Can anyone tell me whether this is causing a problem? |
|
| Back to top |
|
 |
| texan |
| Posted: Thu Sep 08, 2005 8:25 am Post subject: |
|
|
Acolyte
Joined: 25 Feb 2004
Posts: 74
|
I performed dis chs(*) on both client and server. Here is the output:
on Server:
AMQ8417: Display Channel Status details.
CHANNEL(SYSTEM.DEF.CLUSSDR) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME( ) CURRENT
CHLTYPE(CLUSSDR) STATUS(RETRYING)
RQMNAME(
on Client:
AMQ8417: Display Channel Status details.
CHANNEL(TO.FMCQM.TCP) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(xxxxxxxx(14000)) CURRENT
CHLTYPE(CLUSSDR) STATUS(STOPPED)
RQMNAME() |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Sep 08, 2005 8:29 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
From the manual for rc=2041:
| Quote: |
Object definition changed since opened.
Since the Hobj handle used on this call was returned by the MQOPEN call, object definitions that affect this object have been changed. See the MQSeries Application Programming Reference for more information.
This reason does not occur if the object handle is specified in the Context field of the PutMsgOpts parameter on the MQPUT or MQPUT1 call.
Corrective action: Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and retry the operation. However, if the object definitions are critical to the application logic, an MQINQ call can be used after reopening the object, to find out what has changed.
|
Maybe your should try recycling everything (mqwf, qmgrs). Just a suggestion....
_________________
-wayne |
|
| Back to top |
|
|
| texan |
| Posted: Thu Sep 08, 2005 8:33 am Post subject: |
|
|
Acolyte
Joined: 25 Feb 2004
Posts: 74
|
| I tried no. of times. but its not working. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Sep 08, 2005 7:32 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
To recreate default objects, try with -c option
|
|
| Back to top |
|
|
| muralihegde |
| Posted: Fri Sep 09, 2005 3:21 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi,
It looks more like connectivity issue.
1) At your client side, why is the channel TO.FMCQM.TCP in the status STATUS(STOPPED) ? Usually it would be inactive if not running.
Try starting this channel.
2) Also check why the channel on your server in RETRY status?
3) Try pinging the Client from Server and Server from server using the HOSTNAME (not just IP).
After you start both the channels then try recycling everything.
Hope this helps
-murali |
|
| Back to top |
|
|
| vinoth |
| Posted: Tue Sep 13, 2005 6:06 am Post subject: |
|
|
Apprentice
Joined: 03 Mar 2005
Posts: 31
|
i faced this problem, i tried lot of ways to make the SYSTEM.TRANSMIT.CLUSTER* run all went in vain......
action done to resolve is somewat strange , i took the back up of the QM deleted and recreated it , started all the channels, everything went fine...no issues till now.....
Vinoth |
|
| Back to top |
|
|
|
|
