camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3598) camel-jms - ListenerContainer should signal that running is not allowed when its being stopped
Date Fri, 28 Jan 2011 20:18:43 GMT

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

Christian Schneider commented on CAMEL-3598:
--------------------------------------------

Hi Claus,

I donĀ“t yet understand how this is related to the problem I had. My problem was that camel
hangs on startup when the failover is turned on in the connectionfactory and there is no broker
present.
I will debug my problem and check if runningAllowed would help

Christian


> camel-jms - ListenerContainer should signal that running is not allowed when its being
stopped
> ----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3598
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3598
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.7.0
>
>
> When you stop a JmsConsumer (also when using @Consume) we can detect this and signal
to Spring DefaultMessageListenerContainer in the {{runningAllowed}} method. This allows to
stop the listener faster and in a more graceful manner.
> For example ActiveMQ consumer is not likely configured with failover, and thus the listener
container will try to recover, even though we have asked the Consumer to stop.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message