Troubleshooting
Problem
When WebSphere Adapter for JDBC 6.1 outbound attemps to connect to an Oracle 11g database at runtime, it sometimes fails with an error.
Symptom
The following error displays:
com.ibm.j2ca.jdbc.JDBCManagedConnection initializeConnectionFromJNDI
CWYBC0201E: The adapter failed to establish a connection to the database
for the following reason: ORA-01017: invalid username/password; logon
denied
DSRA0010E: SQL State = 72000, Error Code = 1,017. Explanation=The
adapter failed while attempting to establish a connection to the
database. The problem might be in the driver, the database, or the user
credentials provided. The reason stated in the error message can help
you identify the problem area. UserAction=Analyze the reason for the
failure to establish a connection, and fix the related setup problems.
[9/18/10 2:20:05:426 PDT] 000000ec LogUtils E
com.ibm.j2ca.jdbc.JDBCManagedConnection getWBIConnection CWYBC0201E: The
adapter failed to establish a connection to the database for the
following reason: ORA-01017: invalid username/password; logon denied
DSRA0010E: SQL State = 72000, Error Code = 1,017. Explanation=The
adapter failed while attempting to establish a connection to the
database. The problem might be in the driver, the database, or the user
credentials provided. The reason stated in the error message can help
you identify the problem area. UserAction=Analyze the reason for the
failure to establish a connection, and fix the related setup problems.
[9/18/10 2:20:05:428 PDT] 000000ec ExceptionUtil E CNTR0020E: EJB
threw an unexpected (non-declared) exception during invocation of method
"transactionNotSupportedActivitySessionNotSupported" on bean
"BeanId(eCAS-AirPlaneDataApp#eCAS-AirPlaneDataEJB.jar#Module, null)".
Exception data: javax.resource.ResourceException: ORA-01017: invalid
username/password; logon denied
DSRA0010E: SQL State = 72000, Error Code = 1,017
at
com.ibm.j2ca.jdbc.JDBCManagedConnection.getWBIConnection(JDBCManagedConn
ection.java:721)
at
com.ibm.j2ca.base.WBIManagedConnection.getConnection(WBIManagedConnectio
n.java:263)
at
com.ibm.j2ca.base.internal.WBIDefaultConnectionManager.allocateConnectio
n(WBIDefaultConnectionManager.java:58)
at
com.ibm.j2ca.base.WBIConnectionFactory.getConnection(WBIConnectionFactor
y.java:74)
at
com.ibm.j2ca.jdbc.JDBCConnectionFactory.getConnection(JDBCConnectionFact
ory.java)
at
com.ibm.ws.sca.internal.j2c.J2CInterfaceBindingImpl.invoke(J2CInterfaceB
indingImpl.java:114)
at
Cause
The imports containing both the Datasource JNDI and the local values database URL (user / password) are failing, while all of the other imports only specify the Datasource JNDI.
Under a heavy workload, WebSphere Adapter for JDBC sometimes reverts back to using the local credentials, when it should be using the Datasource. This can possibly happen when the Datasource runs out of connections.
When this occurs, the local credentials are not valid and give a login error.
Resolving The Problem
To avoid this issue, you need to modify the WebSphere Adapter for JDBC connection factory to use either the DataSource JNDI, or the local values, not both.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21472503