You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/03/01 08:35:45 UTC

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

     [ https://issues.apache.org/jira/browse/CAMEL-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-10912:
--------------------------------
    Summary: camel-sjms - Session object created from connection that gets closed  (was: Session object created from connection that gets closed)

> 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
>
> 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
(v6.3.15#6346)