[jbpm-dev] [Design of JBoss jBPM] - Multiple 1PC resources in enterprise

thomas.diesler@jboss.com do-not-reply at jboss.com
Thu Sep 11 04:18:16 EDT 2008


Alejandro,

https://jira.jboss.org/jira/browse/JBPM-1708

If I understand you correctly, you associated the DS for the TimerEntityBean with the JbpmDS to share the same DS with the rest of the engine and not have multiple 1PC resources enlisted.


  | <jbosscmp-jdbc>
  |   <defaults>
  |     <datasource>java:/JbpmDS</datasource>
  |     <create-table>false</create-table>
  |     <remove-table>false</remove-table>
  |     <pk-constraint>false</pk-constraint>
  |   </defaults>
  | 
  |   <enterprise-beans>
  |     <entity>
  |       <ejb-name>TimerEntityBean</ejb-name>
  | 

Using the same DS for all DB related stuff seems correct to me. 

The EjbSchedulerTest however still fails


  | Running org.jbpm.scheduler.ejbtimer.EjbSchedulerTest
  | Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 9.431 sec <<< FAILURE!
  | 
  | Caused by: org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000001:bb20:48c8d180:55 status: ActionStatus.ABORT_ONLY >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000001:bb20:48c8d180:55 status: ActionStatus.ABORT_ONLY >)
  | 	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)
  | 

There seems to be more to it than sharing the DS.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175782#4175782

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175782



More information about the jbpm-dev mailing list