ReportServer Forum

richie1985

Member

Registered: 2012-11-01

Tomcat 7, kein Deploy möglich

Hallo,

gern wollte ich ReportServer mal testen und habe dazu auf meinem Windows ein Apache Tomcat 7 installiert und die Installationsanleitung befolgt. Beim ersten Deployen werden auch brav alle Mysql Tabellen angelegt. Leider kommt aber immer die Fehlermeldung "FAIL - Application at context path /reportserver could not be started"

Hier Auszug aus dem Log:

Nov 01, 2012 8:02:19 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\reportserver\WEB-INF\lib\juel-2.2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
Nov 01, 2012 8:02:19 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\reportserver\WEB-INF\lib\juel-api-2.2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
Nov 01, 2012 8:02:38 PM com.google.inject.servlet.InternalServletModule$BackwardsCompatibleServletContextProvider get
WARNING: You are attempting to use a deprecated API (specifically, attempting to @Inject ServletContext inside an eagerly created singleton. While we allow this for backwards compatibility, be warned that this MAY have unexpected behavior if you have more than one injector (with ServletModule) running in the same JVM. Please consult the Guice documentation at http://code.google.com/p/google-guice/wiki/Servlets for more information.
Nov 01, 2012 8:02:38 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Nov 01, 2012 8:02:41 PM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: null
Nov 01, 2012 8:02:42 PM com.sun.xml.ws.server.MonitorBase createRoot
INFO: Metro monitoring rootname successfully set to: null
Nov 01, 2012 8:02:42 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
Nov 01, 2012 8:03:34 PM com.google.inject.internal.ProxyFactory <init>
WARNING: Method [public net.datenwerke.treedb.client.treedb.dto.AbstractNodeDto net.datenwerke.rs.tsreportarea.server.tsreportarea.TsDiskRpcServiceImpl.loadNodeById(java.lang.Long,com.extjs.gxt.ui.client.data.BaseModel) throws net.datenwerke.gxtdto.client.servercommunication.exceptions.ServerCallFailedException] is synthetic and is being intercepted by [net.datenwerke.gf.service.gwtstacktrace.CatchStacktraceInterceptor@78b2a049]. This could indicate a bug.  The method may be intercepted twice, or may not be intercepted at all.
Nov 01, 2012 8:03:34 PM com.google.inject.internal.ProxyFactory <init>
WARNING: Method [public net.datenwerke.treedb.client.treedb.dto.AbstractNodeDto net.datenwerke.rs.tsreportarea.server.tsreportarea.TsDiskRpcServiceImpl.loadNodeById(java.lang.Long,com.extjs.gxt.ui.client.data.BaseModel) throws net.datenwerke.gxtdto.client.servercommunication.exceptions.ServerCallFailedException] is synthetic and is being intercepted by [net.datenwerke.security.service.security.aop.SecurityCheckInterceptor@7f1a6f36]. This could indicate a bug.  The method may be intercepted twice, or may not be intercepted at all.
Nov 01, 2012 8:03:35 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error filterStart
Nov 01, 2012 8:03:35 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/reportserver] startup failed due to previous errors
Nov 01, 2012 8:03:35 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate destroy
INFO: WSSERVLET15: JAX-WS servlet destroyed
Nov 01, 2012 8:03:35 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/reportserver] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [com.google.inject.internal.util.$Finalizer] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [pool-10-thread-1] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [scheduler-watchdog] but has failed to stop it. This is very likely to create a memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/reportserver] created a ThreadLocal with key of type [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.internal.InjectorImpl$1@3fb1da43]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@35708560]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Nov 01, 2012 8:03:35 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [/reportserver] created a ThreadLocal with key of type [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.internal.InjectorImpl$1@3fb1da43]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@6e447d08]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Nov 01, 2012 8:03:48 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask.  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 com.mchange.v2.resourcepool.BasicResourcePool.checkIdleResources(BasicResourcePool.java:1481)
    at com.mchange.v2.resourcepool.BasicResourcePool.access$2000(BasicResourcePool.java:32)
    at com.mchange.v2.resourcepool.BasicResourcePool$CheckIdleResourcesTask.run(BasicResourcePool.java:1964)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)

Ich hoffe Ihr könnt damit was anfangen. Vielen Dank und Gruss!

Arno Mittelbach

datenwerke

Registered: 2012-02-14

Re: Tomcat 7, kein Deploy möglich

Hallo Richie,

das ist jetzt ein Schuss ins Blaue ohne mir wirklich viel angesehen zu haben: Wie sehen denn die Memory Einstellungen für den Tomcat aus? Wir empfehlen
Tomcat mindestens das folgende zuzusichern:

-Xmx1548M
-XX:MaxPermSize=256M

(siehe auch: https://datenwerke.jira.com/wiki/displa … iguration)

Wenn das nichts hilft, sag nochmal Bescheid, dann schauen wir uns den Fehler morgen noch etwas genauer an.

Ach ja .. hast Du alle Tomcat log Dateien mal nach Exceptions abgesucht? Je nach Version und Einstellungen tauchen die "echten"
Fehler gerne in den unterschiedlichsten Logdateien auf...

Grüße
Arno

richie1985

Member

Registered: 2012-11-01

Re: Tomcat 7, kein Deploy möglich

Also die Memory Einstellungen sind so wie gewünscht eingestellt, bei Windows:

Wie oben in dem Log zu sehen ist bestimmt das hier die Fehlermeldung:

Nov 01, 2012 8:02:19 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\reportserver\WEB-INF\lib\juel-2.2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
Nov 01, 2012 8:02:19 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\reportserver\WEB-INF\lib\juel-api-2.2.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class

Oder?

richie1985

Member

Registered: 2012-11-01

Re: Tomcat 7, kein Deploy möglich

Okay anscheinend habe ich den Fehler gefunden, in Java war der Proxy noch aktiviert. Wohin versucht den ReportServer denn eine Verbindung aufzubauen?

Thorsten J. Krause

Guest

Re: Tomcat 7, kein Deploy möglich

Hallo Richie,

freut mich, wenn es jetzt funktioniert. Eigentlich baut ReportServer beim Start keine Verbindung auf - bei der Mehrzahl unserer Installationen hat der Server auf dem ReportServer installiert ist überhaupt keinen Internetzugang.
In der Demoinstallation wird, wie ja auch in der Installationsanleitung steht, zwar standardmässig eine Datenquelle zu unserem Demoserver angelegt, aber das hat ja beim Start noch keinerlei Auswirkung.

Schick uns doch bitte noch die übrigen Tomcat Logfiles, dann können wir nochmal nachforschen, was da bei Dir passiert ist.

Grüße
Thorsten