Re: [HEADS UP] Classloader mixup with Jetty consumers

2012-10-27 Thread Willem jiang
On Sunday, October 28, 2012 at 1:03 AM, Raul Kripalani wrote: > Looks like my reply wasn't delivered to the list on Oct 22nd... Here > it goes again: > > Hi Willem, > > With regards to the integration test, the Processor that compares > classloaders sits right after the consumer endpoint.

Re: [HEADS UP] Classloader mixup with Jetty consumers

2012-10-27 Thread Raul Kripalani
There are likely more cases to consider where the classloader on the Thread could be different than expected. Another place that comes to mind is the Direct VM component, where a boundary is crossed but I'm not sure what thread processes the message on the consumer side... I'll check and report b

Re: [HEADS UP] Classloader mixup with Jetty consumers

2012-10-27 Thread Raul Kripalani
Looks like my reply wasn't delivered to the list on Oct 22nd... Here it goes again: Hi Willem, With regards to the integration test, the Processor that compares classloaders sits right after the consumer endpoint. So, if it succeeds when 2 or more bundles share the same HTTP port, we can be certa

Re: [HEADS UP] Classloader mixup with Jetty consumers

2012-10-21 Thread Willem jiang
Just one comment from the TCCL setting on the CamelContinuationServletl, the unit test that you added doesn't have the thread switch even we used the async invocation API. So we need to set the TCCL somewhere incase the we need to use the camel application class loader in the other thread. --

Re: [HEADS UP] Classloader mixup with Jetty consumers

2012-10-21 Thread Willem jiang
Hi Raul, The patches are looking good. +1 for back porting them into 2.10.x and 2.9.x. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)

Re: [HEADS UP] Classloader mixup with Jetty consumers

2012-10-21 Thread Raul Kripalani
Now also correcting the TCCL on Jetty consumers with disabled continuations: http://svn.apache.org/viewvc?view=revision&revision=1400734. Regards, *Raúl Kripalani* Apache Camel Committer Enterprise Architect, Program Manager, Open Source Integration specialist http://about.me/raulkripalani | http

[HEADS UP] Classloader mixup with Jetty consumers

2012-10-21 Thread Raul Kripalani
Hello, I've come across what I consider a critical bug in camel-jetty, given the installed base of that component. When multiple Camel Contexts expose camel-jetty consumers on the same TCP port, they share the underlying Jetty Connector. As a side effect of this, the route runs with the classload