Experimental Physics and
Industrial Control System

​

>> What would be the cause?

The root cause is that your mgmt webapp is having trouble communicating with the engine webapp. You can look into this a bit more by trying the URL yourself from the command line using curl. Also, looking in the engine's logs will help. If you suspect the engine is non-responsive, you can get a stack trace and then see what the threads are doing. Is there anything in the engine's logs? Does top show anything on the engine?

>> Another thing I had to restart the entire engine from the sampleStartup.sh script

>> Is there a simpler way to start a single appliance only?

I suspect you mean "I had to restart the entire appliance" and "Is there a simpler way to start a single component only"

Ultimately, these are all Tomcat containers; so you should be able to stop/start them any of the methods available for stopping/starting Tomcat. I assume you are using jsvc; in which case, stopping a component is simply adding a -stop argument to the jsvc command like so