For customers sometimes it is an important feature to know the delivery count of the message.
Following are instances messages are redelivered from the broker.
if client rollbacked the session (on a transacted session)
recover the session before acknowledging
application did not acknowledge, client will send NAC upon ack time out.
JMS 2.0 brings up a solution by introducing standard Int type header called JMSXDeliveryCount. It can be used by JMS 1.1 applications as well because, both APIs have the ability to read the JMS header properties.
In WSO2 EI this property can be read as a transport level header in an incoming message from Axis2 JMS Transport or Inbound JMS Transport.
For customers sometimes it is an important feature to know the delivery count of the message. Following are instances messages are redelivered from the broker.
if client rollbacked the session (on a transacted session) recover the session before acknowledging application did not acknowledge, client will send NAC upon ack time out. JMS 2.0 brings up a solution by introducing standard Int type header called JMSXDeliveryCount. It can be used by JMS 1.1 applications as well because, both APIs have the ability to read the JMS header properties.
In WSO2 EI this property can be read as a transport level header in an incoming message from
Axis2 JMS TransportorInbound JMS Transport.Fixes: https://github.com/wso2/product-ei/issues/4636 Port: https://github.com/wso2-support/andes/pull/197