Hi See this wiki page http://camel.apache.org/threading-model.html
You can implement a custom ExecutorServiceStrategy which hook into WebSphere. On Thu, Jul 29, 2010 at 5:01 PM, chaillon <[email protected]> wrote: > > Hi, > > I'm using: > - Camel 2.3.0 > - Websphere 7.0 > - Spring 2.5.6 > - Hibernate 3.5 > > I'm facing lookup errors where looking for the datasource from Camel threads > (or another else JNDI resource) > That seams logic since Camel use JDK threads pool instead of server thread > pool > > So I need to configure Camel to exclusively use websphere threads... > but camel documentation don't give me an example of how to do it > > After a quick look to camel source, I know that all threads are created by > the ExecutorServiceHelper... witch is an internal static final class... so > it can't be modified > I have test to replace this class by my own "websphere compliant" > implementation with success => All camel threads are now managed by the > websphere server > > Now, I know that it is possible... but I would like do it by a proper manner > Camel documentation say to use the ExecutorServiceStrategy to become server > complient, but i see that many threads are not created by this class... And > I can't achieve to make run my application with this strategy (always lookup > error!) > > So, what is the good manner to by websphere complient with Camel? > > See attachement for my own websphere complient implementation > > Thanks > > http://camel.465427.n5.nabble.com/file/n2256731/src.zip src.zip > -- > View this message in context: > http://camel.465427.n5.nabble.com/Usage-of-server-managed-thread-of-Websphere-tp2256731p2256731.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
