| Author |
Message
|
| waso |
 Posted: Mon Apr 21, 2008 1:58 am Post subject: Can't see messages in the queue |
 |
|
Newbie
Joined: 21 Apr 2008
Posts: 3
|
Hello
I have following problem. I have two queues: "testq" and "dead.letter.queue". Second queue is used as a backout requeue queue for "testq". When some error occur on processing message from "testq" then this poison message is being moved to "dead.letter.queue". But the problem is when I'm trying to get all messages from this "dead.letter.queue" or brows them in WebSphere Explorer I can't see any message (but the queue depth is more then 0 so there are some messages there).
Another issue is that these msgs are retrieved by ESB and when I kill the ESB (servicemix) all msgs from "dead.letter.queue" are moved automatically to "testq" (I don't know why). After ESB starts, all messages ale moved back from "testq" to "dead.letter.queue".
Can you help me and describe how I can solve this issue and see all messages in "dead.letter.queue"?
Thanks
Waldemar |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon Apr 21, 2008 2:07 am Post subject: Re: Can't see messages in the queue |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| waso wrote: |
Can you help me and describe how I can solve this issue and see all messages in "dead.letter.queue"?
|
you cant able to read dead.letter.queue, as how you are reading the loacal queues.
you have to use amqsdlq for retreving the msgs from the queue now, or you have to develop your own application to do so.
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24000676&loc=en_US&cs=utf-8&lang=en
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 21, 2008 2:12 am Post subject: Re: Can't see messages in the queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| waso wrote: |
| I have following problem. I have two queues: "testq" and "dead.letter.queue". Second queue is used as a backout requeue queue for "testq". |
I hope you don't mean the dead letter queue in the WMQ sense - just a local queue with a misleading name. A "dead letter queue" means something quite specific, and not a backout queue.
| waso wrote: |
| When some error occur on processing message from "testq" then this poison message is being moved to "dead.letter.queue". But the problem is when I'm trying to get all messages from this "dead.letter.queue" or brows them in WebSphere Explorer I can't see any message (but the queue depth is more then 0 so there are some messages there). |
Are you sure whatever's moving them (presumably an app server or Java construct) is committing them? Uncommitted messages show in the count but can't be retrieved by normal methods.
| waso wrote: |
| Another issue is that these msgs are retrieved by ESB and when I kill the ESB (servicemix) all msgs from "dead.letter.queue" are moved automatically to "testq" (I don't know why). After ESB starts, all messages ale moved back from "testq" to "dead.letter.queue". |
Presumably it thinks you've fixed the problem and is having another go at the messages for you.
| waso wrote: |
Can you help me and describe how I can solve this issue and see all messages in "dead.letter.queue"?
|
Fix the syncpoint issues most probably, and ensure this queue isn't actually the dead letter queue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 21, 2008 2:14 am Post subject: Re: Can't see messages in the queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gaya3 wrote: |
| waso wrote: |
Can you help me and describe how I can solve this issue and see all messages in "dead.letter.queue"?
|
you cant able to read dead.letter.queue, as how you are reading the loacal queues.
|
If it's only the backout queue for a local queue, no message will have a DLH on it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| waso |
| Posted: Mon Apr 21, 2008 3:23 am Post subject: Re: Can't see messages in the queue |
|
|
Newbie
Joined: 21 Apr 2008
Posts: 3
|
| Vitor wrote: |
Are you sure whatever's moving them (presumably an app server or Java construct) is committing them? Uncommitted messages show in the count but can't be retrieved by normal methods.
|
From what I understand, WMQ is moving them automatically. My app isn't responsible for sending them to this dead.letter.queue, because "backout requeue queue" (exact name from WebSphere explorer) is configured on WMQ side in properties for "testq" queue.
If these messages are uncommitted/etc then for my this is a problem on WMQ side (maybe I miss some configuration option, etc).
Waldemar |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 21, 2008 3:37 am Post subject: Re: Can't see messages in the queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| waso wrote: |
| From what I understand, WMQ is moving them automatically. My app isn't responsible for sending them to this dead.letter.queue, because "backout requeue queue" (exact name from WebSphere explorer) is configured on WMQ side in properties for "testq" queue. |
You understand incorrectly. WMQ holds the configuration details, as you see them in the Explorer, but doesn't use them itself. It will be the app server, JMS application or some other construct doing the work. Please give some details of your app & where it runs (if it's not under an app server or using JMS) and that might pin down what's doing it.
| waso wrote: |
If these messages are uncommitted/etc then for my this is a problem on WMQ side (maybe I miss some configuration option, etc).
|
It's a problem on the app side not committing the messages. See my comments above re: identifying what's doing the move. Also please describe what processing takes place when a message is identified as being poision; is this done by trapping a Java exception, or by content? How is the unit of work handled for a backout? WMQ itself won't identify a poison message so what does? It's in there your problem lies.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| waso |
| Posted: Mon Apr 21, 2008 4:40 am Post subject: |
|
|
Newbie
Joined: 21 Apr 2008
Posts: 3
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 21, 2008 4:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Yes - that link is the app server info centre, not the WMQ one. I've been saying throughout this post that an app server is moving your message to the backout queue, not WMQ. This link describes the settings & so forth within app server, and the view of the WMQ configuration which it has & can configure within app server.
It sounds like this FUSE ESB (of which I've no knowledge) isn't committing the unit of work properly. Or the app server is not properly syncronising with the queue manager in some way.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
