July 10th, 2001, 12:26 PM
Tomcat + SOAP + segmentation faults
I have a problem with Tomcat/SOAP on my Redhat 7 Linux system.
I have a Tomcat install that I want to integrate with SOAP. Whenever I add xerces.jar to the beginning of CLASSPATH (like the install docs for SOAP say), Tomcat will not startup. All that happens when I run startup.sh is it prints the classpath that it is using to the terminal and doesn't give back a command prompt
If I then run the shutdown.sh script I get a segmentation fault.
If xerces.jar isn't at the front of the classpath then Tomcat works fine.
Another (probably related) problem is that when running the server/client side testing of SOAP
I get a segmentation fault, but I can only run this if I don't have xerces.jar at the beginning of my classpath (which is why I suspect the two problems are related).
java org.apache.soap.server.ServiceManagerClient rpc-router-url list
July 13th, 2001, 10:41 AM
Turns out that it is a 'known issue' with Redhat and SOAP. Getting the 2.2-12 versions of glibc and glibc-common sorted it out