ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » messages in DLQ

Post new topic  Reply to topic
 messages in DLQ « View previous topic :: View next topic » 
Author Message
saneben
PostPosted: Wed Mar 16, 2005 4:15 am    Post subject: messages in DLQ Reply with quote

Voyager

Joined: 04 Apr 2004
Posts: 96
hi,

We have installed Websphere MQ v5.3 on AIX 5.1 on production. The communication is establised with an existing QM on MQseries V 5.2 Solaris 8. and messages are received & sent successfully. Sometimes we have observed that the some messages written on the system.dead.letter queue. Should we need to apply any CSD for the AIX system ? And any idea why these messages are going to the DLQ?


Regards
Sanjiv

MQGET of message number 2
****Message descriptor****

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1089
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D51205354454C494E4B202020202042354C8920003906'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'STELINK '
** Identity Context
UserIdentifier : ' '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '7'
PutApplName : 'STELINK '
PutDate : '20050315' PutTime : '12145840'
ApplOriginData : ' '

GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'

**** Message ****

length - 856 bytes

00000000: 444C 4820 0000 0001 0000 0109 5359 5354 'DLH ........SYST'
00000010: 454D 2E44 4546 4155 4C54 2E49 4E49 5449 'EM.DEFAULT.INITI'
00000020: 4154 494F 4E2E 5155 4555 4520 2020 2020 'ATION.QUEUE '
00000030: 2020 2020 2020 2020 2020 2020 5354 454C ' STEL'
00000040: 494E 4B20 2020 2020 2020 2020 2020 2020 'INK '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 0441 4D51 5452 4947 2020 0000 0006 '...AMQTRIG ....'
00000080: 5255 4E4D 5154 524D 0000 0000 0000 0000 'RUNMQTRM........'
00000090: 0000 0000 0000 0000 0000 0000 3230 3035 '............2005'
000000A0: 3033 3135 3132 3135 3033 3434 544D 2020 '031512150344TM '
000000B0: 0000 0001 4342 535F 5354 4B5F 424D 5F54 '....CBS_STK_BM_T'
000000C0: 3234 5F53 594E 435F 494E 5F4C 5120 2020 '24_SYNC_IN_LQ '
000000D0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000000E0: 2020 2020 5354 4B5F 5245 515F 4841 4E44 ' STK_REQ_HAND'
000000F0: 4C5F 5052 4F43 4553 5320 2020 2020 2020 'L_PROCESS '
00000100: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000110: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000120: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000130: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000140: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000150: 2020 2020 0000 0006 2F6F 7074 2F73 6862 ' ..../opt/shb'
00000160: 7363 7269 7074 732F 6D71 7365 7269 6573 'scripts/mqseries'
00000170: 2F73 6372 6970 7473 2F73 746B 5F72 6571 '/scripts/stk_req'
00000180: 682E 7368 2020 2020 2020 2020 2020 2020 'h.sh '
00000190: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001A0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001B0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001C0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001D0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001E0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000001F0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000200: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000210: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000220: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000230: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000240: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000250: 2020 2020 2020 2020 2020 2020 2020 2020 ' '

00000260: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000270: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000280: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000290: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000002A0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000002B0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000002C0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000002D0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000002E0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
000002F0: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000300: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000310: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000320: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000330: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000340: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000350: 2020 2020 2020 2020 ' '
Back to top
View user's profile Send private message
Tibor
PostPosted: Wed Mar 16, 2005 5:56 am    Post subject: Reply with quote

Grand Master

Joined: 20 May 2001
Posts: 1033
Location: Hungary
Sanjiv,

The reason code is the third field in the DLH (Dead Letter Header) with value 0x0109 = 265. Its meaning is MQFB_APPL_CANNOT_BE_STARTED in a triggering step.

You can avoid this with setting an environment variable AMQ_SIGCHILD_ACTION=YES when this is not an application problem.

Other topic, e.g:
http://www.mqseries.net/phpBB2/viewtopic.php?t=11414

Tibor
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Mar 16, 2005 12:56 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
You need to set this environment variable in the shell that starts the trigger monitor.
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed Mar 16, 2005 1:18 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
Tibor wrote:
You can avoid this with setting an environment variable AMQ_SIGCHILD_ACTION=YES when this is not an application problem.


Assuming that it is not the triggered application that is failing, and this is a correct APPL_NOT_STARTED error, instead of a spurious error.

Some clever person wrote a FAQ on triggered applications.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » messages in DLQ
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.