Details
-
Bug
-
Resolution: Done
-
Critical
-
7.4.0.GA, 7.5.0.GA
-
None
-
Release Notes
-
CR1
-
Workaround Exists
-
-
-
2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28)
Description
When you configure Data Source on JWS container, there are some missing elements that are needed for the setup to work properly.
Currently the configuration for Oracle looks like this:
<Resource auth="Container" driverClassName="oracle.jdbc.OracleDriver" maxIdle="30" maxTotal="100" maxWaitMillis="10000" name="processServerDS" password="dballo17" type="javax.sql.DataSource" url="jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo" username="dballo17" />
it should look like this:
<Resource auth="Container" type="oracle.jdbc.xa.client.OracleXADataSource" // changed from javax.sql.DataSource maxIdle="30" maxTotal="100" maxWaitMillis="10000" name="processServerDS" password="dballo17" factory="org.apache.tomcat.jdbc.naming.GenericNamingResourcesFactory" // Added url="jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo" URL="jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo" // Added username="dballo17"/>