[jira] [Commented] (CAMEL-10912) camel-sjms - Session object created from connection that gets closed

["Sumeet (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579898#comment-16579898 ] 

Sumeet commented on CAMEL-10912:
--------------------------------

As per the above comments, this should have been fixed in Apache Camel 2.19.x.

But, I am experiencing the exact same issue with Camel 2.20.2 and ActiveMQ Artemis 2.4.0. 

Any pointers on how to resolve it are appreciated.

> camel-sjms - Session object created from connection that gets closed
> --------------------------------------------------------------------
>
>                 Key: CAMEL-10912
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10912
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sjms
>    Affects Versions: 2.18.2
>            Reporter: Ryan Yeats
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 2.19.0
>
>
> This is not easy to reproduce I haven't been able to simplify it down from our code to recreate it but I can reliably cause it to happen.  Basically if you hit a camel-sjms route with a spike of load from nothing and have a bunch of .toD("dynamic-${route}") it can create more connections than the pool allows then when a connection is returned it is closed and one of the routes will be using a session with a closed connection and will not work until it is restarted.
> The code in question:
> https://github.com/apache/camel/blob/camel-2.18.x/components/camel-sjms/src/main/java/org/apache/camel/component/sjms/producer/InOnlyProducer.java#L51-L67



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)