Ok, I'll watch that issue.
Broadening the scope of the discussion a bit, is SJMS designed for Java
SE, Java EE or both?
In a Java EE 6/7 server, you get managed connections from a JCA resource
adapter, pooling and reconnection is provided by the container, so
there's no need to add reconnection to SJMS, and the pooling implemented
in SJMS may be either redundant or even in conflict with connection
pooling in the container.
Would it make sense to implement Java EE-optimized behaviour in
camel-sjms, activated by a bunch of new options?
Or would this be a case for a new camel-jmsee component?
Regads,
Harald
Am 09.11.2013 17:33, schrieb Raul Kripalani:
Yes, exactly. JIRA: https://issues.apache.org/jira/browse/CAMEL-6950.
