cancel
Showing results for 
Search instead for 
Did you mean: 

PI JMS-Adapter Error: Unable to write message to dead letter queue

Former Member
0 Kudos

Hi together,

we are communicating with an MQSeries-Queue. Using a JMS-Adapter as sender. Everything works fine except the case after a error on PI-side.

Scenario:

PI receives the messages from the jms-queue. 3-4 comm.channels are pointing to one queue. JMS-Message selector helps us to identify the messages for each comm.channel.

Everything works fine to this point.

But sometimes there is a problem on PI-side. PI tries to select the messages from the queue. Selection is ok. The oracle table space is full and the message could not be written in the database...no big deal..

The message is still in the JMS-Queue but PI knows now this message(MessageID...). After we solve the orable database problem PI is not processing the messages from the JMS-Queue. And the comm.channel has an error-status:

Channel error occured. Detailed error(if any): JMS error: MQJMS1079: Unable to write message to dead letter queue, Linked error: MQJE001: Completio Code 2, Reason 2098, Error Code: MQJMS1079.

After deleting the messages from the JMS-Queue everything works fine again.

How can we solve that issue without losing the messages in the JMS-Queue? Any ideas?

Is it possible on PI-Side?

Thanks

Serdar

Accepted Solutions (0)

Answers (1)

Answers (1)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Serdar

This error is probably due to a bug on the MQ side. There is a MQ fix, 6.0.2.0.9, which has resolved this error. I recommend you contact MQ support for further details on this (or try applying the above MQ fix).

Regards

Mark