BPEL Process Manager Connection Pool Password Is Corrupted When Connection Pool Properties Are Changed
Last updated on MARCH 08, 2017
Applies to:Oracle(R) BPEL Process Manager - Version 10.1.3.3 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 24-Jul-2012***
This problem can occur on any platform.
When you uses indirect password and then update JDBC resource attributes from application server console (EM Console), oc4j's JDBC password becomes corrupt. Restarting oc4j is required to fix this problem.
-- Steps to reproduce the issue:
1. In the data-sources.xml file, configure a transactional datasource and connection pool for connecting to Oracle database.
2. Use the "password indirection" to secure the password in the connection pool.
3. Now restart the OC4J server, try to access the connection pool from an application (In this case BPEL). The connection to database should be successful.
4. Go to the application server admin console (EM Console) and change the connection pool property (for example change minimum connections from 0 to 1 and maximum connections from -1 to 10).
5. Try to access the database connection from the application, now you will see that connection is not successful.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms