K. Tsang CEng MBCS PMP PMI-ACP OCMJEA OCPJP
K. Tsang wrote:Welcome to the Ranch.
First you need to shutdown JBoss completely normally or using the "kill <processid>" command. Then make sure the port JBoss uses (eg 8080) is not occupied or attached.
You also mentioned "when I close SSH console, it shuts itself down". Are you running JBoss interactively? If so your console window is the session. Just like the comand prompt window in Windows OS.
Once you can start JBoss normally, I believe your 503 error will go away.
Randy Mazin wrote:I'm not sure what you mean by "Are you running JBoss interactively" I was running it with sudo ./run.sh which was working fine a few days ago.
Also, this is my first time working with Jboss.
Any thoughts?
K. Tsang CEng MBCS PMP PMI-ACP OCMJEA OCPJP
K. Tsang wrote:
Randy Mazin wrote:I'm not sure what you mean by "Are you running JBoss interactively" I was running it with sudo ./run.sh which was working fine a few days ago.
Also, this is my first time working with Jboss.
Any thoughts?
Running "interactively" is basically see the jboss log update itself as you access pages. Since you are doing this remotely", killing the console would have kill the interactive session.
From your post "sudo ./run.sh" is interactive. Try
<JBOSS_HOME>/bin/run.sh -b 0.0.0.0 > /dev/null &
The -b flag for accessing anywhere (not just localhost) and the "&" at the end is making it background job.
Also you should start/run JBoss server with the user that owned the JBoss installation folder. If it's root so be it (yet I don't recommend). But that's another story.
Hope this helps.
K. Tsang CEng MBCS PMP PMI-ACP OCMJEA OCPJP
K. Tsang wrote:Good that the server actually starts again. 503 error... not sure why
Does the jboss log have any clues?
Are you using Apache as the front end then forward to JBoss for java apps? If so it may be the Apache HTTP server that cause the 503.