camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Mietz Egli (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3047) JettyHttpComponent.doStop() shuts down all servers in the VM, not just those associated with the component
Date Thu, 12 Aug 2010 22:05:47 GMT

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

Paul Mietz Egli commented on CAMEL-3047:
----------------------------------------

Claus, this new patch should address the issue of sharing connectors across different bundles
(really, across different CamelContexts in the same VM).  I'm pressed for time right now,
but will try to get a unit test that exercises the multiple-context case soon.

> JettyHttpComponent.doStop() shuts down all servers in the VM, not just those associated
with the component
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3047
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3047
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jetty
>    Affects Versions: 2.4.0
>         Environment: Java 1.6.0_20, Karaf 1.6.0, OSX 10.6.4
>            Reporter: Paul Mietz Egli
>             Fix For: 2.5.0
>
>         Attachments: CAMEL-3047-refcount.patch
>
>
> We are running several bundles in Karaf with separate Camel contexts, each of which uses
the camel-jetty component to expose services over HTTP.  Each bundle has an assigned port
and may listen on multiple URIs.  We noticed that when we updated or shut down one of these
bundles, all of the Jetty servers in the other bundles would stop listening on their respective
ports.
> The problem is that the map of ConnectorRef objects in JettyHttpComponent is static,
and therefore shared across the entire VM.  Changing this from static to an instance variable
fixed the issue for us.  

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


Mime
View raw message