Content Management and Capture

 View Only

 CPE database time out erros due to custom subscription process

John Bourdeau's profile image
John Bourdeau posted Tue November 11, 2025 08:45 AM

Hi,

We have a subscription that is getting time out errors and we are trying to understand why.  I've followed a tech note sugesting the following in WAS.

  • Increase total transaction lifetime timeout and maximum transaction timeout to 600 seconds
  • Increase ORB services transaction timeout to 900 seconds

However, the values already in these fields do not represent 120 seconds, so I'm a little skeptical. Does anyone know why we would be getting the following error:

[11/7/25 8:57:24:434 EST] 00000038 TimeoutManage I   WTRN0006W: Transaction 0000019A5E99BA95000000017A095EB431D24CE592E49312D9D0133DADED1609D2DE79C20000019A5E99BA95000000017A095EB431D24CE592E49312D9D0133DADED1609D2DE79C200000001 has timed out after 120 seconds.[11/7/25 8:57:24:434 EST] 00000038 TimeoutManage I   WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[QueueItemExecutor_OS1_Worker background task processing19,5,CE background processing for worker tasks]. The stack trace of this thread when the timeout occurred was: java.lang.Thread.sleepImpl(Native Method) java.lang.Thread.sleep(Thread.java:977) java.lang.Thread.sleep(Thread.java:960) com.enchoice.pdf.AIEnableEventActionHander.onEvent(AIEnableEventActionHander.java:55) com.filenet.engine.handlers.EventActionWrapper$1.run(EventActionWrapper.java:63) com.filenet.engine.handlers.HandlerFactory$HandlerWrapper$1.run(HandlerFactory.java:327)

Michael Seaman's profile image
Michael Seaman

If you have a particularly long-running event handling process you can configure a specific transaction timeout for that which is independent of the normal application server settings. You do this through the CmTransactionTimeout property of the Event Action object.