roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ROL-1967) Fresh Roller-5.1-snapshot can't start in Tomcat7
Date Wed, 07 Aug 2013 17:36:48 GMT

    [ https://issues.apache.org/jira/browse/ROL-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732198#comment-13732198
] 

Glen Mazza commented on ROL-1967:
---------------------------------

Actually, we need to be on Hibernate for the next couple of weeks to spot errors with that.
 User can rebuild with EclipseLink active if he wishes to use that, or add lines 12-13 here
for his roller-custom.properties to make Hibernate happy:  
http://svn.apache.org/viewvc/roller/trunk/app/src/test/resources/roller-custom.properties?view=markup#l12
                
> Fresh Roller-5.1-snapshot can't  start in Tomcat7
> -------------------------------------------------
>
>                 Key: ROL-1967
>                 URL: https://issues.apache.org/jira/browse/ROL-1967
>             Project: Roller
>          Issue Type: Bug
>          Components: Installation, JPA Backend
>    Affects Versions: 5.1
>         Environment: JDK 7,windows 7
>            Reporter: 杨勐
>            Assignee: Dave Johnson
>            Priority: Critical
>
> A fresh Roller installation can't start  in tomcat7,  roler logs sFATAL 2013-08-07 17:59:12,205
JPAPropertiesManagerImpl:initialize - Failed to initialize runtime configuration properties.Please
check that the database has been upgraded!
> org.hibernate.service.jndi.JndiException: unable to find transaction manager
> 	at org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform.locateTransactionManager(JBossAppServerJtaPlatform.java:62)
> 	at org.hibernate.service.jta.platform.internal.AbstractJtaPlatform.retrieveTransactionManager(AbstractJtaPlatform.java:104)
> 	at org.hibernate.service.jta.platform.internal.AbstractJtaPlatform.getTransactionManager(AbstractJtaPlatform.java:115)
> 	at org.hibernate.service.jta.platform.internal.TransactionManagerBasedSynchronizationStrategy.canRegisterSynchronization(TransactionManagerBasedSynchronizationStrategy.java:56)
> 	at org.hibernate.service.jta.platform.internal.AbstractJtaPlatform.canRegisterSynchronization(AbstractJtaPlatform.java:148)
> 	at org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.attemptToRegisterJtaSync(TransactionCoordinatorImpl.java:240)
> 	at org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.pulse(TransactionCoordinatorImpl.java:269)
> 	at org.hibernate.internal.SessionImpl.pulseTransactionCoordinator(SessionImpl.java:2114)
> 	at org.hibernate.internal.SessionImpl.checkTransactionSynchStatus(SessionImpl.java:2108)
> 	at org.hibernate.internal.SessionImpl.getFlushMode(SessionImpl.java:1402)
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.setDefaultProperties(AbstractEntityManagerImpl.java:273)
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.postInit(AbstractEntityManagerImpl.java:181)
> 	at org.hibernate.ejb.EntityManagerImpl.<init>(EntityManagerImpl.java:89)
> 	at org.hibernate.ejb.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:193)
> 	at org.hibernate.ejb.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:188)
> 	at org.apache.roller.weblogger.business.jpa.JPAPersistenceStrategy.getThreadLocalEntityManager(JPAPersistenceStrategy.java:238)
> 	at org.apache.roller.weblogger.business.jpa.JPAPersistenceStrategy.getEntityManager(JPAPersistenceStrategy.java:225)
> 	at org.apache.roller.weblogger.business.jpa.JPAPersistenceStrategy.getNamedQuery(JPAPersistenceStrategy.java:258)
> 	at org.apache.roller.weblogger.business.jpa.JPAPropertiesManagerImpl.getProperties(JPAPropertiesManagerImpl.java:116)
> 	at org.apache.roller.weblogger.business.jpa.JPAPropertiesManagerImpl.initialize(JPAPropertiesManagerImpl.java:76)
> 	at org.apache.roller.weblogger.business.WebloggerImpl.initialize(WebloggerImpl.java:360)
> 	at org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(RollerContext.java:157)
> 	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791)
> 	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> 	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:618)
> 	at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1100)
> 	at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1618)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> 	at java.util.concurrent.FutureTask.run(Unknown Source)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: org.hibernate.service.jndi.JndiException: Unable to lookup JNDI name [java:jboss/TransactionManager]
> 	at org.hibernate.service.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:68)
> 	at org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform.locateTransactionManager(JBossAppServerJtaPlatform.java:55)
> 	... 35 more
> Caused by: javax.naming.NameNotFoundException: Name [jboss/TransactionManager] is not
bound in this Context. Unable to find [jboss].
> 	at org.apache.naming.NamingContext.lookup(NamingContext.java:820)
> 	at org.apache.naming.NamingContext.lookup(NamingContext.java:154)
> 	at org.apache.naming.SelectorContext.lookup(SelectorContext.java:135)
> 	at javax.naming.InitialContext.lookup(Unknown Source)
> 	at org.hibernate.service.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:65)
> 	... 36 moreays:

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message