h seems to be the root of the problem. When I
> reconfigured my test route to use a different (and valid as a producer)
> endpoint then everything worked as expected.
>
> Thanks.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.co
s slightly different.
Thanks for looking into it.
--
View this message in context:
http://camel.465427.n5.nabble.com/NPE-during-stop-start-route-attempts-with-JMX-tp5742131p5742141.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ducer)
endpoint then everything worked as expected.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/NPE-during-stop-start-route-attempts-with-JMX-tp5742131p5742140.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
> at
>
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
> at
>
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/NPE-during-stop-start-route-attempts-with-JMX-tp5742131.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
:
http://camel.465427.n5.nabble.com/NPE-during-stop-start-route-attempts-with-JMX-tp5742131.html
Sent from the Camel - Users mailing list archive at Nabble.com.