Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-3816

Get an HibernateException in JbpmJobExector when starting 4.11 out of the box

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 4.11
    • Fix Version/s: None
    • Component/s: Deployment
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      clean install the downloaded 4.11 zip on Windows 7 and start it without any changes.

      Show
      clean install the downloaded 4.11 zip on Windows 7 and start it without any changes.

      Description

      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)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                osundblad Olle Sundblad (Inactive)
              • Votes:
                4 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: