Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have some experience with JBoss (and Glassfish), and ActiveMQ, but I've never used Camel before (but am familiar with Mule, which I read is similar).</p> <p>Your stack trace looks like it's Camel trying to link ActiveMQ (JMS-stuff on bottom of trace) to a web endpoint (HTTP-stuff on top of trace).</p> <p>I'm a bit confused as to where Camel is running (the CamelContext). You said that you have two virtual machines, one for JBoss and one for ActiveMQ. In my case, we run Mule ESB on the machine with our ActiveMQ. Where is your Camel running?</p> <p>Your stack trace appears most like Problem #1 from the first post. It's as if the Camel part cannot "see" the web endpoint. Check to see that your WAR is deployed correctly, and that your web endpoint (WSDL) is visible from both virtual machines. Check your endpoints; maybe one is set to localhost or something, which would not allow it to get to another machine.</p> <p>It's a bit hard to tell if it's an incomplete read or a complete inability to read. Does any data get through? It's possible that the Web Server is slowly getting overloaded and cannot keep up with requests (and starves some threads as in your error). Socket timeouts become important when you have slow responses or many requests; if you can create a test that is simple (fast and with few requests) then you can at least verify that you have basic connectivity. What data input (test) caused this error?</p> <p>I'll be happy to try to improve this answer given more input. (I'm sorry I would've tried commenting on your question but I don't think I have the rep for that yet...)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload