Skip to Content
Apr 06, 2011 at 01:05 PM

JMS Dead Messages


Hi experts,

in our scenario we sent messages from PI to the local SAP WebAS JMS Provider (on the PI host and instance) through the JMS Adapter (JNDI). The consumer (BlackBoard) can consume the messages just fine when only a few messagess are put on the queue with some minutes in between. But when a large sum of messages is put on the queue, ready to be consumed in a matter of seconds, the consumer doesn't seem to be able to acknowledge the processed messages and a large number of messages remain on the queue (even though they have been consumed). The messages seem dead to the consumer.

Is this something that can be resolved with server side settings (building in delays for instance) and if so how? Or does it sound like a problem with the consumer software (custom code)?