Hi all,
I am using ActiveMQ within ServiceMix and sometimes messages are
succesfully enqueued but never get dequeued. Here are more info:
Versions/OS: fuse-esb-3.4.0.2 with JDK 1.6.0_17 on Solaris
I have configured 1 SU for enqueuing messages to a local(embedded?) queue
from an HTTP endpoint as followes:
<jms:endpoint service="mycompany:enqueuer"
endpoint="myProvider"
role="provider"
destinationStyle="queue"
jmsProviderDestinationName="OBJECT.SURROGATE"
connectionFactory="#connectionFactory" />
<amq:connectionFactory id="connectionFactory"
brokerURL="tcp://localhost:61616" />
And I have another SU for dequeuing messages from this queue and send to
another endpoint (a bean that process the message and persist it to
database)
<jms:consumer
service="mycompany:dequeuer"
endpoint="jms"
targetService="mycompany:DWPersist"
targetEndpoint="bean"
destinationName="OBJECT.SURROGATE"
connectionFactory="#pooledFactory" />
<amq:connectionFactory id="connectionFactory"
brokerURL="tcp://localhost:61616" />
<bean id="pooledFactory"
class="org.apache.activemq.pool.PooledConnectionFactory">
<property name="connectionFactory" ref="connectionFactory" />
</bean>
Messages often get enqueued/dequeued and processed successfully but
occasionally I could see that a message gets enqueued in the log but never
get dequeued (once that happened, any message after that will not be
dequeued either) I wonder if others have run into this issue and have a
solution.
BTW, I put this pair of SUs in-between the HTTP endpoint and the persistence
bean instead of having the HTTP endpoint sends to the bean directly because
I want the users of the HTTP endpoint to be able to use it asynchronously
rather than needing to wait for the completion of the persistence logic. We
also like the idea of having a queue that could be used for more
parallelized processing in the future. Am I using it correctly?
--
View this message in context:
http://old.nabble.com/Message-stuck-in-queue-tp27714279p27714279.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
