Problems installing ReportServer 2.0 in Tomcat 7

ReportServer (EN)
1

Going thru the provided installation documentation, I get the following errors in the catalina.out log file when reportserver tries to run:

INFO: Deploying web application directory /opt/tomcat7/webapps/reportserver
May 2, 2013 1:08:21 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/opt/tomcat7/webapps/reportserver/WEB-INF/lib/gwt-user-2.5.1.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
May 2, 2013 1:08:22 PM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(/opt/tomcat7/webapps/reportserver/WEB-INF/lib/juel-api-2.2.4.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class

Can anyone shine a little light on this error?

2

Hi ragoley,

the two infos that you posted are due to tomcat complaining about that the two jars contain parts of the servlet api specification and should thus technically not be part of the run-time libraries.
We’ve adapted our build process that for the next version the two jars are not included.

However, these are just infos and cannot have caused any problems during the startup, as tomcat simply ignores the jars. If ReportServer is not coming up the error must, thus, lie elsewhere. Have a look at
ALL the tomcat logs. Depending on your installation tomcat flushes error messages to, for example, localhost-xx.log or stderr-xx.log. If you paste all the logs we’ll have
a look at what might cause the problem.

Cheers
Arno

3

I have the same problem… I removed the two jars, and now the only thing I have in the logs is:
SEVERE: Error listenerStart
May 06, 2013 9:27:18 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/reportserver] startup failed due to previous errors

Nothing else! Not helping a lot…

4

Hi tleveque,

can you post the other log’s there Arno describes.

kind regards,
Marcel

5

Hi tleveque,

one guess into the blue is that you have not installed the JCE policy files that allow you to use “proper” encryption.
Instead of installing the JCE policy files you can reduce the key size used by ReportServer by setting

rs.crypto.pbe.keylength = 128

It is defined in the file reportserver.properties (in the WEB-INF/classes subdirectory).

Also see http://reportserver.datenwerke.net/forum/viewtopic.php?id=41.

If this does not help please provide all the log files, then we can have a look at what is going on.

Cheers
Arno

6

Yes the keylength is set to 128.

But now I found this in one of the log file:

SEVERE: Exception sending context initialized event to listener instance of class net.datenwerke.rs.ReportServerServiceConfig
java.lang.RuntimeException: ReportServer does not want to start under these circumstances: Schema creation is activated in one of the persistence configurations but the forcecreate property is not set. As this might compromise the database ReportServer will not start until the issue is resolved.
at net.datenwerke.rs.ReportServerServiceConfig.preStartCheck(ReportServerServiceConfig.java:490)
at net.datenwerke.rs.ReportServerServiceConfig.getInjector(ReportServerServiceConfig.java:193)
at com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:45)
at net.datenwerke.gf.DwGwtFrameworkBase.contextInitialized(DwGwtFrameworkBase.java:57)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4797)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5291)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1673)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
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:722)
Caused by: java.lang.RuntimeException: Schema creation is activated in one of the persistence configurations but the forcecreate property is not set. As this might compromise the database ReportServer will not start until the issue is resolved.
at net.datenwerke.rs.ReportServerServiceConfig.preStartCheck(ReportServerServiceConfig.java:482)
… 17 more

7

If it can help, here is all my log files and my config files
https://www.dropbox.com/sh/uxb8uqk9v5z96xa/19R9FixVuE

8

Hi tleveque,

the message you receive is kind of a leftover from how we used to install the previous ReportServer version.
On the first startup ReportServer tries to autocreate some required tables. As this is a potentially dangerous operation, there is a failsafe mechanism in form of a special textfile, to enable the process. You can read the details on this mechanism in the install instructions detailed in https://datenwerke.jira.com/wiki/display/PUBLIC/Installation+and+basic+configuration

The easiest way to get started with the new version, is to use the sql-scripts in the ddl-subdirectory, and not use this mechanism at all. Unfortunately, we forgot to remove some old config from the build process, so you have to do this manually.

Open the file persistence.xml (in the WEB-INF/classes/META-INF subdirectory)
and locate the following section

<!-- Recreate table on server restart -->
<!--  DISABLE FOR PRODUCTION -->
<property name="hibernate.hbm2ddl.auto" value="create" />

change it to

<!-- Recreate table on server restart -->
<!--  DISABLE FOR PRODUCTION -->
<property name="hibernate.hbm2ddl.auto" value="" />

Cheers,
Thorsten

9

Hi again…

I did the change in the config file and created the tables using the reportserver-RS2.0-svn-4711-schema-PostgreSQL_CREATE.sql file, and now I get this, and my cpu is running at 100% until I stop Tomcat!

May 06, 2013 12:14:13 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: /Users/thierryleveque/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
May 06, 2013 12:14:13 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
May 06, 2013 12:14:13 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
May 06, 2013 12:14:13 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 471 ms
May 06, 2013 12:14:13 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
May 06, 2013 12:14:13 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.35
May 06, 2013 12:14:13 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Applications/dev/tools/apache-tomcat-7.0.35/webapps/docs
May 06, 2013 12:14:13 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Applications/dev/tools/apache-tomcat-7.0.35/webapps/examples
May 06, 2013 12:14:14 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Applications/dev/tools/apache-tomcat-7.0.35/webapps/host-manager
May 06, 2013 12:14:14 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Applications/dev/tools/apache-tomcat-7.0.35/webapps/manager
May 06, 2013 12:14:14 PM org.apache.catalina.session.StandardManager doLoad
SEVERE: IOException while loading persisted sessions: java.io.EOFException
java.io.EOFException
	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2304)
	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2773)
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:798)
	at java.io.ObjectInputStream.<init>(ObjectInputStream.java:298)
	at org.apache.catalina.util.CustomObjectInputStream.<init>(CustomObjectInputStream.java:58)
	at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:246)
	at org.apache.catalina.session.StandardManager.load(StandardManager.java:204)
	at org.apache.catalina.session.StandardManager.startInternal(StandardManager.java:491)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5300)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1673)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	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:722)

May 06, 2013 12:14:14 PM org.apache.catalina.session.StandardManager startInternal
SEVERE: Exception loading sessions from persistent storage
java.io.EOFException
	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2304)
	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2773)
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:798)
	at java.io.ObjectInputStream.<init>(ObjectInputStream.java:298)
	at org.apache.catalina.util.CustomObjectInputStream.<init>(CustomObjectInputStream.java:58)
	at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:246)
	at org.apache.catalina.session.StandardManager.load(StandardManager.java:204)
	at org.apache.catalina.session.StandardManager.startInternal(StandardManager.java:491)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5300)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1673)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	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:722)

May 06, 2013 12:14:14 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Applications/dev/tools/apache-tomcat-7.0.35/webapps/reportserver
May 06, 2013 12:14:26 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error filterStart
May 06, 2013 12:14:26 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/reportserver] startup failed due to previous errors
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/reportserver] registered the JDBC driver [org.h2.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
May 06, 2013 12:14:26 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.
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Thread-2] but has failed to stop it. This is very likely to create a memory leak.
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Thread-3] but has failed to stop it. This is very likely to create a memory leak.
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Thread-4] but has failed to stop it. This is very likely to create a memory leak.
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Thread-5] but has failed to stop it. This is very likely to create a memory leak.
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Thread-6] but has failed to stop it. This is very likely to create a memory leak.
May 06, 2013 12:14:26 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/reportserver] appears to have started a thread named [Thread-7] but has failed to stop it. This is very likely to create a memory leak.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@7e24a26f]) 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.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@1724661c]) 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.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@56abc422]) 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.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@26d9c0a2]) 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.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@21f5df9b]) 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.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@d1cd179]) 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.
May 06, 2013 12:14:26 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@2c7bf549]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@585458f]) 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.
May 06, 2013 12:14:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Applications/dev/tools/apache-tomcat-7.0.35/webapps/ROOT
May 06, 2013 12:14:26 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
May 06, 2013 12:14:26 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
May 06, 2013 12:14:26 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 13127 ms
May 06, 2013 12:18:25 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
May 06, 2013 12:18:25 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
May 06, 2013 12:18:25 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
May 06, 2013 12:18:25 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
May 06, 2013 12:18:25 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8080"]
May 06, 2013 12:18:25 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-bio-8009"]
May 06, 2013 12:18:25 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-8080"]
May 06, 2013 12:18:25 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-bio-8009"]

I am using jdk1.7.0_13 on Mac OS X 10.8.3
And Tomcat 7.0.35.

It is a brans new installation of Tomcat. No other webapp running (apart the manager app).
The PostgresSql is running locally and is working fine with other projects.
I have the postgres jdbc driver postgresql-9.1-901.jdbc4.jar installed in the lib directory of Tomcat.

Any clue?

10

Found also this in another log:

SEVERE: Exception starting filter guiceFilter
javax.persistence.PersistenceException: [PersistenceUnit: reportServerPU] Unable to build EntityManagerFactory
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:930)
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
	at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:72)
	at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:63)
	at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:47)
	at com.google.inject.persist.jpa.JpaPersistService.start(JpaPersistService.java:94)
	at com.google.inject.persist.PersistFilter.init(PersistFilter.java:77)
	at com.google.inject.servlet.FilterDefinition.init(FilterDefinition.java:114)
	at com.google.inject.servlet.ManagedFilterPipeline.initPipeline(ManagedFilterPipeline.java:98)
	at com.google.inject.servlet.GuiceFilter.init(GuiceFilter.java:172)
	at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:281)
	at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
	at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:107)
	at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4656)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5312)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1673)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	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:722)
Caused by: org.hibernate.MappingException: Repeated column in mapping for entity: net.datenwerke.scheduler.service.scheduler.triggers.complex.config.MonthlyNthDayConfig column: hour (should be mapped with insert="false" update="false")
	at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:682)
	at org.hibernate.mapping.PersistentClass.checkPropertyColumnDuplication(PersistentClass.java:704)
	at org.hibernate.mapping.PersistentClass.checkPropertyColumnDuplication(PersistentClass.java:700)
	at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:726)
	at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:479)
	at org.hibernate.mapping.SingleTableSubclass.validate(SingleTableSubclass.java:64)
	at org.hibernate.cfg.Configuration.validate(Configuration.java:1284)
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1742)
	at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920)
	... 26 more
11

Hi tleveque,

sorry to hear that it’s still not working for you.

We tried to mimic your scenario as best as we could (OsX, Tomcat 7, jdk1.7, postgres 9.1 and 9.2), but we were unable to reproduce the errors you are getting.

Could you (after deleting your logs) restart tomcat and send us the logfiles of this clean run?
Also include your persistence.xml, please.

This is the config, that is working for me

<!-- Connection properties -->        
<property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/>
<property name="hibernate.connection.driver_class" value="org.postgresql.Driver"/>
<property name="hibernate.connection.url" value="jdbc:postgresql:reportserver"/>
<property name="hibernate.connection.username" value="postgres"/>
<property name="hibernate.connection.password" value="postgres"/>

Sincerely yours,
Thorsten J. Krause

12

Here is my logs and config files:
https://www.dropbox.com/s/h73yd2jdw3t3ifh/LogsAndConfig.zip

By the way, I don’t understand your connection url in your config sample. Is “jdbc:postgresql:reportserver” a valid url? Where is the database name?
Usually my urls look like this: “jdbc:postgresql://localhost:5432/reportserver”…

13

Hi tleveque,

the problem is most probably the naming strategy in persistence.xml. Here you have

<property name="hibernate.ejb.naming_strategy" value="org.hibernate.cfg.ImprovedNamingStrategy"/>

but it should be

<property name="hibernate.ejb.naming_strategy" value="net.datenwerke.rs.utils.hibernate.OracleNamingStrategy"/>

Yes, the name OracleNamingStrategy is a bit misleading and we should probably change that in one of the next versions.
You need that particular naming strategy independent of the underlying database choice. The problem is, that
we had to fix a couple of things in Hibernate’s naming strategy. As these fixes were originally only needed to support oracle
the name got stuck. Please let us know, if
this still does not fix the problem.

As for the connection url, this depends upon your postgres installation. For any “real” installation you need a url as you suggested. For some
out of the box quick postgres installation the other one is fine (the last part is the database name).

Hope this helps
Arno

14

It is working now!!!
I changed this (the “hibernate.ejb.naming_strategy”), at the beginning to try to make it works… but forgot to put it back at the original value..

Thanks again for your help.

15

No problem. I am glad its working now you. Please don’t hesitate to ask, if you have any further problems or questions.

Cheers
Arno