Auku, I just managed to reproduce that issue here as well. The endpoint MBeans seem to stay around for the other endpoint, but the connection no longer works. Could you raise a Camel JIRA issue about this problem so it can get fixed?
Thanks, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Wed, Oct 13, 2010 at 2:29 PM, Auke <[email protected]> wrote: > > I see that the message via the email isn't really well formatted, sorry about > that. I tried to make it as clear as possible on the forum but that didn't > do much good for the email. > > Anyhow I meant these two routes: > > --- > <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> > > <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> > --- > > For the log see the forums or see > http://servicemix.396122.n5.nabble.com/file/n3210380/test-scenario-log.log > this file around line 230. > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Jetty-connector-stops-unexpectedly-tp3208647p3210380.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
