Data Sources File Can Be Corrupted When Using Ascontrol In 10.1.3 To Edit a Connection Pool (Doc ID 802283.1)

Last updated on JULY 13, 2017

Applies to:

Enterprise Manager for Fusion Middleware - Version and later
Oracle Containers for J2EE - Version and later
Information in this document applies to any platform.
***Checked for relevance on 16-Dec-2013***


Problem Statement:
When using the ascontrol interface to update the data sources configuration, often the data-sources.xml configuration file becomes empty (0 bytes), and it is no longer possible to start the OC4J instance.
Restoring a copy of the file allows the instance to be restarted as normal. The only workaround to this is manually editing the file.

Steps To Reproduce:

With customer provided test case:

1. Create a new OC4J instance (oc4j_temp)
2. Go to oc4j_temp > Administration > JDBC Resources
3. Click on "Example Connection Pool" to edit it.
4. Change the URL and username/password. I entered the following:

URL: jdbc:oracle:thin:@//<testdbHostname>:<port>/<testdbServiceName>
Username: <testuser>
Cleartext password: <testpwd>

5. Apply the changes. Return to the home screen and restart the OC4J instance.
6. Prepare the instance for deployment by adding appropriate jms queues:

cp jms.xml ../../oc4j_temp/config/
opmnctl reload

7. Go to oc4j_temp > Administration > Server Properties and adjust the max heap size to at least 512m.
8. Restart the OC4J instance again.
At that point it was checked data-sources.xml , and it was correct
9. Go to the applications screen, click deploy.
10. Supply the test.ear file and deployment plan.
11. Use the application name framework, and the URL binding /temp
12. Deploy the application.
At that point it was checked data-sources.xml , and it was correct
13. Go to oc4j_temp > Administration > JDBC Resources
14. Change the username and password. Press apply.
At that point it was checked data-sources.xml , and it is an empty file (0 byte)

At that point accessing with ASControl to "oc4j_temp > Administration > JDBC Resources" and editing the
Example Connection Pool file is possible,  even testing the connection pool is successful, however the
data-sources.xml file at the ./config directory is completely empty.

Business Impact:
Administration of JDBC resources becomes dangerous and unstable as the data-sources.xml
configuration file can be easily corrupted


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