Babak Vahdat wrote > > Where does that stack trace blows up on the JConsole or on your App side? > Can you attach that huge stack trace as an Attachment to your Post? > First of all, thank you for helping me to post a sensible message.
Stack trace is too long, but you can glance it at: http://pastebin.com/WS6y9DEG The JConsole is quite silent: it just says in the dialog box: 'Connection Failed. Retry?' > And how do you deploy your Camel App? Standalone, JEE-Server (if yes which > one and which version), OSGi (the same information as well). > > The more information you provide, the more likely the people on the Forum > can help you. > > Babak > It is a stand-alone Camel app: it was launched with mvn camel:run. Platform is Debian GNU/Linux Lenny, Java is java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) camel is camel-2.8.4. The stack trace bounces up from the console from which the mvn camel:run command is issued. ciao, Francesco -- View this message in context: http://camel.465427.n5.nabble.com/thread-error-with-java-lang-Thread-State-TIMED-WAITING-from-jconsole-tp5459905p5462495.html Sent from the Camel - Users mailing list archive at Nabble.com.
