Jasperserver error HTTP 404

[ushavamsi2003]

Hi,

Could someone please help me to figure out this issue.I have installed the japsersrever trial version for windows xp.The tomcat server seems to work fine.But when I try to connect to the japserserver i get a HTTP 404 error.I tried rebooting the system, restarting the tomcat server with no affect.Aattached is the log of  Tomcat for your reference.

Jul 15, 2013 4:10:38 PM org.apache.catalina.core.AprLifecycleListener initINFO: Loaded APR based Apache Tomcat Native library 1.1.20.Jul 15, 2013 4:10:38 PM org.apache.catalina.core.AprLifecycleListener initINFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].Jul 15, 2013 4:10:39 PM org.apache.coyote.http11.Http11AprProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:10:39 PM org.apache.coyote.ajp.AjpAprProtocol initINFO: Initializing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:10:39 PM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 2311 msJul 15, 2013 4:10:39 PM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaJul 15, 2013 4:10:39 PM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.26Jul 15, 2013 4:10:39 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory host-managerJul 15, 2013 4:10:42 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory jasperserver-proJul 15, 2013 4:11:33 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartJul 15, 2013 4:11:33 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver-pro] startup failed due to previous errorsJul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcSEVERE: A web application registered the JBDC driver [mondrian.olap4j.MondrianOlap4jDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [Thread-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [CascadeCacheCleaner] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:11:40 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory managerJul 15, 2013 4:11:40 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory ROOTJul 15, 2013 4:11:40 PM org.apache.coyote.http11.Http11AprProtocol startINFO: Starting Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:11:40 PM org.apache.coyote.ajp.AjpAprProtocol startINFO: Starting Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:11:40 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 61228 msJul 15, 2013 4:16:27 PM org.apache.coyote.http11.Http11AprProtocol pauseINFO: Pausing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:16:27 PM org.apache.coyote.ajp.AjpAprProtocol pauseINFO: Pausing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:16:28 PM org.apache.catalina.core.StandardService stopINFO: Stopping service CatalinaJul 15, 2013 4:16:28 PM org.apache.coyote.http11.Http11AprProtocol destroyINFO: Stopping Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:16:28 PM org.apache.coyote.ajp.AjpAprProtocol destroyINFO: Stopping Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:16:49 PM org.apache.catalina.core.AprLifecycleListener initINFO: Loaded APR based Apache Tomcat Native library 1.1.20.Jul 15, 2013 4:16:49 PM org.apache.catalina.core.AprLifecycleListener initINFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].Jul 15, 2013 4:16:49 PM org.apache.coyote.http11.Http11AprProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:16:49 PM org.apache.coyote.ajp.AjpAprProtocol initINFO: Initializing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:16:49 PM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 849 msJul 15, 2013 4:16:49 PM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaJul 15, 2013 4:16:49 PM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.26Jul 15, 2013 4:16:49 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor host-manager.xmlJul 15, 2013 4:16:49 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor jasperserver-pro.xmlJul 15, 2013 4:17:17 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartJul 15, 2013 4:17:17 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver-pro] startup failed due to previous errorsJul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcSEVERE: A web application registered the JBDC driver [mondrian.olap4j.MondrianOlap4jDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [Thread-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [CascadeCacheCleaner] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:17 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:17:20 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor manager.xmlJul 15, 2013 4:17:20 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory ROOTJul 15, 2013 4:17:20 PM org.apache.coyote.http11.Http11AprProtocol startINFO: Starting Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:17:20 PM org.apache.coyote.ajp.AjpAprProtocol startINFO: Starting Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:17:20 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 31036 msJul 15, 2013 4:17:26 PM org.apache.coyote.http11.Http11AprProtocol pauseINFO: Pausing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:17:26 PM org.apache.coyote.ajp.AjpAprProtocol pauseINFO: Pausing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:17:27 PM org.apache.catalina.core.StandardService stopINFO: Stopping service CatalinaJul 15, 2013 4:17:27 PM org.apache.coyote.http11.Http11AprProtocol destroyINFO: Stopping Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:17:27 PM org.apache.coyote.ajp.AjpAprProtocol destroyINFO: Stopping Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:19:39 PM org.apache.catalina.core.AprLifecycleListener initINFO: Loaded APR based Apache Tomcat Native library 1.1.20.Jul 15, 2013 4:19:39 PM org.apache.catalina.core.AprLifecycleListener initINFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].Jul 15, 2013 4:19:39 PM org.apache.coyote.http11.Http11AprProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:19:39 PM org.apache.coyote.ajp.AjpAprProtocol initINFO: Initializing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:19:39 PM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 853 msJul 15, 2013 4:19:39 PM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaJul 15, 2013 4:19:39 PM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.26Jul 15, 2013 4:19:39 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor host-manager.xmlJul 15, 2013 4:19:40 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor jasperserver-pro.xmlJul 15, 2013 4:20:08 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartJul 15, 2013 4:20:08 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver-pro] startup failed due to previous errorsJul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcSEVERE: A web application registered the JBDC driver [mondrian.olap4j.MondrianOlap4jDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [Thread-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [CascadeCacheCleaner] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:08 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:20:11 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor manager.xmlJul 15, 2013 4:20:11 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory ROOTJul 15, 2013 4:20:11 PM org.apache.coyote.http11.Http11AprProtocol startINFO: Starting Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:20:11 PM org.apache.coyote.ajp.AjpAprProtocol startINFO: Starting Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:20:11 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 31815 msJul 15, 2013 4:20:13 PM org.apache.coyote.http11.Http11AprProtocol pauseINFO: Pausing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:20:13 PM org.apache.coyote.ajp.AjpAprProtocol pauseINFO: Pausing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:20:14 PM org.apache.catalina.loader.WebappClassLoader findResourceInternalINFO: Illegal access: this web application instance has been stopped already.  Could not load ehcache-version.properties.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.Jul 15, 2013 4:20:14 PM org.apache.catalina.core.StandardService stopINFO: Stopping service CatalinaJul 15, 2013 4:20:14 PM org.apache.coyote.http11.Http11AprProtocol destroyINFO: Stopping Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:20:14 PM org.apache.coyote.ajp.AjpAprProtocol destroyINFO: Stopping Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:21:33 PM org.apache.catalina.core.AprLifecycleListener initINFO: Loaded APR based Apache Tomcat Native library 1.1.20.Jul 15, 2013 4:21:33 PM org.apache.catalina.core.AprLifecycleListener initINFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].Jul 15, 2013 4:21:33 PM org.apache.coyote.http11.Http11AprProtocol initINFO: Initializing Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:21:33 PM org.apache.coyote.ajp.AjpAprProtocol initINFO: Initializing Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:21:33 PM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 801 msJul 15, 2013 4:21:33 PM org.apache.catalina.core.StandardService startINFO: Starting service CatalinaJul 15, 2013 4:21:33 PM org.apache.catalina.core.StandardEngine startINFO: Starting Servlet Engine: Apache Tomcat/6.0.26Jul 15, 2013 4:21:33 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor host-manager.xmlJul 15, 2013 4:21:34 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor jasperserver-pro.xmlJul 15, 2013 4:22:01 PM org.apache.catalina.core.StandardContext startSEVERE: Error listenerStartJul 15, 2013 4:22:01 PM org.apache.catalina.core.StandardContext startSEVERE: Context [/jasperserver-pro] startup failed due to previous errorsJul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbcSEVERE: A web application registered the JBDC driver [mondrian.olap4j.MondrianOlap4jDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [Thread-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreadsSEVERE: A web application appears to have started a thread named [quartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [CascadeCacheCleaner] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:01 PM org.apache.catalina.loader.WebappClassLoader clearReferencesStopTimerThreadSEVERE: A web application appears to have started a TimerThread named [adhocCache] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly cancelled.Jul 15, 2013 4:22:04 PM org.apache.catalina.startup.HostConfig deployDescriptorINFO: Deploying configuration descriptor manager.xmlJul 15, 2013 4:22:04 PM org.apache.catalina.startup.HostConfig deployDirectoryINFO: Deploying web application directory ROOTJul 15, 2013 4:22:04 PM org.apache.coyote.http11.Http11AprProtocol startINFO: Starting Coyote HTTP/1.1 on http-8080Jul 15, 2013 4:22:04 PM org.apache.coyote.ajp.AjpAprProtocol startINFO: Starting Coyote AJP/1.3 on ajp-8009Jul 15, 2013 4:22:04 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 30926 ms

In the localhost file under tomcat logs i could also see some error as:

"Caused by: net.sf.ehcache.config.InvalidConfigurationException: There is one error in your configuration:    * CacheManager configuration: You've assigned more memory to the on-heap than the VM can sustain, please adjust your -Xmx setting accordingly

Thanks

Vamsi



 

[marianol]

How much memory do you have in that XP machine? It looks like from the ehcache error the JVM is asking for more memory that the one available in the machine. I think that the deafule in Jasper is -Xms1024m -Xmx2048m

A couple of questions that will help everybody trouble shoot this:
- Which version of Jasper Server? What Install are you using (bundled or WAR file)
- Which Tomcat Version?
- What are your current tomcat settings (specially Xmx and Xms)

[ushavamsi2003]

Thanks for the feedback.

 

I have 2 GB of RAM in my machine. The Jasperserver I am using is the 5.2 one and Apache-tomcat is of 6 version.Bundled version. I checked the catalina.bat and setenv.bat and there is no Xmx / -Xms parameter set to.

 

Please let me know your feedback.

 

Thanks

[ushavamsi2003]

Thanks for the feedback.

I have 2 GB of RAM in my machine. The Jasperserver I am using is the 5.2 one and Apache-tomcat is of 6 version.Bundled version. I checked the catalina.bat and setenv.bat and there is no Xmx / -Xms parameter set to.

Please let me know your feedback.

Thanks

 

[jatinb]

We tried to upgrade an existing JasperReports Server 4.5.1 with repository on an Oracle DB to version 5.2 using a jasperreports-server-5.2-bin. We followed the steps as mentioned in the JasperReports-Server-Install-Guide 5.2, chapter 12. The upgrade script executed successfully with an ‘BUILD SUCCESSFUL’ message. However, on restarting jasper service, we get an error.

The error is same as:
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'AdHocEhCacheMBeanRegistration' defined in ServletContext resource [/WEB-INF/applicationContext-diagnostic-pro.xml]: Cannot resolve reference to bean 'adhocCacheManager' while setting bean property 'arguments' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'adhocCacheManager' defined in ServletContext resource [/WEB-INF/applicationContext-datarator.xml]: Invocation of init method failed; nested exception is net.sf.ehcache.config.InvalidConfigurationException: There is one error in your configuration:
    * CacheManager configuration: You've assigned more memory to the on-heap than the VM can sustain, please adjust your -Xmx setting accordingly

[jatinb]

Were you able to resolve the error?