Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 6 Mar 2012 21:49:58 +0000 (UTC)
From: =?utf-8?Q?Micha=C5=82_Warecki_=28Updated=29_=28JIRA=29?=
 <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <2096244900.29787.1331070598987.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1733734418.1744.1323709890654.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-4770) Add startAsync option to JMS consumer
 endpoint to allow route to be started, but the connection to the remote
 broker occurs async
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CAMEL-4770?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Micha=C5=82 Warecki updated CAMEL-4770:
----------------------------------

    Attachment:     (was: AsyncStartListener.patch)
   =20
> Add startAsync option to JMS consumer endpoint to allow route to be start=
ed, but the connection to the remote broker occurs async
> -------------------------------------------------------------------------=
--------------------------------------------------------
>
>                 Key: CAMEL-4770
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4770
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jms
>            Reporter: Claus Ibsen
>             Fix For: 2.10.0, 2.9.2
>
>         Attachments: AsyncStartListener2.patch
>
>
> This allows people to add routes which consumes from JMS destinations, by=
 which the consumer should start async in a separate thread, this ensures C=
amel will continue starting the route, and continue the code. Then the asyn=
s thread starts the JmsConsumer in the background. This is needed in case t=
he remote connection to the JMS broker does not work. But you want to signa=
l the route is started anyway, as the JMS consumer most likely support fail=
over and retry, so the connection may come online later.
> We may need to add some way to store a flag, so you from JMX can monitor =
if the JMS consumer is live or not.
> See nabble
> http://camel.465427.n5.nabble.com/Adding-JMS-route-may-block-if-remote-is=
-down-using-failover-connection-tp5037014p5037014.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira