Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 28 Apr 2016 08:46:12 +0000 (UTC)
From: "Catalina-Alina Dobrica (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12962933.1461747481000.56986.1461833172889@Atlassian.JIRA>
In-Reply-To: <JIRA.12962933.1461747481000@Atlassian.JIRA>
References: <JIRA.12962933.1461747481000@Atlassian.JIRA>
 <JIRA.12962933.1461747481071@arcas>
Subject: [jira] [Commented] (CAMEL-9916) SJMS component is not currently
 nodev/XML route compatible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Catalina-Alina Dobrica commented on CAMEL-9916:
-----------------------------------------------

What I actually should have said is "on context restart".
If you stop only the routes and restart them, the pool is not closed, but in the use-case where I needed the feature, the entire context is restarted (by stop then start) when you want to restart a route, which causes the component to restart and it's pool to be closed.

> SJMS component is not currently nodev/XML route compatible
> ----------------------------------------------------------
>
>                 Key: CAMEL-9916
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9916
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-sjms
>            Reporter: Catalina-Alina Dobrica
>
> SJMS component is currently not friendly for XML route usage because:
> * You need a component instance which has been "activated" - has had a connection factory set.
> * On route restart, the component cannot be reused because the underlying pool is closed and not recreated


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)