Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <29747984.5471281566147345.JavaMail.jira@thor>
Date: Wed, 11 Aug 2010 18:35:47 -0400 (EDT)
From: "Paul Mietz Egli (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Updated: (CAMEL-3047) JettyHttpComponent.doStop() shuts down
 all servers in the VM, not just those associated with the component
In-Reply-To: <28592053.5461281566028018.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Paul Mietz Egli updated CAMEL-3047:
-----------------------------------

    Attachment: CAMEL-3047.patch

patch against trunk 984599

> 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.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.