| Author |
Message
|
| fatima |
 Posted: Mon Nov 22, 2010 12:08 am Post subject: Messages on Dead Letter Queue Reason Code 65536 |
 |
|
Newbie
Joined: 30 Sep 2009
Posts: 7
|
Hi,
The current environment is as follows:
| Code: |
Hardware O/S Platform
VMWARE
SUSE Linux Enterprise Server 10 on x86-64
Solaris 10 on SPARC
Runtime Environment
MQ V7.0.1.2
IBM Message Broker Message Broker 6.1.0.5
Oracle 10.2.0.2 Base with patch 10.2.0.3
|
We have just upgraded Message Broker and MQ as follows:
| Code: |
FROM
IBM Message Broker Message Broker 6.1.0.1
TO
IBM Message Broker Message Broker 6.1.0.5
FROM
MQ V7.0
TO
MQ V7.0.1.2
We have also introduced SUPPORT PACK ma01 to write messages from a Queue to File as a Cron Job that runs once a day.
Remote Queue definitions were changed from Remote to Local.
These Queues are used for logging messages.
|
Message Broker was able to write the messages to the various log Queues without any problem.
Since the changes mentioned above we are experiencing problems.
| Code: |
Observations:
Message Broker successfully processes the message and writes the message to the Log Queues.
Messages are then immediately taken from the Log Queues and written to a user defined Dead Letter Queue
|
In the MQDEAD Header field the following can be seen:
Reason Code: 65536
Put-Application Name: WebSphereMQIntegrator6
The are no errors reported in the following logs:
1. Syslog
2. MQ Log
2. Trace file in the Message Broker flow attached to the catch terminal used to report errors.
I need a more descriptive explanation of the error in order to solve the problem.
Kindly advise
Thanks
Fatima |
|
| Back to top |
|
 |
| ramires |
| Posted: Mon Nov 22, 2010 3:40 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 22, 2010 4:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The only thing that will take a message from a queue and put it on another queue is an application.
Is there an IPPROC on the destination queue? What program? Does the LOG queues have backout queues defined? |
|
| Back to top |
|
|
| fatima |
| Posted: Mon Nov 22, 2010 5:21 am Post subject: Messages on Dead Letter Queue Reason Code 65536 |
|
|
Newbie
Joined: 30 Sep 2009
Posts: 7
|
Hello,
Thank you for all your responses
The good news we found our problem.
An execution group that has nothing to do with the queues has attached itself to the Queues and wants to process the messages on the Qs sending them off TO the user defined Dead Letter Queue.
Broker was bounced several times on the week-end to help resolve the
problem, but that has not helped. We even closed the connection in
MQ that causes the problem, but then it just starts up again.
So we thinking of bouncing the execution group and see if it happens
again, if yes then we delete the execution group and re-create the
execution group again.
Why does this happen though? 
Thank You,
Fatima |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 22, 2010 5:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The only reason an ExecutionGroup would open a queue would be because someone deployed a flow to that EG that opened those queues. |
|
| Back to top |
|
|
| fatima |
| Posted: Fri Dec 03, 2010 4:12 am Post subject: Messages on Dead Letter Queue Reason Code 65536 |
|
|
Newbie
Joined: 30 Sep 2009
Posts: 7
|
Hello,
The solution to the problem was as follows:
1. Stop all flows running in the Execution Group
2. Remove all deployed children from Execution Group
3. Delete the Execution Group
4. Deploy flows to Execution Group again
MqJeff there were no flows deployed using that Qs in that Execution Group
Thank You,
Fatima |
|
| Back to top |
|
|
|
|
