#1 2013-10-01 18:52:52

lowreyjon
Member
From: Gainesville, FL
Registered: 2013-10-01

Errors in setup

Using Tomcat 7, Java 7 and the latest ReportServer 2.1 on MAC OS 10.8.5

I am receiving the following error in my Catalina.out file starting from the startup of reportserver.   I updated every step in the instructions but I'm new to using a Mac.  (New job and they have a mac environment)  So assumptions made on the "how" part of updating everything is the source of my problem I'm sure.

Here is the error starting from the kickoff of reportserver when I startup Tomcat.

INFO: Deploying web application directory /Users/jonathanlowrey/tomcat/webapps/reportserver
14:26:22,507  INFO Version:37 - HCANN000001: Hibernate Commons Annotations {4.0.2.Final}
14:26:22,514  INFO Version:41 - HHH000412: Hibernate Core {4.2.2.Final}
14:26:22,517  INFO Environment:239 - HHH000206: hibernate.properties not found
14:26:22,518  INFO Environment:342 - HHH000021: Bytecode provider name : javassist
14:26:22,905  WARN Ejb3Configuration:1141 - HHH000144: hibernate.connection.autocommit = false breaks the EJB3 specification
14:26:22,972  INFO ConnectionProviderInitiator:188 - HHH000130: Instantiating explicit connection provider: org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider
14:26:22,973  INFO C3P0ConnectionProvider:128 - HHH010002: C3P0 using driver: com.postgresql.jdbc.Driver at URL: jdbc:postgresql://localhost:5432/reportserver
14:26:22,973  INFO C3P0ConnectionProvider:129 - HHH000046: Connection properties: {user=jonathanlowrey, password=****, autocommit=false, release_mode=auto}
14:26:22,974  INFO C3P0ConnectionProvider:132 - HHH000006: Autocommit mode: false
Oct 01, 2013 2:26:22 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error filterStart
Oct 01, 2013 2:26:22 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/reportserver] startup failed due to previous errors
Oct 01, 2013 2:26:23 PM net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl getConfigFailsafe
WARNING: Configfile datasources/internaldb.cf could not be loaded. Default values are in effect.
com.google.inject.ProvisionException: Guice provision errors:

1) Error in custom provider, java.lang.NullPointerException
  while locating com.google.inject.persist.jpa.JpaPersistService
  while locating javax.persistence.EntityManager

1 error
	at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
	at net.datenwerke.rs.utils.simplequery.byatt.QueryByAttProcessor.process(QueryByAttProcessor.java:62)
	at net.datenwerke.rs.utils.simplequery.byatt.QueryByAttInterceptor.invoke(QueryByAttInterceptor.java:25)
	at net.datenwerke.rs.terminal.service.terminal.vfs.hooks.TreeBasedVirtualFileSystem.getNodeByLocation(TreeBasedVirtualFileSystem.java:107)
	at net.datenwerke.rs.terminal.service.terminal.vfs.hooks.TreeBasedVirtualFileSystem.getLocation(TreeBasedVirtualFileSystem.java:60)
	at net.datenwerke.rs.terminal.service.terminal.vfs.VirtualFileSystemDeamon.getLocation(VirtualFileSystemDeamon.java:142)
	at net.datenwerke.rs.terminal.service.terminal.vfs.VirtualFileSystemDeamon.getAbsoluteLocation(VirtualFileSystemDeamon.java:104)
	at net.datenwerke.rs.terminal.service.terminal.vfs.VirtualFileSystemDeamon.getLocation(VirtualFileSystemDeamon.java:80)
	at net.datenwerke.rs.terminal.service.terminal.vfs.hookers.VfsObjectResolver.getParentLocation(VfsObjectResolver.java:81)
	at net.datenwerke.rs.terminal.service.terminal.vfs.hookers.VfsObjectResolver.consumes(VfsObjectResolver.java:23)
	at net.datenwerke.rs.terminal.service.terminal.objresolver.ObjectResolverDeamon.getObjects(ObjectResolverDeamon.java:60)
	at net.datenwerke.rs.terminal.service.terminal.objresolver.ObjectResolverDeamon.getObjects(ObjectResolverDeamon.java:88)
	at net.datenwerke.rs.terminal.service.terminal.objresolver.ObjectResolverDeamon.getObjects(ObjectResolverDeamon.java:84)
	at net.datenwerke.rs.terminal.service.terminal.TerminalServiceImpl.getObjectsByLocation(TerminalServiceImpl.java:101)
	at net.datenwerke.rs.terminal.service.terminal.TerminalServiceImpl.getObjectByLocation(TerminalServiceImpl.java:112)
	at net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfig(ConfigServiceImpl.java:85)
	at net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfig(ConfigServiceImpl.java:76)
	at net.datenwerke.rs.configservice.service.configservice.ConfigServiceImpl.getConfigFailsafe(ConfigServiceImpl.java:67)
	at net.datenwerke.rs.core.service.internaldb.InternalDbModule.provideDbLocation(InternalDbModule.java:37)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.google.inject.internal.ProviderMethod.get(ProviderMethod.java:104)
	at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
	at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
	at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
	at net.datenwerke.rs.core.service.internaldb.InternalDbServiceImpl.getLocation(InternalDbServiceImpl.java:81)
	at net.datenwerke.rs.core.service.internaldb.InternalDbServiceImpl.clearDatabase(InternalDbServiceImpl.java:114)
	at net.datenwerke.rs.core.service.internaldb.hookers.ClearInternalDbOnShutdown.contextDestroyed(ClearInternalDbOnShutdown.java:26)
	at net.datenwerke.gf.DwGwtFrameworkBase.contextDestroyed(DwGwtFrameworkBase.java:88)
	at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4980)
	at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5626)
	at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:160)
	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:1113)
	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1671)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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)
Caused by: java.lang.NullPointerException
	at com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
	at com.google.inject.persist.jpa.JpaPersistService.get(JpaPersistService.java:50)
	at com.google.inject.persist.jpa.JpaPersistService.get(JpaPersistService.java:34)
	at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:55)
	at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
	at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
	... 45 more

Oct 01, 2013 2:26:23 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.
Oct 01, 2013 2:26:23 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.
Oct 01, 2013 2:26:23 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.
Oct 01, 2013 2:26:23 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.
Oct 01, 2013 2:26:23 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@5b5aabf0]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@1dce486b]) 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.
Oct 01, 2013 2:26:23 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@5b5aabf0]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@51f47816]) 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.
Oct 01, 2013 2:26:23 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@5b5aabf0]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@8f81663]) 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.
Oct 01, 2013 2:26:23 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@5b5aabf0]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@5785c22e]) 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.
Oct 01, 2013 2:26:23 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Users/jonathanlowrey/tomcat/webapps/ROOT
Oct 01, 2013 2:26:23 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Oct 01, 2013 2:26:23 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Oct 01, 2013 2:26:23 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 11708 ms

Offline

#2 2013-10-01 22:07:46

Thorsten J. Krause
Guest

Re: Errors in setup

Hi,

this looks like something is amiss with your database connection. Have you looked at the tomcat logfiles? Usually there are several tomcat logs named catalina-nnn.log and localhost-nnn.log

Cheers,
Thorsten

#3 2013-10-01 23:13:08

lowreyjon
Member
From: Gainesville, FL
Registered: 2013-10-01

Re: Errors in setup

The code pasted above is out of the catalina.out file.  it has all the information contained in both the local and catalina log file. It contains all the same information in them and then some. 

Here is my connection properties out of my persistence.xml file.  Is anything amiss?


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


			<!--<property name="hibernate.default_schema" value=""/>-->
			<property name="hibernate.connection.autocommit" value="false"/>

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

Offline

#4 2013-10-01 23:27:55

Thorsten J. Krause
Guest

Re: Errors in setup

Your configuration looks fine. You could try setting

<property name="hibernate.hbm2ddl.auto" value="validate"/>

This enforces the validation of the database schema, which should produce some additional error messages. (These usually only end up in the localhost file, but your setup of course might be different)

#5 2013-10-02 12:47:54

lowreyjon
Member
From: Gainesville, FL
Registered: 2013-10-01

Re: Errors in setup

Thanks, I added this information.  This morning when I restarted the server I received this information in the localhost.XXX.log.  Looks like it cant find the jdbc driver.  Did i type something wrong specific to the driver?

INFO: ContextListener: attributeAdded('org.apache.jasper.compiler.TldLocationsCache', 'org.apache.jasper.compiler.TldLocationsCache@45e352cc')
Oct 02, 2013 8:34:32 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter guiceFilter
javax.persistence.PersistenceException: [PersistenceUnit: reportServerPU] Unable to build EntityManagerFactory
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:924)
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
	at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:59)
	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:4775)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5452)
	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:1113)
	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1671)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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)
Caused by: org.hibernate.service.classloading.spi.ClassLoadingException: HHH010003: JDBC Driver class not found: org.postgresql.jdbc.Driver
	at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:142)
	at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
	at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
	at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
	at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:223)
	at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:89)
	at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)
	at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)
	at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)
	at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1797)
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1755)
	at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96)
	at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)
	... 25 more
Caused by: org.hibernate.service.classloading.spi.ClassLoadingException: Unable to load class [org.postgresql.jdbc.Driver]
	at org.hibernate.service.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:149)
	at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:139)
	... 37 more
Caused by: java.lang.ClassNotFoundException: Could not load requested class : org.postgresql.jdbc.Driver
	at org.hibernate.service.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:296)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:270)
	at org.hibernate.service.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:146)
	... 38 more

Offline

#6 2013-10-02 13:16:19

Thorsten J. Krause
Guest

Re: Errors in setup

Oh sorry, I did not catch that yesterday, your driver_class is wrong. The correct value for postgres is

org.postgresql.Driver


Cheers,
Thorsten

#7 2013-10-02 14:56:32

lowreyjon
Member
From: Gainesville, FL
Registered: 2013-10-01

Re: Errors in setup

Thanks VERY much.  This worked! I am overjoyed.  Thank you for taking the time.  I appreciate it.  I am at the login prompt now. 

Thanks,
Jon

Offline

Board footer

Powered by FluxBB