IBM Support

Deletion of virtual portal fails with transaction timeout

Technote (troubleshooting)


Attempt to delete virtual portal via Virtual Portal Manager portlet fails with error:

EJPAH4000E: Failed to delete virtual portal

Attempts to delete the virtual portal using the ConfigEngine task "delete-virtual-portal" may fail as well.


With the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded:

  • the total and/or maximum transaction lifetime timeout value(s) for the server
  • the WCM component's transaction timeout

Diagnosing the problem

SystemOut.log may show the following:

Example #1:

[9/10/12 10:08:43:757 AMT] 0000001a TimeoutManage I   WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.

[datestamp] 00000055 JTATransactio E   RT0025E: Failed to save user transaction
Caused by: javax.transaction.RollbackException

[datestamp] 00000055 DeleteVPComma E AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred. EJPFB0002E: Exception occurred.
Caused by: javax.transaction.RollbackException

Example #2:

[datestamp] 000000f4 TimeoutManage I   WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.
[datestamp] 000000f4 TimeoutManage I   WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 8,5,main]. The stack trace of this thread when the timeout occurred was: Method)$$

Resolving the problem

1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below.

2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider:

Name: wcm.transaction.timeout

Value: 600 (for example)

Note: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.

Related information

Transaction settings
Setting Resource Environment Provider custom properties

Document information

More support for: WebSphere Portal
Virtual portals

Software version: 8.0

Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS

Reference #: 1611073

Modified date: 20 May 2015