dyn/admin's JDBCBrowser Commits SQL When you click the "Execute and Rollback" Button

(Doc ID 1683863.1)

Last updated on DECEMBER 22, 2016

Applies to:

Oracle Commerce Platform - Version 10.1.1 and later
Information in this document applies to any platform.


Statement of Issue:
The dyn/admin's jdbcbrowser commits SQL when you click the "Execute and Rollback" button.
If your datasource is configured to return autocommit connections by default then you may get an error saying you can't rollback in autocommit mode and the SQL is committed.
If not then the SQL is commited, not rolled back, despite "Execute and Rollback" being clicked.

Oracle Commerce 10.1.1
on JBoss EAP 5.1.0
using oracle.jdbc.xa.client.OracleXADataSource

1. Navigate to http://host:port/dyn/admin/nucleus/atg/dynamo/admin/jdbcbrowser/ConnectionPoolPointer/ and ensure autocommit=false
2. Navigate to http://host:port/dyn/admin/atg/dynamo/admin/en/jdbcbrowser/executeQuery.jhtml and enter some SQL to create a visible change in a repository item
3. Click Execute and Rollback button
4. Inspect the repository item's data columns using an SQL client and you see the update is committed

Expected Behavior:
The SQL is executed and if successful then rolled back.

Actual Behavior:
The SQL is executed and committed.

Business Impact:
Administrators cannot use this part of the dyn/admin application to test their SQL.
Administrators should never modify the ATG tables using SQL so this is considered low impact.


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