1) Your JVM installation is corrupt, in which case downloading and installing the JVM again should fix it.
2) The JVM level is incompatible with the OS level, the most likely cause being incompatible library versions, in which case you would have to resolve the library versions. Though RPM should have complained during the JDK install about incompatible library versions. ( I have run JBoss with JDK 1.4.2 on RedHat Ent. 4 with no problems, but not on 3. Has anyone else out there run this combo?)
Thanks PeterJ. I reinstalled the jdk and then did a run.
I get a couple of exceptions. One is about the port 8080 already in use. That's what Tomcat runs on. Do I change the port on Tomcat or can I change the port on Jboss? I have about 20 tomcat contexts and would hate to reconfigure Tomcat for all of these because everytime I do, Tomcat takes a dump.
Can I set JBoss to run on a different port like 8081?
You can change the port number in deploy/jbossweb-tomcat55.sar/server.xml.
You can also search the configuration XML files for the string 8080.
Thanks PeterJ. I changed the deploy/jbossweb-tomcat55.sar/server.xml file to be 8081 and then ran run.sh and it worked. Now I just need to run it as a service in the background and see what happens with my OhioEdge CRM application.