camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9619) Qpid failover unsuccessful, Invalid Bundle Context
Date Fri, 19 Feb 2016 10:03:18 GMT

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

Sergey  commented on CAMEL-9619:
--------------------------------

I'm not sure that this is simple or even possible. We have Qpid Java client library, with
its own JNDI factory:

java.naming.factory.initial=org.apache.qpid.jndi.PropertiesFileInitialContextFactory

and 

<jee:jndi-lookup id="qpidConnectionFactory" jndi-name="QpidConnectionFactory" environment-ref="springConfig"/>

How could I implement it using blueprint?

> 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, camel-jms, camel-spring
>    Affects Versions: 2.15.2
>            Reporter: Sergey 
>         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)

Mime
View raw message