3 Replies Latest reply on Nov 18, 2005 5:51 AM by Jens Briesofsky

    Deployment to Jboss 4.0.3SP1

    Jens Briesofsky Newbie

      Hi All,

      I just had some quite unenjoyable time trying to deploy jbpm and the webapp into an already existing jboss-4.0.3SP1 installtion. Although it should have been quite trivial it took me two days.
      At first I thought the reason was that I tried to use a PostgreSQL datasource - but after changing it back to the DefaultDS the problem persisted.

      Symptoms were: after about 90 seconds running time (webapp functional until then) I got the following errors in the log:

      [JDBCExceptionReporter] No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))
      06:30:05,062 INFO [SchedulerThread] runtime exception while executing timers
      org.hibernate.exception.GenericJDBCException: Cannot open connection
      at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:91)
      at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:79)
      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:307)
      at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:109)
      at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:134)
      at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57)
      at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1236)
      at org.jbpm.tc.hibernate.HibernateTransactionInterceptor.begin(HibernateTransactionInterceptor.java:32)
      at org.jbpm.tc.ContextBuilder.begin(ContextBuilder.java:132)
      at org.jbpm.scheduler.impl.SchedulerThread.executeTimers(SchedulerThread.java:67)
      at org.jbpm.scheduler.impl.SchedulerThread.run(SchedulerThread.java:35)
      Caused by: org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ))
      at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:79)
      at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
      at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:304)
      ... 8 more
      Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )
      at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:246)
      at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:410)
      at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:342)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:462)
      at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:894)
      at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:73)
      ... 10 more

      after unsuccessfully trying numerous things i examined the log files more closely and found that the deployment on the starters kit reported
      "ConnectionReleaseMode=null" whereas the 4.0.3SP1 reported
      "ConnectionReleaseMode=auto".
      It turned out that the reason was the version of Hibernate deployed on 4.0.3.SP1 which is Hibernate 3.1 - it was required to revert this back to Hibernate 3.1 Beta3 (as in the starters kit) to get things running...

      Hope this helps to save others some headace...

      Jens