2008/6/16 jmfj <[EMAIL PROTECTED]>: > > Yes, this was an issue and is now solved - here is the new code: > > http://www.nabble.com/file/p17870603/CamelTest.java CamelTest.java
Ah great! > When using the multi threaded feature of TestNG (pom.xml) > > (...) > <plugin> > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-surefire-plugin</artifactId> > <configuration> > <groups>unit,performance</groups> > <parallel>methods</parallel> > <threadCount>1</threadCount> > </configuration> > </plugin> > (...) > > If <threadCount/> is greater than 1 (multiple threads one per each test > method, executing in parallel) the test again fails occasionally.. The only > shared component across those two methods are Camel classes. Hmm - so the instance variables in those test methods should be different for each thread right? This is really strange - sounds like we've some static instance variables around the place then right? I've looked at the DefaultCamelContext and the SedaEndpoint and don't see any statics. > Apologies if I am posting in the wrong group... No this is the right group! :). Please keep these issues coming, it could well be you've found some gremlin in the code! -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
