This week's book giveaway is in the Performance forum.
We're giving away four copies of The Java Performance Companion and have Charlie Hunt, Monica Beckwith, Poonam Parhar, & Bengt Rutisson on-line!
See this thread for details.
Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

mule 2.0 and JMS endpoint

 
Sander Evanfield
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When using mule 2.0, need to handle poison message for a jms endpoint. Mule goes to infinite loop

My configuration files are:

jms:endpoint name="someChannel" queue="${some.q}" connector-ref="EMSConnector"
synchronous="true">

jms:connector name="EMSConnector" acknowledgementMode="DUPS_OK_ACKNOWLEDGE" durable="false"
noLocal="true" persistentDelivery="true" maxRedelivery="3" cacheJmsSessions="true" eagerConsumer="false"
specification="1.1" connectionFactory-ref="EMSConnectionFactory" username="${ems.usr.name}" password="${ems.usr.passwd}"
redeliveryHandlerFactory-ref="RedeliveryHandlerFactory" createMultipleTransactedReceivers="false"
numberOfConcurrentTransactedReceivers="1">
<spring:property name="exceptionListener" ref="OMSExceptionStrategy"/>
</jms:connector>

<spring:bean name="RedeliveryHandlerFactory" class="org.mule.transport.jms.CountingRedeliveryHandlerFactory" />

spring:bean name="EMSConnectionFactory" class="com.tibco.tibjms.TibjmsQueueConnectionFactory">
<spring:constructor-arg value="${ems.host.name}" />
</spring:bean>

How can I redesign this to handle a poison message and prevent infinite loop.



 
Roger Sterling
Ranch Hand
Posts: 426
Eclipse IDE Fedora Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sander Evanfield wrote:When using mule 2.0, need to handle poison message for a jms endpoint. Mule goes to infinite loop

...

How can I redesign this to handle a poison message and prevent infinite loop.



You might check with the SOA ESB guys over at soabus.org

Other than that , you could use

<number-of-retries>3</number-of-retries>
<retry-wait>2000</retry-wait>

or equivalent for Tibco.


You might consider other messaging platforms : Active MQ, WMQ, etc. as your JMS provider.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic