[jBPM] - jBPM5 Exception Handling
by dme
dme [http://community.jboss.org/people/dme] created the discussion
"jBPM5 Exception Handling"
To view the discussion, visit: http://community.jboss.org/message/633574#633574
--------------------------------------------------------------
Hi,
I have created a flow to test the Fault/Exception Handling provided by jBPM, but the fault is never handled. I have attached the Process File and the correspondign Java Driver Below.
The Exception is raised correctly, and within the sub-process I add an exception handler which maps to the Fault Code. In this Excetpion Handler I am printing a message stating that the fault was handled, but the code never reaches the exception handler. When I look at the "XML" behind the process, it does not contain the code for exception handling. Now if I close the process file and re-open it, the exception handling code does not show in Eclipse as well.
I looked at the Example "ErrorBoundaryEventInterrupting.bpmn2" and see that even in this case the Exception Handler code is not in the XML for the process. Where is this code kept and how do I fix my process to handle the fault/exceptions generated?
Thanks.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/633574#633574]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
[Datasource Configuration] - E_FAILED_TO_GET_DATASOURCE Error - JBoss & Filenet
by jonis1974
jonis1974 [http://community.jboss.org/people/jonis1974] created the discussion
"E_FAILED_TO_GET_DATASOURCE Error - JBoss & Filenet"
To view the discussion, visit: http://community.jboss.org/message/633683#633683
--------------------------------------------------------------
Hi everybody,
since April 2009 we've got a J2EE application that accesses a Filenet P8 Content Engine (4.0
) running on a JBoss AS.
We had not had any problems with the infraestructure until a month ago, when the activity (accesses) in the Filenet system increased. Since this happened we have seen that in the JBoss logs always appears the message:
"+2011-10-25 08:58:19,172 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: public abstract com.filenet.apiimpl.transport.ExecuteChangesResponse com.filenet.engine.ejb.EngineCoreLocal.executeChanges(com.filenet.apiimpl.transport.ClientCallContext,com.filenet.apiimpl.transport.ExecuteChangesRequest):+
+com.filenet.api.exception.EngineRuntimeException: E_FAILED_TO_GET_DATASOURCE: Failed to get DataSource java:jdbc/PoolDarXA."+
A week ago we increased the size of the connection pool and we have seen that the pool is big enough now to support the users accessing the system, but the problem and the message still appear.
We have also seen that other error messages appear mixed with the one stated before:
"+2011-10-25 08:58:19,157 WARN [org.jboss.tm.TransactionImpl] XAException: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=WNDARP02/83, BranchQual=, localId=83] errorCode=XA_UNKNOWN(0)+
+javax.transaction.xa.XAException: java.sql.SQLException: DTC_XA_START:No transaction cookie returned+"
"+2011-10-25 08:58:19,172 WARN [org.jboss.tm.TransactionImpl] XAException: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=WNDARP02/83, BranchQual=, localId=83] errorCode=XA_UNKNOWN(0)+
+javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***+"
The database is MS SQL Server (version 9.00.3042), the driver is MS SQL Server 2005 JDBC Driver (version 1.2.2828.203) and the datasource configurations are:
<datasources>
<xa-datasource>
<jndi-name>jdbc/PoolDarXA</jndi-name>
<track-connection-by-tx></track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
<xa-datasource-property name="ServerName">10.30.2.234</xa-datasource-property>
<xa-datasource-property name="PortNumber">1433</xa-datasource-property>
<xa-datasource-property name="DatabaseName">CE_DAR</xa-datasource-property>
<xa-datasource-property name="SelectMethod">cursor</xa-datasource-property>
<user-name>ce_login</user-name>
<password>XXXXXXX</password>
<min-pool-size>10</min-pool-size>
<max-pool-size>100</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
<check-valid-connection-sql>select count(*) from SysObjects</check-valid-connection-sql>
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<metadata>
<type-mapping>MS SQLSERVER</type-mapping>
</metadata>
</xa-datasource>
</datasources>
<datasources>
<xa-datasource>
<jndi-name>jdbc/PoolGCDJ_XA</jndi-name>
<track-connection-by-tx></track-connection-by-tx>
<isSameRM-override-value>false</isSameRM-override-value>
<xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
<xa-datasource-property name="ServerName">10.30.2.234</xa-datasource-property>
<xa-datasource-property name="PortNumber">1433</xa-datasource-property>
<xa-datasource-property name="DatabaseName">GCDJ</xa-datasource-property>
<xa-datasource-property name="SelectMethod">cursor</xa-datasource-property>
<user-name>ce_login</user-name>
<password>XXXXXXX</password>
<min-pool-size>10</min-pool-size>
<max-pool-size>50</max-pool-size>
<check-valid-connection-sql>select count(*) from SysObjects</check-valid-connection-sql>
<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<metadata>
<type-mapping>MS SQLSERVER</type-mapping>
</metadata>
</xa-datasource>
</datasources>
I would like to know if anybody knows what else has to be done just not to get these datasource access errors. If you need more information to help me solve the problem please tell me. Thank you in advance.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/633683#633683]
Start a new discussion in Datasource Configuration at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
