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 » WebSphere Message Broker (ACE) Support » dead letter header

Post new topic  Reply to topic
 dead letter header « View previous topic :: View next topic » 
Author Message
Nizam
PostPosted: Thu May 13, 2004 10:08 am    Post subject: dead letter header Reply with quote

Disciple

Joined: 10 Feb 2004
Posts: 160

Hi,
I see the following message in my Dead Letter Queue everytime I start my machine.
I am using mq 5.3 and wbimb 5.0 on windows 2000 pro...
44 4C 48 20 00 00 00 01 DLH ....
00 00 00 00 53 59 53 54 ....SYST
45 4D 2E 42 52 4F 4B 45 EM.BROKE
52 2E 41 44 4D 49 4E 2E R.ADMIN.
52 45 50 4C 59 00 00 00 REPLY...
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 43 43 43 2E ....CCC.
53 4D 41 52 52 49 2E 44 SMARRI.D
45 56 00 00 00 00 00 00 EV......
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 02 22 ......."
00 00 04 B8 20 20 20 20 ...¸
20 20 20 20 00 01 00 00 ....
4D 51 53 65 72 69 65 73 MQSeries
49 6E 74 65 67 72 61 74 Integrat
6F 72 32 00 00 00 00 00 or2.....
00 00 00 00 32 30 30 34 ....2004
30 35 31 32 31 36 34 35 05121645
30 32 30 30 3C 42 72 6F 0200<Bro
6B 65 72 20 75 75 69 64 ker uuid
3D 22 61 32 34 64 64 35 ="a24dd5
31 32 2D 66 63 30 30 2D 12-fc00-
30 30 30 30 2D 30 30 38 0000-008
30 2D 66 30 35 31 31 38 0-f05118
64 38 38 63 33 65 22 20 d88c3e"
6C 61 62 65 6C 3D 22 43 label="C
43 43 42 52 4B 22 20 76 CCBRK" v
65 72 73 69 6F 6E 3D 22 ersion="
31 22 3E 3C 4F 76 65 72 1"><Over
61 6C 6C 43 6F 6D 70 6C allCompl
65 74 69 6F 6E 43 6F 64 etionCod
65 20 72 65 73 75 6C 74 e result
3D 22 66 61 69 6C 75 72 ="failur
65 22 3E 3C 4C 6F 67 45 e"><LogE
6E 74 72 79 20 63 61 74 ntry cat
61 6C 6F 67 3D 22 42 49 alog="BI
50 76 35 30 30 22 20 6E Pv500" n
75 6D 62 65 72 3D 22 32 umber="2
30 38 37 22 3E 3C 49 6E 087"><In
73 65 72 74 20 74 79 70 sert typ
65 3D 22 73 74 72 69 6E e="strin
67 22 20 74 65 78 74 3D g" text=
22 43 43 43 42 52 4B 22 "CCCBRK"
2F 3E 3C 49 6E 73 65 72 /><Inser
74 20 74 79 70 65 3D 22 t type="
73 74 72 69 6E 67 22 20 string"
74 65 78 74 3D 22 61 32 text="a2
34 64 64 35 31 32 2D 66 4dd512-f
63 30 30 2D 30 30 30 30 c00-0000
2D 30 30 38 30 2D 66 30 -0080-f0
35 31 31 38 64 38 38 63 5118d88c
33 65 22 2F 3E 3C 2F 4C 3e"/></L
6F 67 45 6E 74 72 79 3E ogEntry>
3C 2F 4F 76 65 72 61 6C </Overal
6C 43 6F 6D 70 6C 65 74 lComplet
69 6F 6E 43 6F 64 65 3E ionCode>
3C 45 78 65 63 75 74 69 <Executi
6F 6E 47 72 6F 75 70 43 onGroupC
6F 6D 70 6C 65 74 69 6F ompletio
6E 43 6F 64 65 20 75 75 nCode uu
69 64 3D 22 32 63 37 64 id="2c7d
30 31 37 35 2D 66 63 30 0175-fc0
30 2D 30 30 30 30 2D 30 0-0000-0
30 38 30 2D 39 36 39 64 080-969d
38 62 61 38 35 63 33 61 8ba85c3a
22 20 72 65 73 75 6C 74 " result
3D 22 75 6E 6B 6E 6F 77 ="unknow
6E 22 3E 3C 4C 6F 67 45 n"><LogE
6E 74 72 79 20 63 61 74 ntry cat
61 6C 6F 67 3D 22 42 49 alog="BI
50 76 35 30 30 22 20 6E Pv500" n
75 6D 62 65 72 3D 22 32 umber="2
30 36 36 22 3E 3C 49 6E 066"><In
73 65 72 74 20 74 79 70 sert typ
65 3D 22 73 74 72 69 6E e="strin
67 22 20 74 65 78 74 3D g" text=
22 43 43 43 42 52 4B 22 "CCCBRK"
2F 3E 3C 49 6E 73 65 72 /><Inser
74 20 74 79 70 65 3D 22 t type="
73 74 72 69 6E 67 22 20 string"
74 65 78 74 3D 22 61 32 text="a2
34 64 64 35 31 32 2D 66 4dd512-f
63 30 30 2D 30 30 30 30 c00-0000
2D 30 30 38 30 2D 66 30 -0080-f0
35 31 31 38 64 38 38 63 5118d88c
33 65 22 2F 3E 3C 49 6E 3e"/><In
73 65 72 74 20 74 79 70 sert typ
65 3D 22 73 74 72 69 6E e="strin
67 22 20 74 65 78 74 3D g" text=
22 61 63 68 61 76 65 7A "achavez
22 2F 3E 3C 49 6E 73 65 "/><Inse
72 74 20 74 79 70 65 3D rt type=
22 73 74 72 69 6E 67 22 "string"
20 74 65 78 74 3D 22 33 text="3
36 30 22 2F 3E 3C 2F 4C 60"/></L
6F 67 45 6E 74 72 79 3E ogEntry>
3C 2F 45 78 65 63 75 74 </Execut
69 6F 6E 47 72 6F 75 70 ionGroup
43 6F 6D 70 6C 65 74 69 Completi
6F 6E 43 6F 64 65 3E 3C onCode><
45 78 65 63 75 74 69 6F Executio
6E 47 72 6F 75 70 20 75 nGroup u
75 69 64 3D 22 32 63 37 uid="2c7
64 30 31 37 35 2D 66 63 d0175-fc
30 30 2D 30 30 30 30 2D 00-0000-
30 30 38 30 2D 39 36 39 0080-969
64 38 62 61 38 35 63 33 d8ba85c3
61 22 2F 3E 3C 2F 42 72 a"/></Br
6F 6B 65 72 3E oker>



Could you please tell me what it is..
thanks
Back to top
View user's profile Send private message
JT
PostPosted: Thu May 13, 2004 12:18 pm    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Quote:
61 6C 6F 67 3D 22 42 49 alog="BI
50 76 35 30 30 22 20 6E Pv500" n
75 6D 62 65 72 3D 22 32 umber="2
30 36 36 22 3E 3C 49 6E 066"><In

From the V5.0 Information Center on BIP2066:
Quote:
Explanation
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.

Response
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere MQ log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.
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 » WebSphere Message Broker (ACE) Support » dead letter header
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.