[
https://issues.apache.org/activemq/browse/CAMEL-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62689#action_62689
]
Ioannis Alexandrakis commented on CAMEL-3047:
---------------------------------------------
It is a bit irrelevant, since 2.5 is almost out, but i think the patch has a
little problem.
The line :
if (connectorRef != null && connectorRef.decrement() == 0)
should be
if (connectorRef != null && connectorRef.refCount == 0)
Otherwise, it gets decremented twice -in disconnect too?- (in my example i had
2 routes and the problem was still there after a restart of one of them).
In 2.5 it is ok though, just the attached patch has this code.
> 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
> Assignee: Willem Jiang
> 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.
