Deleting Content Nodes in Bulk Using the Content Management (CM) API's Causes a weblogic.transaction.internal.TimedOutException
(Doc ID 1105572.1)
Last updated on JANUARY 16, 2025
Applies to:
Oracle WebLogic Portal - Version 9.2.0 to 10.3.0 [Release Weblogic Platform to AS10gR3]Information in this document applies to any platform.
Symptoms
When deleting content nodes in bulk using the WebLogic Portal (WLP) Content Management (CM) API, the following transaction timeout exception is thrown:
Errror message:
<Error> <ContentManagement> <msr1> <AdminServer> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <BEA1-04337C337B3D3EAEE75B> <> <1272602427089> <BEA-000000> <
com.bea.content.RepositoryException: java.sql.SQLException: The transaction is no longer active - status: 'Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 49 seconds BEA1-04337C337B3D3EAEE75B]'. No further JDBC access is allowed within this transaction.
at com.bea.content.internal.server.dao.DaoBase.doDatabaseAction(DaoBase.java:301)
at com.bea.content.virtual.internal.server.dao.NodeDao.cascadeDeleteNode(NodeDao.java:846)
at com.bea.content.virtual.internal.server.persister.JDBCVirtualPersister.delete(JDBCVirtualPersister.java:387)
at com.bea.content.virtual.internal.server.logic.VirtualOpsLogic.delete(VirtualOpsLogic.java:239)
at com.bea.content.virtual.internal.server.bean.VirtualOpsBean.delete(VirtualOpsBean.java:123)
...
at com.bea.content.manager.internal.NodeOpsImpl.deleteNode(NodeOpsImpl.java:597)
at com.bea.content.federated.internal.NodeManagerImpl.remove(NodeManagerImpl.java:552)
at portlets.test.register.TestController.deleteNode(TestController.java:1037)
at portlets.test.register.TestController.addData(TestController.java:191)
...
...
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 49 seconds BEA1-04337C337B3D3EAEE75B]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:83)
at weblogic.jdbc.wrapper.Connection.clearPreparedStatement(Connection.java:219)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:127)
at com.bea.content.internal.server.common.dbaction.ExecuteAction.runExecuteStep(ExecuteAction.java:15)
at com.bea.content.internal.server.common.dbaction.SqlStatementAction.execute(SqlStatementAction.java:117)
at com.bea.content.internal.server.dao.DaoBase.doDatabaseAction(DaoBase.java:294)
at com.bea.content.virtual.internal.server.dao.NodeDao.cascadeDeleteNode(NodeDao.java:846)
at com.bea.content.virtual.internal.server.persister.JDBCVirtualPersister.delete(JDBCVirtualPersister.java:387)
...
...
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
The above stack trace is observed while using the com.bea.portal.tools.content.controls.ContentNodeControl.remove(ContentContext context, ID nodeId) API. Please refer to the ContentNodeControl Interface for the API details.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |