Too Many Items in the PTODOITEMS Table where instId=-4444 Causing Performance Problems (Doc ID 848096.1)

Last updated on JUNE 19, 2014

Applies to:

Oracle Business Process Management Suite - Version 5.7 to 10.3.1
Information in this document applies to any platform.
***Checked for relevance on 14-Jun-YYYY***

Symptoms

The engine or other aspects of the BPM environment may appear to be slow. The database may also appear to have an excessive load coming from the BPM engine.  You may see a high count of rows in the PTODOITEMS table where instid=-4444.  You may also find messages that look like the following in the engine logs:

The Server is running out of Automatic Execution Threads ( 98 % of the pool is in use). It is recommendable to expand the size through the Process Administrator.

 

Executing item: UNSELECT Inst (235,-4444,-1) Act [ActivityName] Proc [No process] Due [2009-06-22 22:13:55+01:00 1245705235000000] TimeStamp [2009-06-22 22:11:55+01:00] id[14753097] later [true]

 

Inconsistency found, trying to delete Automatic Item [UNSELECT Inst (235,-4444,-1) Act [ActivityName] Proc [No process] Due [2009-06-22 22:13:55+01:00 1245705235000000] TimeStamp [2009-06-22 22:11:55+01:00] id[14753135] later [true]]
(Rows Deleted : 0)
Rows found: Details:
Trace: at fuego.server.persistence.jdbc.JdbcToDoItemPersMgr.printError(JdbcToDoItemPersMgr.java:1055)
+: at fuego.server.persistence.jdbc.JdbcToDoItemPersMgr.delete(JdbcToDoItemPersMgr.java:796)
+: at fuego.server.persistence.Persistence.deleteToDoItem(Persistence.java:750)
+: at fuego.server.execution.AbstractToDoQueue.persist(AbstractToDoQueue.java:74)
+: at fuego.server.execution.EngineExecutionContext.persistToDoItems(EngineExecutionContext.java:1888)
+: at fuego.server.execution.EngineExecutionContext.persist(EngineExecutionContext.java:1111)
+: at fuego.transaction.TransactionAction.beforeCompletion(TransactionAction.java:132)
+: at fuego.connector.ConnectorTransaction.beforeCompletion(ConnectorTransaction.java:685)
+: at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:368)
+: at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
+: at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
+: at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
+: at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
+: at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
+: at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:63)
+: at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
+: at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:264)
+: at fuego.server.execution.ToDoItem.run(ToDoItem.java:559)
+: at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:773)
+: at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:753)
+: at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
+: at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
+: at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446)
+: at fuego.component.ExecutionThread.work(ExecutionThread.java:837)
+: at fuego.component.ExecutionThread.run(ExecutionThread.java:408)

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