You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2009/02/11 10:07:59 UTC

[jira] Created: (SMX4-210) When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped

When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped
--------------------------------------------------------------------------------------------------------------------------

                 Key: SMX4-210
                 URL: https://issues.apache.org/activemq/browse/SMX4-210
             Project: ServiceMix 4
          Issue Type: Bug
            Reporter: Guillaume Nodet




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

[jira] Resolved: (SM-1797) When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.

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

Guillaume Nodet resolved SM-1797.
---------------------------------

    Resolution: Fixed

Sending        src/main/java/org/apache/servicemix/camel/CamelJbiComponent.java
Transmitting file data .
Committed revision 743290.

> When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1797
>                 URL: https://issues.apache.org/activemq/browse/SM-1797
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: servicemix-camel-2008.02
>
>
> This is also true when not using service units and registering endpoints directly into the component.

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

[jira] Updated: (SM-1797) When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.

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

Guillaume Nodet updated SM-1797:
--------------------------------

      Description: This is also true when not using service units and registering endpoints directly into the component.
    Fix Version/s: servicemix-camel-2008.02
         Assignee: Guillaume Nodet

> When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1797
>                 URL: https://issues.apache.org/activemq/browse/SM-1797
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: servicemix-camel-2008.02
>
>
> This is also true when not using service units and registering endpoints directly into the component.

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

[jira] Resolved: (SM-1797) When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.

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

Guillaume Nodet resolved SM-1797.
---------------------------------

    Resolution: Fixed

Sending        src/main/java/org/apache/servicemix/camel/CamelJbiComponent.java
Transmitting file data .
Committed revision 743279.

> When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1797
>                 URL: https://issues.apache.org/activemq/browse/SM-1797
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: servicemix-camel-2008.02
>
>
> This is also true when not using service units and registering endpoints directly into the component.

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

[jira] Reopened: (SM-1797) When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.

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

Guillaume Nodet reopened SM-1797:
---------------------------------


The endpoint is now removed from the nmr, but not from the internal service unit of the camel component:

{code}
Exception in thread "SpringOsgiExtenderThread-32" java.lang.IllegalStateException: An endpoint is already registered for key: {http://servicemix.apache.org/examples/camel}receiver:endpoint
        at org.apache.servicemix.common.Registry.registerEndpoint(Registry.java:55)
        at org.apache.servicemix.common.DefaultComponent.addEndpoint(DefaultComponent.java:295)
        at org.apache.servicemix.camel.CamelJbiComponent.activateJbiEndpoint(CamelJbiComponent.java:173)
        at org.apache.servicemix.camel.JbiEndpoint$1.doStart(JbiEndpoint.java:151)
        at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:47)
        at org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:421)
        at org.apache.camel.impl.DefaultCamelContext.startRoutes(DefaultCamelContext.java:659)
        at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:632)
        at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:167)
        at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:162)
        at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:47)
        at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:97)
        at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:116)
        at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
        at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
        at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
        at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.finishRefresh(AbstractDelegatedExecutionApplicationContext.java:380)
        at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:346)
        at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
        at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:308)
        at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:138)
        at java.lang.Thread.run(Thread.java:613)
{code}

> When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1797
>                 URL: https://issues.apache.org/activemq/browse/SM-1797
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: servicemix-camel-2008.02
>
>
> This is also true when not using service units and registering endpoints directly into the component.

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

[jira] Moved: (SM-1797) When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.

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

Guillaume Nodet moved SMX4-210 to SM-1797:
------------------------------------------

        Key: SM-1797  (was: SMX4-210)
    Project: ServiceMix  (was: ServiceMix 4)

> When stopping a bundle with a camel route from("jbi:xxx"), the jbi endpoint is not unregistered when the bundle is stopped
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1797
>                 URL: https://issues.apache.org/activemq/browse/SM-1797
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>


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