[ 
https://issues.apache.org/jira/browse/CAMEL-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-9674.
--------------------------------
    Resolution: Won't Fix

Its how OSGi works. The service is looked up and will timeout after a while.



> Using activemq component: Karaf blueprint hangs when jmsConfig wasn't 
> configured
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-9674
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9674
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-activemq
>    Affects Versions: 2.12.3
>         Environment: - Karaf 2.3.3
> - Aries blueprint 1.1.0
>            Reporter: Andrei Shakirin
>
> Hi,
> Sorry for reporting issue for pretty old Camel version, just like to be sure 
> that it is (or will be) fixed in newer versions.
> Environment: activemq camel component is used in Karaf container and 
> configured in Aries blueprint 
> Issue: if configuration correct, activemq component works as a charm.
> However if user forget to set jmsConfig with connection factory into 
> ActiveMQComponent, the blueprint context hangs in "Creating" state and no any 
> error message / exceptions are thrown. This make diagnostic of the problem 
> very difficult.
> The blueptrint configuration looks like:
> {code}
>    <reference id="jmsConnectionFactory" 
> interface="javax.jms.ConnectionFactory"/>
>     <bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
>         <property name="connectionFactory" ref="jmsConnectionFactory"/>
>     </bean>
>     <bean id="jmsConfig" 
> class="org.apache.camel.component.jms.JmsConfiguration">
>         <property name="connectionFactory" ref="jmsConnectionFactory"/>
>     </bean>
>     <bean id="activemq" 
> class="org.apache.activemq.camel.component.ActiveMQComponent">
>         <property name="configuration" ref="jmsConfig"/>
>     </bean>
> {code}
> The jmsConnectionFactory is imported as OSGi service. 
> To reproduce the problem it is enough to comment or remove <bean 
> id="activemq"  element. The blueprint context hangs without any error message.



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

Reply via email to