[
https://issues.jboss.org/browse/JBESB-3816?page=com.atlassian.jira.plugin...
]
Ian Walker commented on JBESB-3816:
-----------------------------------
Just installed JBoss AS 5.1.0.GA + JBoss ESB 4.12 on RHEL 6.2 and got the same Hiberate
error. Running with debug logging turned on, I get the following:
{noformat}
16:29:56,867 INFO [Configuration] configuring from resource: hibernate.cfg.xml
16:29:56,867 INFO [Configuration] Configuration resource: hibernate.cfg.xml
16:29:56,869 DEBUG [DTDEntityResolver] trying to resolve system-id
[
http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd]
16:29:56,869 DEBUG [DispatcherThread] failed to retrieve next waiting due job
org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1528)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1462)
at
org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
at
org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
at
org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
at
org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
at
org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
at
org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
at
org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
at
org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
at org.jbpm.svc.Services.getService(Services.java:160)
at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
at
org.jbpm.job.executor.DispatcherThread.getNextDueDateWithinIdleInterval(DispatcherThread.java:193)
at org.jbpm.job.executor.DispatcherThread.run(DispatcherThread.java:70)
Caused by: org.dom4j.DocumentException:
www.hibernate.org Nested exception:
www.hibernate.org
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1518)
{noformat}
Looking through the installed JBoss ESB 4.12, I found {{www.hibernate.com...}} in the
{{deploy/jbpm.esb/hibernate.cfg.xml}}.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://www.hibernate.org/dtd/hibernate-configuration-3.0.dtd">
{code}
Changing {{hibernate.cfg.xml}} to the following (taken from ESB 4.10) seems to fix the
problem on both RHEL and Windows.
{code:xml}
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd">
{code}
Get an HibernateException in JbpmJobExector when starting 4.11 out of
the box
-----------------------------------------------------------------------------
Key: JBESB-3816
URL:
https://issues.jboss.org/browse/JBESB-3816
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment
Affects Versions: 4.11
Environment: Windows 7
Reporter: Olle Sundblad
When I download and install (unzip) the 4.11 release and start it using run.bat without
any changes whatsoever I get the following stacktrace over and over again.
end of start console (it started with no errors/warnings):
09:57:16,666 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
09:57:16,677 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build:
SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 28s:270ms
but immediately after I get the following:
09:57:31,928 INFO [Configuration] configuring from resource: hibernate.cfg.xml
09:57:31,929 INFO [Configuration] Configuration resource: hibernate.cfg.xml
09:57:52,939 INFO [Configuration] configuring from resource: hibernate.cfg.xml
09:57:52,940 INFO [Configuration] Configuration resource: hibernate.cfg.xml
09:57:52,939 ERROR [LockMonitorThread] exception in
JbpmJobExector@138.106.178.133:Monitor
org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1494)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1428)
at
org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89)
at
org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:75)
at
org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:104)
at
org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:93)
at
org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionManager(JtaDbPersistenceService.java:100)
at
org.jbpm.persistence.jta.JtaDbPersistenceService.getTransactionStatus(JtaDbPersistenceService.java:88)
at
org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:50)
at
org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:61)
at org.jbpm.svc.Services.getService(Services.java:160)
at org.jbpm.svc.Services.getPersistenceService(Services.java:197)
at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:695)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:639)
at
org.jbpm.job.executor.LockMonitorThread.unlockOverdueJobs(LockMonitorThread.java:64)
at org.jbpm.job.executor.LockMonitorThread.run(LockMonitorThread.java:43)
Caused by: org.dom4j.DocumentException: Connection timed out: connect Nested exception:
Connection timed out: connect
at org.dom4j.io.SAXReader.read(SAXReader.java:484)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1484)
... 15 more
This repeats over and over again until I stop the server.
I do not get this exception in 4.10 (so my unqualified guess is the jbpm5 stuff is
missing the hibernate.cfg.xml or something)
--
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