mule 2.0 and JMS endpoint

[Sander Evanfield]

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.