java.sql.SQLException: addSync: caught Exception

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via adobe.com by Unknown author, 1 year ago
enlist: caught ExceptionchainedExceptionMessage:enlist: caught Exception chainedException trace:java.sql.SQLException: enlist: caught Exception
via Google Groups by Tuft, 1 year ago
java.sql.SQLException: addSync: caught Exception
at com.ibm.ws.Transaction.JTA.TransactionImpl.registerSynchronization(TransactionImpl.java:3546)
at com.ibm.ws.Transaction.JTA.TransactionImpl.registerSynchronization(TransactionImpl.java:3525)
at com.ibm.ws.Transaction.JTA.TranManagerSet.registerSynchronization(TranManagerSet.java:514)
at com.ibm.ejs.j2c.XATransactionWrapper.addSync(XATransactionWrapper.java:290)
at com.ibm.ejs.j2c.ConnectionManager.initializeForUOW(ConnectionManager.java:1337)
at com.ibm.ejs.j2c.ConnectionManager.involveMCInTran(ConnectionManager.java:1062)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:612)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:449)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:418)
at com.ibm.icm.ci.Datastore$DataSource.getConnection(Datastore.java:596)
at com.ibm.icm.ci.ConnectionService.getConnection(ConnectionService.java:67)
at com.ibm.icm.ts.tss.ls.BaseDBImpl$ConnectionWrapper.getConnection(BaseDBImpl.java:1408)
at com.ibm.icm.ts.tss.ls.BaseDBImpl.executeQuery(BaseDBImpl.java:252)
at com.ibm.icm.ts.tss.ls.BaseDBImpl.findUnclaimedIndex(BaseDBImpl.java:719)
at com.ibm.icm.ts.tss.ls.BaseDBImpl.claimUnprocessedIndex(BaseDBImpl.java:704)
at com.ibm.icm.ts.tss.ls.LibraryServerImpl.getIndexToUpdate(LibraryServerImpl.java:265)
at com.ibm.icm.ts.tss.ls.LibraryServerImpl.pendingReader(LibraryServerImpl.java:93)
at com.ibm.icm.ts.tss.app.IndexMaintainer.runIndexMaintenance(IndexMaintainer.java:138)
at com.ibm.icm.ts.tss.app.IndexMaintainer.checkForUpdates(IndexMaintainer.java:119)
at com.ibm.icm.ts.tss.app.IndexMaintenanceService.checkForUpdates(IndexMaintenanceService.java:65)
at com.ibm.icm.ts.tss.app.IndexMaintenanceService.access$000(IndexMaintenanceService.java:27)
at com.ibm.icm.ts.tss.app.IndexMaintenanceService$Notifiee.onEvent(IndexMaintenanceService.java:114)
at com.ibm.icm.ts.act.ActivityImpl$ManagerImpl$ActivityRunner.runActivity(ActivityImpl.java:333)
at com.ibm.icm.ts.act.ActivityImpl$ManagerImpl$ActivityRunner.run(ActivityImpl.java:303)
at com.ibm.hrl.workmanager.RunnableWrapper.run(RunnableWrapper.java:44)
at com.ibm.hrl.workmanager.impl.was.WasWork.run(WasWork.java:75)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:261)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at javax.security.auth.Subject.doAs(Subject.java:495)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:118)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:328)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:757)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:218)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:158)
at java.lang.Thread.run(Thread.java:811)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.