ReportServer Forum

Rajesh

Member

Registered: 2012-06-01

Issue with setting up

Hi,

I was trying to setup ReportServer but Im getting these errors. Any help?

13:55:47,747  INFO HbmBinder:353 - Mapping class: RS_FILTER_BLOCK_2_FILTERS_A ->
RS_FILTER_BLOCK_2_FILTERS_A
13:55:47,747  INFO HbmBinder:353 - Mapping class: net.datenwerke.rs.dsbundle.ser
vice.dsbundle.entities.DatabaseBundleEntry_A -> RS_DATABASE_BUNDLE_ENTRY_A
13:55:47,747  INFO DefaultTraversableResolver:81 - Instantiated an instance of o
rg.hibernate.validator.engine.resolver.JPATraversableResolver.
13:55:48,154  INFO SessionFactoryImpl:202 - building session factory
13:55:55,966  INFO SessionFactoryObjectFactory:105 - Not binding factory to JNDI
, no JNDI name configured
13:55:59,326  INFO SchemaValidator:121 - Running schema validator
13:55:59,326  INFO SchemaValidator:129 - fetching database metadata
13:55:59,638  INFO DefaultTraversableResolver:81 - Instantiated an instance of o
rg.hibernate.validator.engine.resolver.JPATraversableResolver.
13:56:00,279  INFO DatabaseMetadata:119 - table not found: RS_ACE
Jun 1, 2012 1:56:00 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error filterStart
Jun 1, 2012 1:56:00 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/reportserver] startup failed due to previous errors
Jun 1, 2012 1:56:00 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate d
estroy
INFO: WSSERVLET15: JAX-WS servlet destroyed
Jun 1, 2012 1:56:00 PM com.sun.xml.ws.transport.http.servlet.WSServletContextLis
tener contextDestroyed
INFO: WSSERVLET13: JAX-WS context listener destroyed
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesJdbc
SEVERE: The web application [/reportserver] registered the JDBC driver [org.post
gresql.Driver] but failed to unregister it when the web application was stopped.
To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [com.google.inject.internal.util.$Finalizer] but has failed to stop it. This
is very likely to create a memory leak.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [Thread-2] but has failed to stop it. This is very likely to create a memory
leak.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [Thread-3] but has failed to stop it. This is very likely to create a memory
leak.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [Thread-4] but has failed to stop it. This is very likely to create a memory
leak.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [Timer-0] but has failed to stop it. This is very likely to create a memory l
eak.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has fai
led to stop it. This is very likely to create a memory leak.
Jun 1, 2012 1:56:08 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has fai
led to stop it. This is very likely to create a memory leak.
Jun 1, 2012 1:56:09 PM org.apache.catalina.loader.WebappClassLoader clearReferen
cesThreads
SEVERE: The web application [/reportserver] appears to have started a thread nam
ed [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has fai
led to stop it. This is very likely to create a memory leak.
Jun 1, 2012 1:56:09 PM org.apache.catalina.loader.WebappClassLoader checkThreadL
ocalMapForLeaks
SEVERE: The web application [/reportserver] created a ThreadLocal with key of ty
pe [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.interna
l.InjectorImpl$1@177c306]) and a value of type [java.lang.Object[]] (value [[Lja
va.lang.Object;@741e88]) but failed to remove it when the web application was st
opped. Threads are going to be renewed over time to try and avoid a probable mem
ory leak.
Jun 1, 2012 1:56:09 PM org.apache.catalina.loader.WebappClassLoader checkThreadL
ocalMapForLeaks
SEVERE: The web application [/reportserver] created a ThreadLocal with key of ty
pe [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.interna
l.InjectorImpl$1@177c306]) and a value of type [java.lang.Object[]] (value [[Lja
va.lang.Object;@1809f0f]) but failed to remove it when the web application was s
topped. Threads are going to be renewed over time to try and avoid a probable me
mory leak.
Jun 1, 2012 1:56:09 PM org.apache.catalina.loader.WebappClassLoader checkThreadL
ocalMapForLeaks
SEVERE: The web application [/reportserver] created a ThreadLocal with key of ty
pe [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.interna
l.InjectorImpl$1@177c306]) and a value of type [java.lang.Object[]] (value [[Lja
va.lang.Object;@14ac3cb]) but failed to remove it when the web application was s
topped. Threads are going to be renewed over time to try and avoid a probable me
mory leak.
Jun 1, 2012 1:56:09 PM org.apache.catalina.loader.WebappClassLoader checkThreadL
ocalMapForLeaks
SEVERE: The web application [/reportserver] created a ThreadLocal with key of ty
pe [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.interna
l.InjectorImpl$1@177c306]) and a value of type [java.lang.Object[]] (value [[Lja
va.lang.Object;@17c66f0]) but failed to remove it when the web application was s
topped. Threads are going to be renewed over time to try and avoid a probable me
mory leak.
Jun 1, 2012 1:56:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory E:\Apache Software Foundation\apache-t
omcat-7.0.27\webapps\docs
Jun 1, 2012 1:56:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory E:\Apache Software Foundation\apache-t
omcat-7.0.27\webapps\examples
Jun 1, 2012 1:56:14 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory E:\Apache Software Foundation\apache-t
omcat-7.0.27\webapps\host-manager
Jun 1, 2012 1:56:15 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory E:\Apache Software Foundation\apache-t
omcat-7.0.27\webapps\manager
Jun 1, 2012 1:56:16 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory E:\Apache Software Foundation\apache-t
omcat-7.0.27\webapps\ROOT
Jun 1, 2012 1:56:16 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8080"]
Jun 1, 2012 1:56:17 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8009"]
Jun 1, 2012 1:56:17 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 129161 ms
Jun 1, 2012 1:56:33 PM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  C
ould not load com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourc
eTask.  The eventual following stack trace is caused by an error thrown for debu
gging purposes as well as to attempt to terminate the thread which caused the il
legal access, and has no functional impact.
java.lang.IllegalStateException
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1597)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1556)
        at com.mchange.v2.resourcepool.BasicResourcePool.checkIdleResources(Basi
cResourcePool.java:1481)
        at com.mchange.v2.resourcepool.BasicResourcePool.access$2000(BasicResour
cePool.java:32)
        at com.mchange.v2.resourcepool.BasicResourcePool$CheckIdleResourcesTask.
run(BasicResourcePool.java:1964)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Exception in thread "Timer-0" java.lang.NoClassDefFoundError: com/mchange/v2/res
ourcepool/BasicResourcePool$AsyncTestIdleResourceTask
        at com.mchange.v2.resourcepool.BasicResourcePool.checkIdleResources(Basi
cResourcePool.java:1481)
        at com.mchange.v2.resourcepool.BasicResourcePool.access$2000(BasicResour
cePool.java:32)
        at com.mchange.v2.resourcepool.BasicResourcePool$CheckIdleResourcesTask.
run(BasicResourcePool.java:1964)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.ClassNotFoundException: com.mchange.v2.resourcepool.BasicRe
sourcePool$AsyncTestIdleResourceTask
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1711)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa
der.java:1556)
        ... 5 more

Last edited by Rajesh (2012-06-01 08:28:50)

Arno Mittelbach

datenwerke

Registered: 2012-02-14

Re: Issue with setting up

Hi Rajesh,

it looks like you are missing the database tables. Have you started ReportServer for the first time? If so, you need to change the following property in your persistence.xml file:
<property name="hibernate.hbm2ddl.auto" value="" />
to
<property name="hibernate.hbm2ddl.auto" value="create" />

cf. https://datenwerke.jira.com/wiki/x/Q4Cg section Configuration, persistence.xml

I hope that helps. If not, please send all the log files as tomcat spreads exceptions over its various files.

Cheers
Arno

Rajesh

Member

Registered: 2012-06-01

Re: Issue with setting up

Thanks Arno for the quick help. Now the server is up and running. Only problem is that I dont understand German .
Is there anyway to switch to an English view?

Thorsten J. Krause

Guest

Re: Issue with setting up

Hi Rajesh,

you can change the language in the menu labeled "Optionen",
another possibility is to access the application with the parameter ?locale=en

To set the default language, you have to edit the file reportserver.properties.

Cheers,
Thorsten