My Oracle Support Banner

Timeout During MFT Purging (Doc ID 2257758.1)

Last updated on FEBRUARY 02, 2019

Applies to:

Oracle Managed File Transfer - Version 12.2.1.1.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to purge, the following error occurs:

[2017-01-31T11:39:38.748+01:00] [MFTNode1] [ERROR] [] [oracle.mft.COMMON] [tid: [ACTIVE].ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <USERID>] [ecid:<ECID>,0:9] [APP: mft-app] [partition-name: DOMAIN] [tenant-name: GLOBAL] Unable to run the threadWorkExecutor, action :startPurge[[
MFTException [threadName=[ACTIVE] ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)', errorID=<ERRORID>, errorDesc=MFT-4504_JTA Transaction Error, cause=MFTException [threadName=[ACTIVE] ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)', errorID=<ERRORID>, errorDesc=MFT-4504_JTA Transaction Error, cause=Transaction timed out after 29 seconds
]]
at oracle.tip.mft.purge.runtime.RuntimePurgeService.purgeInternal(RuntimePurgeService.java:146)
at oracle.tip.mft.init.ThreadWorkExecutor.run(ThreadWorkExecutor.java:159)
at oracle.tip.mft.init.WorkManagerExecutor$1.run(WorkManagerExecutor.java:166)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
...

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
Symptoms
Changes
Cause
Solution
References


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