Hi I am new to cobertura , i created a war using cobertura while deploying this war in tomcat i am getting below error message
INFO: Initializing Mojarra 2.0.4 (FCS b09) for context '/victor'
Apr 02, 2012 1:22:07 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Apr 02, 2012 1:22:07 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/victor] startup failed due to previous errors
Apr 02, 2012 1:22:07 PM com.sun.xml.ws.transport.http.servlet.WSServletContextLi
stener contextDestroyed enter code here`
INFO: WSSERVLET13: JAX-WS context listener destroyed
Apr 02, 2012 1:22:08 PM org.apache.catalina.loader.WebappClassLoader clearRefere
ncesThreads
SEVERE: The web application [/victor] appears to have started a thread named [Th
read-3] but has failed to stop it. This is very likely to create a memory leak.
Apr 02, 2012 1:22:08 PM org.apache.catalina.loader.WebappClassLoader clearThread
LocalMap
SEVERE: The web application [/victor] created a ThreadLocal with key of type [nu
ll] (value [com.sun.faces.util.Util$1#14ec141]) and a value of type [java.util.H
ashMap] (value [{com.sun.faces.patternCache={ = }}]) but failed to remove it whe
n the web application was stopped. This is very likely to create a memory leak.
Apr 02, 2012 1:22:16 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Apr 02, 2012 1:22:16 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
Apr 02, 2012 1:22:17 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Apr 02, 2012 1:22:17 PM org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-9009
Apr 02, 2012 1:22:17 PM org.apache.coyote.ajp.AjpAprProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-8009
Apr 02, 2012 1:22:17 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 276800 ms
Just i changed my java version to 1.6 i used to compile sources with 1.7 for Cobertura instrumentation.
Related
After noticing that my web application is not running on the production server anymore, I looked inside the tomcat log (catalina.out):
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Listening for transport dt_socket at address: 8000
Mar 26, 2018 7:53:26 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 26, 2018 7:53:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 4624 ms
Mar 26, 2018 7:53:26 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 26, 2018 7:53:26 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Mar 26, 2018 7:53:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Listening for transport dt_socket at address: 8000
Mar 26, 2018 7:54:26 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 26, 2018 7:54:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2108 ms
Mar 26, 2018 7:54:26 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 26, 2018 7:54:26 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Mar 26, 2018 7:54:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Listening for transport dt_socket at address: 8000
Mar 26, 2018 7:55:31 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 26, 2018 7:55:32 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2428 ms
Mar 26, 2018 7:55:32 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 26, 2018 7:55:32 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Mar 26, 2018 7:55:32 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Listening for transport dt_socket at address: 8000
Mar 26, 2018 7:56:36 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 26, 2018 7:56:36 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1873 ms
Mar 26, 2018 7:56:36 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 26, 2018 7:56:36 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Mar 26, 2018 7:56:36 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
Listening for transport dt_socket at address: 8000
Mar 26, 2018 7:57:42 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Mar 26, 2018 7:57:42 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2534 ms
Mar 26, 2018 7:57:42 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Mar 26, 2018 7:57:42 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52 (Ubuntu)
Mar 26, 2018 7:57:42 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
The deploy "loop" starts with the following message:
Mar 26, 2018 5:00:45 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Mar 26, 2018 5:00:46 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
I tried to restart Tomcat and the entire server multiple times without success.
Can you imagine what's going wrong here?
Similar cases have been reported and the explanation was a Memory Leak.
About this warning which mentions that PermGen is ignored, why don't you use the correct option ? This might explain an insufficient memory leading to your problem.
Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
If after using the correct option (XX:MaxMetaspaceSize) you still have this problem, try giving it more memory. Try to understand what changed then your application cannot run anymore (data has changed in the DB ? how ?). If you still to convince yourself, remove the application and start Tomcat with no webapps at all.
Strange...
Can you run your app with other server ? Such as glassfish or jetty ?
I know it doesn't answer your question,but if the app work with the servers mentioned above, than your tomcat is with some problem,but if not work if them, than your code have some problems.
Following are the startup log messages:
Check if Algo ant logger exists
Found Algo logger, starting with Algo ant logging
Buildfile: $ALGOWEBAPPS_HOME/bin/algowebapps-control.xml
Deleting:$ALGO_TOP/algowebapps/webapps/
acm.war,acm470help.war,awl.war,dmcfg.war,Navigator.war,mdc.war,Visualizer.war
Copying 7 file to $ALGO_TOP/algowebapps/webapps
Deleting directory $ALGO_TOP/algowebapps/webapps/awl
Copying 1 file to $ALGO_TOP/algowebapps/webapps/ROOT
Sep 26, 2017 10:18:25 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path...
Sep 26, 2017 10:18:25 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-12001
Sep 26, 2017 10:18:26 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8888
Sep 26, 2017 10:18:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1145 ms
Sep 26, 2017 10:18:26 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Sep 26, 2017 10:18:26 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
Sep 26, 2017 10:18:26 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Navigator.war
Load details in $ALGO_TOP/algowebapps/webapps/Navigator//MetaTables.xml
Loaded 11 tables & views
Load details of db jdbc:oracle:thin:#UAT4
Load details of db jdbc:oracle:thin:#UAT4
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive mdc.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive acm.war
INFO: GridServlet - ==> initializing GridServlet processing
INFO: TreeServlet - ==> initializing TreeServlet processing
==> initializing LoaderServlet
INFO: AjaxStoreServlet - ==> initializing AjaxStoreServlet processing
INFO: ConfigStoreServlet - ==> initializing ConfigStoreServlet processing
INFO: ActionDataServlet - ==> initializing Ricos HTTP Servlet Executer
INFO: ExecuterServlet2 - ==> initializing Ricos HTTP Servlet Executer
INFO: ValidationServlet - ==> initializing ValidationServlet processing
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive acm470help.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive awl.war
Sep 26, 2017 10:18:32 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive dmcfg.war
2017-09-26 22:18:33,525 DEBUG [dmcfg] Installing into composite=com.algorithmics.log.provider.DailyLogFileProvider com.algorithmics.log.provider.CompositeLogProvider
2017-09-26 22:18:33,533 DEBUG [dmcfg] File path 'log' is relative - prepending ALGO_TOP=/opt/bns/alreu4/Algo/ALGO_TOP com.algorithmics.log.provider.DailyLogFileProvider
2017-09-26 22:18:33,534 DEBUG [dmcfg] Opening file '$ALGO_TOP/log/dmcfg-default-sbuvvrwm471-2017-09-26.log' om.algorithmics.log.provider.DailyLogFileProvider
2017-09-26 22:18:33,541 DEBUG [dmcfg] Installing into composite=com.algorithmics.log.provider.ConsoleLogProvider com.algorithmics.log.provider.CompositeLogProvider
Sep 26, 2017 10:18:36 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive Visualizer.war
Initializing started...
<<<It hangs here indefinitely>>>
Below is what is expected to follow in a normal startup:
[[
Initializing finished...
Sep 26, 2017 10:37:48 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Sep 26, 2017 10:37:48 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-12001
Sep 26, 2017 10:37:48 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Sep 26, 2017 10:37:48 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 7637 ms
]]
Is downloading Tomcat cource code and enable Tomcat debug mode the only choice to identify the root cause of such issue? But I have no access to the source code of those applications running in Tomcat (I can decompile the jar files in war files though it's a tedious). or there might be better way to figure out the cause?
This seems to be an issue with the deployed application start up. You would have to enable debug logging for the application and see the root cause.
You might also check the context.xml for the webapp and see if it's connecting to an external resource, e.g., a database. The log message explicitly mentions an Oracle jdbc driver, it may be hanging while trying to create a database connection pool.
the problem is now mitigated by a upgrade of NFS server to V4.
I am using tomcat server from eclipse for my projects. All these days it is working fine. But since 3 days tomcat is not starting sometimes from eclipse. I checked in Internet and tried lot many solutions. Even solutions given in other posts in stack-overflow related to this problem are not helping me. The console messages are
Oct 07, 2014 11:08:06 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/ packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Oct 07, 2014 11:08:06 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.j2ee.server:dims' did not find a matching property.
Oct 07, 2014 11:08:06 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:DReST' did not find a matching property.
Oct 07, 2014 11:08:06 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8181"]
Oct 07, 2014 11:08:06 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Oct 07, 2014 11:08:06 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 303 ms
Oct 07, 2014 11:08:06 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Oct 07, 2014 11:08:06 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.54
Oct 07, 2014 11:08:07 AM org.apache.tiles.impl.BasicTilesContainer init
INFO: Initializing Tiles2 container. . .
Oct 07, 2014 11:08:07 AM org.apache.tiles.impl.BasicTilesContainer initializeDefinitionsFactory
INFO: Tiles2 container initialization complete.
Oct 07, 2014 11:08:07 AM org.apache.tiles.access.TilesAccess setContainer
INFO: Publishing TilesContext for context: org.apache.catalina.core.ApplicationContextFacade
Oct 07, 2014 11:08:07 AM com.opensymphony.xwork2.config.providers.XmlConfigurationProvider info
INFO: Parsing configuration file [struts-default.xml]
Oct 07, 2014 11:08:07 AM com.opensymphony.xwork2.config.providers.XmlConfigurationProvider info
INFO: Parsing configuration file [struts-plugin.xml]
Oct 07, 2014 11:08:07 AM com.opensymphony.xwork2.config.providers.XmlConfigurationProvider info
INFO: Parsing configuration file [struts.xml]
Oct 07, 2014 11:08:07 AM org.apache.struts2.config.BeanSelectionProvider info
INFO: Loading global messages from ApplicationResources
Servlet Context --call back method--contextInitialized()
/home/saipavan/apache-tomcat-7.0.54/wtpwebapps/dims/StudentDao.properties
/home/saipavan/apache-tomcat-7.0.54/wtpwebapps/dims/
/home/saipavan/apache-tomcat-7.0.54/wtpwebapps/dims/
/home/saipavan/apache-tomcat-7.0.54/wtpwebapps/dims/
/home/saipavan/apache-tomcat-7.0.54/wtpwebapps/dims/
/home/saipavan/apache-tomcat-7.0.54/wtpwebapps/dims/
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/manager
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/manager has finished in 75 ms
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/ROOT
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/ROOT has finished in 67 ms
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/host-manager
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/host-manager has finished in 70 ms
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/examples
Oct 07, 2014 11:08:09 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Oct 07, 2014 11:08:09 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Oct 07, 2014 11:08:09 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: attributeAdded('org.apache.jasper.compiler.TldLocationsCache', 'org.apache.jasper.compiler.TldLocationsCache#7e7a19e7')
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/examples has finished in 142 ms
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/docs
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /home/saipavan/apache-tomcat-7.0.54/webapps/docs has finished in 68 ms
Oct 07, 2014 11:08:09 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8181"]
Oct 07, 2014 11:08:09 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Oct 07, 2014 11:08:09 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2670 ms
I am able to start tomcat through terminal. but when i try to open tomcat in browser after starting, I am getting error
Firefox can't establish a connection to the server at localhost:8181.
What might be the problem? Can anyone help me? Thankyou.
seems localhost is not getting resolved to IP address. Try to ping localhost ping -c localhost or try your systems IP address instead of localhost.
I have a Java web application that I am trying to deploy to our company's application server. It uses spring and spring-security. Everything works correctly when I run the application in Tomcat from Eclipse but when I try and deploy the .war file into a standalone Tomcat instance the server does not even finish starting up.
These are the catalina logs from the last attempt:
Jan 30, 2014 1:16:39 PM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.23 using APR version 1.4.6.
Jan 30, 2014 1:16:39 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Jan 30, 2014 1:16:39 PM org.apache.catalina.core.AprLifecycleListener initializeSSL
INFO: OpenSSL successfully initialized with version OpenSSL 1.0.0g 18 Jan 2012
Jan 30, 2014 1:16:40 PM org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jan 30, 2014 1:16:40 PM org.apache.coyote.ajp.AjpAprProtocol init
INFO: Initializing Coyote AJP/1.3 on ajp-8009
Jan 30, 2014 1:16:40 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2567 ms
Jan 30, 2014 1:16:40 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jan 30, 2014 1:16:40 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.36
Jan 30, 2014 1:16:41 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Jan 30, 2014 1:16:41 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Jan 30, 2014 1:16:41 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive MyApp.war
And then startup stops.
These are the localhost logs:
Jan 30, 2014 1:16:46 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
And then nothing...
All of the other log files for this last attempt are blank.
Any insight you guys might have would be greatly appreciated!
This problem was caused by not setting the JAVA_OPTS property to point to my .ini files.
I included this in my startup script:
set JAVA_OPTS= -DLOGCONFIG=%CATALINA_HOME%\conf\logging.ini -DINIFILE=%CATALINA_HOME%\conf\webapps.ini
and it ran succesfully
Yesterday I deployed my war in openshift using the usual command git push. But when I checked the url http://nrollin-nrollin.rhcloud.com, I am seeing the error HTTP Status 404 - The requested resource is not available. I have deployed the war many times but this is the first time I am seeing this error. I have even restarted the server but no luck. I searched down the cause in openshift forum also (https://www.openshift.com/forums/openshift/jbossas-application-the-requested-resource-is-not-available), but no solution to me as such yet. The app is running good in my local PC and is developed in Spring MVC and Hibernate.
Can anyone suggest me the cause of this issue? Or do I have to create app again..?
Below are the logs :
Jul 27, 2013 3:43:44 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-127.4.82.1-8080
Jul 27, 2013 3:43:44 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 5182 ms
Jul 27, 2013 3:43:44 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jul 27, 2013 3:43:44 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.37
Jul 27, 2013 3:43:45 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ROOT.war
Jul 27, 2013 3:44:06 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Jul 27, 2013 3:44:06 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [] startup failed due to previous errors
Jul 27, 2013 3:44:09 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-127.4.82.1-8080
Jul 27, 2013 3:44:10 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 25540 ms
I faced the same problem in my local system yesterday but I resolved it by cleaning it along with its directory. I think the same would be needed for Openshift tomcat server.