When Runnig PX, weblogic.transaction.internal.TimedOutException: Transaction Timed Out After XXX Seconds Occurs at AdminSessionBean (Doc ID 1904628.1)

Last updated on JANUARY 24, 2024

Applies to:

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

Symptoms

Below error happens while running custom Process Extension (PX)

Error

java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out after 305 seconds
BEA1-56B26DB0B4644BC89D43

Steps

Deploy custom PX by coping PX jar file to: %Agile_Home%\integration\sdk\extensions
Log into Java Client as admin user, and configure PX by going to Admin tab > Data Settings > Process Extensions
Log into Web Client, and execute the PX
The error message is displayed on the Web Client screen:
java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out after 305 seconds
BEA1-56B26DB0B4644BC89D43
Agile Application Server log shows the error stack like below. See to Doc ID:1456651.1 understand the Agile Application Server location.
Can see TimedOutException is happening at AdminSessionBean:

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!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.