Show the ID of a consumer that has received or processed a message
The JMSQSEQCONSUMER cron task reads from a continuous queue that already has an active Message Driven Bean. This setup can lead to duplicate message processing, messages being processed hours or days after initial processing, and confusing and misleading entries in the Message Tracking application.
The JMSQSEQCONSUMER cron task reads from a continuous queue that already has an active Message Driven Bean. This setup can lead to duplicate message processing, messages being processed hours or days after initial processing, and confusing and misleading entries in the Message Tracking application.