If a Jemboss server was working but has stopped doing so then stop the server using the tomstop script, check that the server process has stopped and kill it if not, and then restart the server using the tomstart script. Allow 30 seconds for the server to stabilize.
If the client/server installation fails, and if the cause is not immediately obvious, then two log files may help diagnose the problem. Using the installation example above these are:
/m1/SOAPRESULTS/Jemboss_error.log
/usr/local/tomcat/logs/catalina.out
The most common problems are:
Failure to set the permissions of the jembossctl program correctly (client/server). This should be owned by root with the setuid bit set.
Failure to set the permissions of the results directory correctly. This should be world readable and writeable with the sticky bit set.
Using a very new version of Tomcat or Axis that Jemboss has not yet been modified to work with.
EMBOSS binaries not working owing to missing library dependencies. You should check that the EMBOSS binaries work by invoking one of them directly. In the example installation you should try typing:
/usr/local/emboss/bin/embossversion |
Jemboss will not work if the EMBOSS binaries don't.
Ports blocked by firewalls or already in use by other applications.
Note that if you have to try reinstalling Jemboss then you must start from scratch. We'll repeat that; you must start from scratch! Installation of Jemboss modifies things in most directories such that they cannot easily be set back to their default contents by any other means than deletion and re-extraction. So, delete:
The EMBOSS source code directory
The installation directory
The tomcat directory
The axis directory
then re-extract them from their tarballs.