HTTP Status 404 - /jasperserver-pro/login.html

[ramesh.meda]

Hi,

I installed jasper report server 5.6.1 version intenallay insatalled Tomacat server & postgre sql,tomcat server runing but report server application not opening,the below error getting,please

send solutions for this below isssue.

HTTP Status 404 - /jasperserver-pro/login.html

---

type Status report

message /jasperserver-pro/login.html

description The requested resource is not available.

---

Apache Tomcat/7.0.42

C:Jaspersoftjasperreports-server-5.6.1apache-tomcatlogscatalina 2014-10-16

Oct 06, 2014 12:57:10 AM org.apache.catalina.core.AprLifecycleListener init

INFO: Loaded APR based Apache Tomcat Native library 1.1.27 using APR version 1.4.6.

Oct 06, 2014 12:57:10 AM org.apache.catalina.core.AprLifecycleListener init

INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].

Oct 06, 2014 12:57:11 AM org.apache.catalina.core.AprLifecycleListener initializeSSL

INFO: OpenSSL successfully initialized (OpenSSL 1.0.1d 5 Feb 2013)

Oct 06, 2014 12:57:12 AM org.apache.coyote.AbstractProtocol init

INFO: Initializing ProtocolHandler ["http-apr-8080"]

Oct 06, 2014 12:57:12 AM org.apache.coyote.AbstractProtocol init

INFO: Initializing ProtocolHandler ["ajp-apr-8009"]

Oct 06, 2014 12:57:12 AM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 1460 ms

Oct 06, 2014 12:57:12 AM org.apache.catalina.core.StandardService startInternal

INFO: Starting service Catalina

Oct 06, 2014 12:57:12 AM org.apache.catalina.core.StandardEngine startInternal

INFO: Starting Servlet Engine: Apache Tomcat/7.0.42

Oct 06, 2014 12:57:12 AM org.apache.catalina.startup.HostConfig deployDirectory

INFO: Deploying web application directory C:Jaspersoftjasperreports-server-5.6.1apache-tomcatwebappshost-manager

Oct 06, 2014 12:57:12 AM org.apache.catalina.startup.HostConfig deployDirectory

INFO: Deploying web application directory C:Jaspersoftjasperreports-server-5.6.1apache-tomcatwebappsjasperserver-pro

Oct 06, 2014 12:57:27 AM org.apache.catalina.startup.TaglibUriRule body

INFO: TLD skipped. URI: http://www.springframework.org/tags is already defined

Oct 06, 2014 12:57:27 AM org.apache.catalina.startup.TaglibUriRule body

INFO: TLD skipped. URI: http://www.tonbeller.com/jpivot/core is already defined

Oct 06, 2014 12:57:27 AM org.apache.catalina.startup.TaglibUriRule body

INFO: TLD skipped. URI: http://www.springframework.org/tags is already defined

Oct 06, 2014 12:57:49 AM org.apache.catalina.core.StandardContext startInternal

SEVERE: Error listenerStart

Oct 06, 2014 12:57:49 AM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/jasperserver-pro] startup failed due to previous errors

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.oracle.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.oracle.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.sqlserver.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.sqlserver.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.db2.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.db2.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.hive.HiveDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [tibcosoftware.jdbc.hive.HiveDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/jasperserver-pro] registered the JDBC driver [org.teiid.jdbc.TeiidDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [Thread-2] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] 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.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] 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.

Oct 06, 2014 12:57:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [sessionMonitor] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [bitronix-task-scheduler] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [bufferManager Cleaner] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [scheduled-eviction-thread-0] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [CascadeCacheCleaner] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [JasperServer Adhoc EhCache Cleaner] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/jasperserver-pro] appears to have started a thread named [adhocCache] but has failed to stop it. This is very likely to create a memory leak.

Oct 06, 2014 12:57:50 AM org.apache.catalina.startup.HostConfig deployDirectory

INFO: Deploying web application directory C:Jaspersoftjasperreports-server-5.6.1apache-tomcatwebappsmanager

Oct 06, 2014 12:57:50 AM org.apache.catalina.startup.HostConfig deployDirectory

INFO: Deploying web application directory C:Jaspersoftjasperreports-server-5.6.1apache-tomcatwebappsROOT

Oct 06, 2014 12:57:50 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler ["http-apr-8080"]

Oct 06, 2014 12:57:50 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler ["ajp-apr-8009"]

Oct 06, 2014 12:57:50 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 38062 ms

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:57:50 AM org.apache.catalina.loader.WebappClassLoader findResourceInternal

INFO: 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.

Oct 06, 2014 12:58:48 AM org.apache.catalina.loader.WebappClassLoader loadClass

INFO: Illegal access: this web application instance has been stopped already.  Could not load org.infinispan.util.concurrent.BoundedConcurrentHashMap$Values.  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.

java.lang.IllegalStateException

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1600)

    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559)

    at org.infinispan.util.concurrent.BoundedConcurrentHashMap.values(BoundedConcurrentHashMap.java:2113)

    at org.infinispan.container.DefaultDataContainer.purgeExpired(DefaultDataContainer.java:189)

    at org.infinispan.eviction.EvictionManagerImpl.processEviction(EvictionManagerImpl.java:102)

    at org.infinispan.eviction.EvictionManagerImpl$ScheduledTask.run(EvictionManagerImpl.java:144)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

    at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)

    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:724)

 

 

 

[hozawa]

Can't find the exact cause from the error message. By any chance, are you using Java8? JasperReports Server still haven't supported Java8. You'll have to use Java7.