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 2016/05/05 15:01:12 UTC

[jira] [Commented] (CAMEL-9619) Qpid failover unsuccessful, Invalid Bundle Context

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

Claus Ibsen commented on CAMEL-9619:
------------------------------------

See CAMEL-9900 there is a new option you can try to turn on that some users also had that invalid bundle context error but using plain jms. But the AMQP component is built on top of JMS.

> Qpid failover unsuccessful, Invalid Bundle Context
> --------------------------------------------------
>
>                 Key: CAMEL-9619
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9619
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-amqp, osgi
>    Affects Versions: 2.15.2
>            Reporter: Sergey 
>            Priority: Minor
>         Attachments: camel-context.xml, jms.xml, osgi-context.xml
>
>
> We have AMQP camel client consuming data from Qpid queue. Our setup contains one camel bundle and a connection factory, deployed as spring-dm xml. Everything works fine until failover, when we have an error like this:
> 2016-02-18 18:00:05,273 | ERROR | [fibigdataQueue] | faultJmsMessageListenerContainer | 292 - org.apache.servicemix.bundles.spring-jms - 3.2.11.RELEASE_1 | Could not refresh JMS Connection for destination 'fibigdataQueue' - retrying in 5000 ms. Cause: Invalid BundleContext.
> At the moment camel stops to consume messages from queue, and stuck in this state until camel bundle updated.



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