| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9544 error |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sacha |
 Posted: Fri Jan 21, 2005 3:01 am Post subject: AMQ9544 error |
 |
|
Novice
Joined: 05 Dec 2004
Posts: 10
Location: Switzerland
|
Hello,
I'm trying to send message to a remote QM. unfortunately I have a AMQ9544 in the error log.
We are pretty sure of the Remote QM name and remote receive queue name (double-checked with our counter-part)
When I read the DLQ, I see my message, but I have no idea on how to read/decode the different fields.
Here is an example :
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D5120514D2E41303030303031202041F0D8F720000702'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QM.A000001 '
** Identity Context
UserIdentifier : 'mqm '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '28'
PutApplName : 'Websphere MQ Client for Java'
PutDate : '20050121' PutTime : '10315452'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 194 bytes
00000000: 444C 4820 0000 0001 0000 010F 2020 2020 'DLH ........ '
00000010: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000040: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 0333 4D51 5354 5220 2020 0000 0006 '...3MQSTR ....'
00000080: 7275 6E6D 7163 686C 5F6E 6420 2020 2020 'runmqchl_nd '
00000090: 2020 2020 2020 2020 2020 2020 3230 3035 ' 2005'
000000A0: 3031 3231 3130 3331 3534 3532 5445 5354 '012110315452TEST'
000000B0: 2054 4841 5420 5348 4F55 4C44 2057 4F52 ' THAT SHOULD WOR'
000000C0: 4B32 'K2 '
Last, I snooped my NIC and open the output with Ethereal. I have the following output :
time 0 : MESSAGE_DATA sent
time 0.07 : ACKnowledge from the remote server
time 1.01 : STATUS_DATA sent : "Confirm Request" control flag set
time 1.05 : STATUS_DATA received from the remote server : "DLQ used" set
time 1.05 : ACK sent
thanks for your help,
sacha |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Fri Jan 21, 2005 3:53 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The error in the DLH is 010F. You could have found this out for yourself by looking at the definition of the DLH in cmqc.h, and then loking for 271 in cmqc.h. This means MQFB_XMIT_Q_MSG_ERROR.
The reason for that is fairly clear to see. The msg itself has a format of MQSTR, which means that it must have been put directly to the xmitq. It should have been put to the remote queue. Please read the Intercomms manual, CH 4 WMQ distributed messaging techniques, for how to put msgs to remote qmgrs and queues. |
|
| Back to top |
|
|
| Sacha |
| Posted: Fri Jan 21, 2005 5:36 am Post subject: resolved |
|
|
Novice
Joined: 05 Dec 2004
Posts: 10
Location: Switzerland
|
hello,
thanks a lot for your quick answer.
you're right, we've been putting messages directly into our xmitq. |
|
| 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
|
|
|
|
