camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Moutray (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-12070) Orphaned AMQP Consumers
Date Thu, 11 Jan 2018 16:54:00 GMT

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

Ryan Moutray edited comment on CAMEL-12070 at 1/11/18 4:53 PM:
---------------------------------------------------------------

Ah, yes, this was investigated. However from what I could tell the CachingConnectionFactory
does not have a way to set start/stop. Additionally, the bundle that is starting/stopping
for us is not the bundle that contains the connection factory (which is in a separate common/core
bundle), it is the bundle with the Camel routes that creates the consumer.

The thought was that when a bundle with Camel amqp endpoints was restarted properly, it should
close the connection during shutdown. But it seems that this is not the design?


was (Author: rmoutray):
Ah, yes, this was investigated. However from what I could tell the CachingConnectionFactory
does not have a way to set start/stop. Additionally, the bundle that is starting/stopping
for us is not the bundle that contains the connection factory (which is in a separate common/core
bundle), it is the bundle with the Camel routes that creates the consumer.

The thought was that when a bundle with Camel amqp endpoints was restarted properly, it should
either close the connection during shutdown or get the same connection when it starts back
up. But it seems that this is not the design?

> Orphaned AMQP Consumers
> -----------------------
>
>                 Key: CAMEL-12070
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12070
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-amqp
>    Affects Versions: 2.19.3
>         Environment: OSGI / Karaf
>            Reporter: Ryan Moutray
>
> When "updating" bundles with a new version in an OSGI container (e.g. Karaf), Camel leaves
orphaned Consumers listening to the queue.
> Affected functionality is that messages are not delivered to the new Consumer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message