Weblogic.transaction.internal.TimedOutException From NotifyTask (Doc ID 1930627.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Agile PLM Framework - Version 9.3.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 9.3.2.0 version, Application Server

When attempting to do any action on Agile,
the following error occurs.

ERROR
-----------------------
not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds

Transaction BEA1-002A8277FDE91C272A33 not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds
BEA1-002A8277FDE91C272A33]
java.sql.SQLException: Transaction BEA1-002A8277FDE91C272A33 not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds
BEA1-002A8277FDE91C272A33]
at weblogic.jdbc.jts.Driver.getTransaction(Driver.java:556)
at weblogic.jdbc.jts.Driver.connect(Driver.java:114)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:553)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:518)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:511)
at com.agile.util.sql.DefaultConnectionFactory.getConnFromDS(DefaultConnectionFactory.java:84)
at com.agile.util.sql.DefaultConnectionFactory.getJDBCConnection(DefaultConnectionFactory.java:48)
at com.agile.util.sql.ConnectionFactory.getConnection(ConnectionFactory.java:37)
at com.agile.pc.cmserver.base.SQLHelper.getConnection(SQLHelper.java:57)
at com.agile.pc.cmserver.notification.ChangeHistoryDAO.getNotifyUsers(ChangeHistoryDAO.java:992)
at com.agile.pc.cmserver.notification.VOChangeHistory.createCustomField(VOChangeHistory.java:633)
at com.agile.pc.cmserver.notification.VOChangeHistory.getNotifyFields(VOChangeHistory.java:524)
at com.agile.common.server.notification.NotifyService.createNotifyFields(NotifyService.java:941)
at com.agile.common.server.notification.NotifyService.send(NotifyService.java:756)
at com.agile.common.server.notification.NotifyService.send(NotifyService.java:705)
at com.agile.common.server.notification.NotifyService.send(NotifyService.java:271)
at com.agile.common.server.notification.NotifyService.send(NotifyService.java:185)
at com.agile.pc.cmserver.notification.ChangeHistoryService.sendChange(ChangeHistoryService.java:724)
at com.agile.pc.cmserver.notification.ChangeHistoryService.processChangeHistory(ChangeHistoryService.java:284)
at com.agile.pc.cmserver.notification.ChangeHistoryService.processChangeHistories(ChangeHistoryService.java:119)
at com.agile.pc.cmserver.notification.NotifyTask.processChangeHistory(NotifyTask.java:518)
at com.agile.pc.cmserver.notification.NotifyTask.run(NotifyTask.java:214)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
<2014-08-01 01:03:32,863> <ChangeHistoryService:ERROR> process change notification failed:
Transaction BEA1-002A8277FDE91C272A33 not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds
BEA1-002A8277FDE91C272A33]
java.sql.SQLException: Transaction BEA1-002A8277FDE91C272A33 not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 302 seconds
BEA1-002A8277FDE91C272A33]
at weblogic.jdbc.jts.Driver.getTransaction(Driver.java:556)
at weblogic.jdbc.jts.Driver.connect(Driver.java:114)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:553)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:518)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:511)
at com.agile.util.sql.DefaultConnectionFactory.getConnFromDS(DefaultConnectionFactory.java:84)
at com.agile.util.sql.DefaultConnectionFactory.getJDBCConnection(DefaultConnectionFactory.java:48)
at com.agile.util.sql.ConnectionFactory.getConnection(ConnectionFactory.java:37)
at com.agile.pc.cmserver.base.SQLHelper.getConnection(SQLHelper.java:57)
at com.agile.pc.cmserver.notification.ChangeHistoryDAO.getNotifyUsers(ChangeHistoryDAO.java:992)
at com.agile.pc.cmserver.notification.ChangeHistoryService.getNotifyUsers(ChangeHistoryService.java:190)
at com.agile.pc.cmserver.notification.ChangeHistoryService.processChangeHistory(ChangeHistoryService.java:206)
at com.agile.pc.cmserver.notification.ChangeHistoryService.processChangeHistories(ChangeHistoryService.java:119)
at com.agile.pc.cmserver.notification.NotifyTask.processChangeHistory(NotifyTask.java:518)
at com.agile.pc.cmserver.notification.NotifyTask.run(NotifyTask.java:214)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Do normal action to Agile
2. Check server log



Cause

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