Hi
maybe the reported bugs below could be also of your interest:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539288
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523368
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/thread-error-with-java-lang-Thread-State-TIM
Babak Vahdat wrote
>
> Sorry, I messed it up!
>
> I mixed the the JDK build version versus the Hotspot build version you
> pasted at http://pastebin.com/WS6y9DEG. So simply forget my advice...
>
> I've still got no idea why you can not connect through the JConsole.
>
> Babak
>
Actually your
Sorry, I messed it up!
I mixed the the JDK build version versus the Hotspot build version you
pasted at http://pastebin.com/WS6y9DEG. So simply forget my advice...
I've still got no idea why you can not connect through the JConsole.
Babak
--
View this message in context:
http://camel.465427.n
And maybe do a "mvn clean install" beforehand as well to make sure your class
files are generated using the "correct" JDK compiler.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/thread-error-with-java-lang-Thread-State-TIMED-WAITING-from-jconsole-tp5459905p5462936.html
Hi
This is expected. The TIMED_WAITING thread is a JmsConsumer thread
which pickup new messages from the ActiveMQ message queue.
Currently there queue is empty so there is no messages to pickup and
therefore the thread is waiting.
If you put messages on that queue, then the thread will pickup and
Hi,
You do launch your Camel application under a pretty old JDK (20.1-b02)
installed on your box as well and *not* the (26-b03) build!
- Remove the bin directory of this old JDK installation from your unix PATH
and put the bin directory of the one you already mentioned by your post
- Set JAVA_HOM
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:/
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? 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
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
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
And check the link you've already provided regarding the note about the
required jars for the J
10 matches
Mail list logo
