Cannot get a connection to RES database after RES server restart

Technote (troubleshooting)


Problem(Abstract)

Rule invocation fails each time after the RES server is restarted due to database connection failure. After running RES diagnostics, rule invocation begins to run successfully until the next time when the server is restarted.

Symptom

The following error occurs on the client side:
Error in session ilog.rules.res.session.impl.ejb3.IlrStatelessSessionRemote
ilog.rules.res.session.IlrSessionException: An error occurred while the rule session was invoked.:
ilog.rules.res.xu.ruleset.impl.archive.IlrRulesetArchiveInformationException: ilog.rules.res.xu.messages, Message code: XU.ERROR.10050, parameters: datasource
ilog.rules.res.persistence.IlrDAOException: DAO.ERROR.1002 - Cannot get a connection to the database.
java.sql.SQLException: Invalid Oracle URL specifiedDSRA0010E: SQL State = 99999, Error Code = 17,067

The following stack trace is observed on the server side:

javax.resource.spi.ResourceAllocationException: DSRA8100E: Unable to get a XAConnection from the DataSource.
...
Caused by: java.sql.SQLException: Invalid Oracle URL specifiedDSRA0010E: SQL State = 99999, Error Code = 17,067


Cause

A possible cause for this behavior is that the J2C authentication data for RES datasource is not configured properly.


Resolving the problem

Verify the following in WAS admin console, Resources > JDBC and Data sources configuration for resdatasource:
1. Under Related Items > JAAS - J2C authentication data, Alias, User ID, and Password are defined.

Open Resources > JDBC and Data sources and click resdatasource
2. Alias defined in step1 is selected in the field Authentication Alias for XA recovery
3. Database user defined in step1 is given XA recovery privileges by your DBA.
4. If the issue persists, from resdatasource, click Additional Properties > Custom properties
Add user, whose value is the database user and password, whose value is the database password

Test connection on the datasource after the server is restarted and verify the test passes successfully .

After completing the aforementioned steps, should the behavior continue to occur upon rule invocation, contact IBM Support for further assistance.

Related information

XA Transaction Recovery


Cross reference information
Segment Product Component Platform Version Edition
Business Integration IBM Operational Decision Manager Platform Independent 8.0.1, 8.0, 7.5

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere ILOG JRules
Modules:Execution Server (BRES / RES)

Software version:

7.0, 7.1

Operating system(s):

Platform Independent

Reference #:

1623272

Modified date:

2013-02-01

Translate my page

Machine Translation

Content navigation