Details
-
Feature Request
-
Status: Resolved (View Workflow)
-
Major
-
Resolution:
Out of Date
-
0.8
-
None
-
None
Description
JCA JMSProcessor should have the ability to :
1) send a configurable type of JMS message (Object, text, byte) to a remote destination that is not registered in the local JNDI naming directory. Doing so probably necessitates use of proprietary Hornetq client libraries
2) optionally set the proprietary Hornetq String property that indicates to the Hornetq broker to track for possible duplicate messages to ensure idempotent operation
3) handle (in a configurable manner) JMSExceptions thrown by the Hornetq connection when broker fail-over occurs as per the Hornetq documentation. As an example, when a JMSException is thrown by the Hornetq client that includes content of either:
a) "Unblocking a blocking call that will never get a response"
b) "Timed out waiting for response when sending packet"
then the JMSProcessor should catch the exception and offer the ability to re-send the message a configurable # of times.