[
https://issues.apache.org/jira/browse/CAMEL-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819133#comment-13819133
]
Harald Wellmann commented on CAMEL-6950:
----------------------------------------
As a proof of concept, I created a new component camel-sjmsee as a simplified
version of camel-sjms:
https://github.com/hwellmann/camel/tree/sjmsee/components/camel-sjmsee
Given that a Java EE container provides connection pools anyway, this component
does not pool any connections, producers or InOut reply consumers but creates
them on the fly (closing a managed connection simply returns it to the
container-managed pool). There is still a pool for ordinary consumers. Each
consumer registers an exception listener on its connection which removes the
consumer from the pool when an exception occurs. There is a reconnect task
submitted to the consumer's executor which tries to refill the pool every 10
seconds.
I've tested this manually on JBoss AS 7.2.0 in the context of my application. I
can now stop and restart the external ActiveMQ broker, and communication is
restored automatically.
If this approach makes sense, I'm happy to improve it and make an official
contribution. My main question is whether or not this should be a separate
component or be integrated into camel-sjms somehow.
> camel-sjms: Lacks reconnection logic in case of exception
> ---------------------------------------------------------
>
> Key: CAMEL-6950
> URL: https://issues.apache.org/jira/browse/CAMEL-6950
> Project: Camel
> Issue Type: Bug
> Components: camel-sjms
> Affects Versions: 2.12.1
> Reporter: Raul Kripalani
> Assignee: Raul Kripalani
>
> See this thread:
> http://camel.465427.n5.nabble.com/SJMS-failure-with-stale-reply-queue-tp5742833.html.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
