Babak Vahdat wrote
>
> Hi
>
> Can you please precisely describe the problem you're facing? The thread
> state TIMED_WAITING is a legitimate state:
>
> http://docs.oracle.com/javase/6/docs/api/java/lang/Thread.State.html#TIMED_WAITING
>
Just connecting with jconsole to camel apps throws a huge thread stack
trace. Pardon, TIMED_WAITING is legitimate. Sure I can't read stack trace
(which is very long), but at the very beginning:
Full thread dump Java HotSpot(TM) Server VM (20.1-b02 mixed mode):
"InactivityMonitor WriteCheck" daemon prio=10 tid=0x087ad400 nid=0x5c1f in
Object.wait() [0x8ca6e000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0xaea3fbd0> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0xaea3fbd0> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
"InactivityMonitor ReadCheck" daemon prio=10 tid=0x09442400 nid=0x5c1e in
Object.wait() [0x8cabe000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0xaea3f700> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0xaea3f700> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)
could it be a concurrency issue?
Babak Vahdat wrote
>
> And check the link you've already provided regarding the note about the
> required jars for the JMX support on Camel 2.8 or older which says:
>
> If these jars is not on the classpath Camel will fallback to non JMX mode!
>
> Babak
>
Thank you for the advise: actually it looks I already included the jars
thanks to maven. Also adding these jars to pom.xml doesn't change anything.
Thank you again,
Francesco
--
View this message in context:
http://camel.465427.n5.nabble.com/thread-error-with-java-lang-Thread-State-TIMED-WAITING-from-jconsole-tp5459905p5460320.html
Sent from the Camel - Users mailing list archive at Nabble.com.
