AppManage deployment fails with “Could not commit with auto-commit set on”.
book
Article ID: KB0081696
calendar_today
Updated On:
Products
Versions
TIBCO Runtime Agent (TRA)
5.9.1
Description
AppManage -deploy command in a DB-based domain using ojdbc7.jar. returns the message “Server is either down or too busy to respond” with the following error appearing in Administrator.log: Error [Pool] AESDKJ-0000 [main] java.sql.SQLException: Could not commit with auto-commit set on at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:2360) at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:2407) at com.tibco.runtime.pool.jdbc.JdbcConnection.commit(JdbcConnection.java:196) at com.tibco.pof.entitystore.db.PofInitializationDB.createInitTables(PofInitializationDB.java:46) at com.tibco.pof.entitystore.db.DBEntityStore.init(DBEntityStore.java:563) at com.tibco.pof.entitystore.EntityStoreManager.a(EntityStoreManager.java:221) at com.tibco.pof.entitystore.EntityStoreManager.getEntityStore(EntityStoreManager.java:193) at com.tibco.pof.entitystore.EntityStoreManager.isInstalled(EntityStoreManager.java:408) at com.tibco.pof.admindomain.AdministrationDomain.isInstalled(AdministrationDomain.java:142) at com.tibco.administrator.command.tool.ApplicationManagement.l(ApplicationManagement.java:1769) at com.tibco.administrator.command.tool.ApplicationManagement.task(ApplicationManagement.java:222) at com.tibco.administrator.command.tool.ApplicationManagement.main(ApplicationManagement.java:157)
Issue/Introduction
AppManage -deploy command fails with the error message “Could not commit with auto-commit set on”.
Environment
ERHL 5.x
Resolution
Add the property “java.property.oracle.jdbc.autoCommitSpecCompliant=false” to AppManage.tra test. If it works, add the property to other .tra files as well like tibcoadmin_<domain_name>.tra, hawkagent_<domain_name>.tra and domainutility.tra.