File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes system.dead.letter.queue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "system.dead.letter.queue" Watch "system.dead.letter.queue" New topic
Author

system.dead.letter.queue

Moi Tinh
Greenhorn

Joined: Mar 05, 2005
Posts: 16
I'm using Websphere App server and MQ 5.3 with fix pack #7 on HP-UX. When I tried to put a message into the remote queue using jms, it put the message into the system.dead.letter.queue instead. I tried to use amqsput and it sent the message successfully so that means the connection is correct. I stopped the sender channel and tried to send the messages. I was able to see them in the transmission queue. The minute I turned the sender channel on, the messages are gone and they are in the dead letter queue.

I was able to send the message using jms on windows and it worked fine. The code is unchanged. Any ideas?
Ken Loh
Ranch Hand

Joined: Feb 16, 2005
Posts: 190
It would help if you could submit some code to start with.

Originally posted by Moi Tinh:
I'm using Websphere App server and MQ 5.3 with fix pack #7 on HP-UX. When I tried to put a message into the remote queue using jms, it put the message into the system.dead.letter.queue instead. I tried to use amqsput and it sent the message successfully so that means the connection is correct. I stopped the sender channel and tried to send the messages. I was able to see them in the transmission queue. The minute I turned the sender channel on, the messages are gone and they are in the dead letter queue.

I was able to send the message using jms on windows and it worked fine. The code is unchanged. Any ideas?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: system.dead.letter.queue