[esb-issues] [JBoss JIRA] Closed: (JBESB-1131) jBPM does not finish clearly

Kevin Conner (JIRA) jira-events at lists.jboss.org
Mon Oct 22 06:38:03 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBESB-1131?page=all ]

Kevin Conner closed JBESB-1131.
-------------------------------

    Resolution: Done

Closing for now, may need changing depending on further jBPM work

> jBPM does not finish clearly
> ----------------------------
>
>                 Key: JBESB-1131
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1131
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Process flow
>    Affects Versions: 4.2.1 IR1
>            Reporter: Jiri Pechanec
>         Assigned To: Kevin Conner
>             Fix For: 4.2.1
>
>
> When stopping the ESB the JBPM job executor thread throws following exception.
> 13:44:54,116 WARN  [JDBCExceptionReporter] SQL Error: 0, SQLState: null
> 13:44:54,116 ERROR [JDBCExceptionReporter] You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.)
> 13:44:54,117 ERROR [JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds
> org.hibernate.exception.GenericJDBCException: Cannot open connection
>         at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
>         at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
>         at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
>         at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
>         at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426)
>         at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
>         at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119)
>         at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57)
>         at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326)
>         at org.jbpm.persistence.db.DbPersistenceService.beginTransaction(DbPersistenceService.java:132)
>         at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:124)
>         at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:359)
>         at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:563)
>         at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:112)
>         at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:58)
> Caused by: org.jboss.util.NestedSQLException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.; - nested throwable: (javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.)
>         at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:94)
>         at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
>         at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
>         ... 10 more
> Caused by: javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null.
>         at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:387)
>         at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
>         at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
>         ... 12 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list