You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2010/10/15 09:11:40 UTC
[jira] Moved: (CAMEL-3235) Restarting a bundle with a jetty
endpoint also stops connector for other jetty endpoints (in different
bundles)
[ https://issues.apache.org/activemq/browse/CAMEL-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen moved SMX4-609 to CAMEL-3235:
---------------------------------------------
Component/s: (was: camel-nmr)
camel-jetty
Affects Version/s: (was: 4.3.0)
2.4.0
Key: CAMEL-3235 (was: SMX4-609)
Project: Apache Camel (was: ServiceMix 4)
> Restarting a bundle with a jetty endpoint also stops connector for other jetty endpoints (in different bundles)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3235
> URL: https://issues.apache.org/activemq/browse/CAMEL-3235
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jetty
> Affects Versions: 2.4.0
> Environment: Windows Vista, Linux (CentOS release 5.5)
> Reporter: Auke van Leeuwen
> Attachments: test-projects.zip, test-scenario-log.log
>
>
> Scenario: I create two simple routes in different bundles:
> <route id="jettyRoute1">
> <from uri="jetty:http://0.0.0.0:15000/jetty?matchOnUriPrefix=true"/>
> <to uri="log:nl.example.jetty.jetty1?showAll=true&level=INFO"/>
> </route>
> and (the other bundle):
> <route id="jettyRoute2">
> <from uri="jetty:http://0.0.0.0:16000/jetty?matchOnUriPrefix=true"/>
> <to uri="log:nl.example.jetty.jetty2?showAll=true&level=INFO"/>
> </route>
> When I go to http://localhost:15000/jetty or http://localhost:16000/jetty I get both log message in my log. My routes are working. However when I restart one of those bundles both jetty servers are killed and only one is restarted.
> See also http://servicemix.396122.n5.nabble.com/Jetty-connector-stops-unexpectedly-td3208647.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.