I have Tomcat and Java SDK properly installed and Tomcat runs fine in 8080 when I start it on its own, but when I start OpenEMM it does not open in Tomcat on port 8080 -- I get the error
Firefox can't establish a connection to the server at www.[myurl].com:8080.
When I start OpenEMM from the ssh command line I get the following. I do not have sendmail worked out yet but I'm assuming this shouldn't stop OpenEMM from running in Tomcat -- please correct me if I'm wrong on this. It appears from the server's response that it's starting.
UPDATE: I have disabled sendmail with bin/sendmail-disable.sh and still have the same problem loading in Tomcat, so have ruled that out as the culprit.
Here's the log from /home/openemm/tomcat/logs:
Oct 12, 2013 9:00:22 AM org.apache.catalina.startup.Catalina load
WARNING: Catalina.start using conf/server.xml: Error at (24, 78) : org.apache.catalina.mbeans.ServerLifecycleListener
Oct 12, 2013 9:00:22 AM org.apache.tomcat.util.digester.Digester startElement
SEVERE: Begin event threw exception
java.lang.ClassNotFoundException: org.apache.catalina.mbeans.ServerLifecycleListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:116)
at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1176)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:506)
at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1347)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2768)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:846)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:775)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:628)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1449)
at org.apache.catalina.startup.Catalina.load(Catalina.java:582)
at org.apache.catalina.startup.Catalina.start(Catalina.java:646)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:357)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:491)
Oct 12, 2013 9:00:22 AM org.apache.catalina.startup.Catalina load
WARNING: Catalina.start using conf/server.xml: Error at (24, 78) : org.apache.catalina.mbeans.ServerLifecycleListener
Oct 12, 2013 9:00:22 AM org.apache.catalina.startup.Catalina start
SEVERE: Cannot start server. Server instance is not configured.
Figure this out partially -- it seems the server.xml file supplied with Tomcat 8 was an old version and was causing problems. I deleted apache-tomcat-8.0.0-RC1 and installed apache-tomcat-8.0.0-RC3, updated the server.xml and web.xml files and now Tomcat is trying to load. See my new post on the subsequent blank page issue.
Got this issue resolved. The Tomcat version wasn't the problem. Renaming the openemm folder to ROOT and the openemm-ws folder to openemm-ws2 resolved this issue. Thanks.