Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Process Manager (Stardust) » Warnings about skipped event handling in Stardust log file(Dangling references in AuditTrail cause massive logging output)
Warnings about skipped event handling in Stardust log file [message #758066] Mon, 21 November 2011 20:31 Go to next message
Jan Hendrik Scheufen is currently offline Jan Hendrik Scheufen
Messages: 61
Registered: October 2011
Member

I see the following warnings in the IPP log repeated over and over again.

<Nov 17, 2011 5:54:18 PM EST> <Warning> <ag.carnot.workflow.runtime.beans.AuditTrailLogger> <000000> <Skipping event handling for aborted Process instance = 3081025 (Process Definition: Engine Report Extract) (User: system_carnot_engine (Realm: system_carnot_engine) (system_carnot_engine, system_carnot_engine))>
<Nov 17, 2011 5:54:18 PM EST> <Warning> <ag.carnot.workflow.runtime.beans.AuditTrailLogger> <000000> <Skipping event handling for aborted Process instance = 3081026 (Process Definition: Engine Report Extract) (User: system_carnot_engine (Realm: system_carnot_engine) (system_carnot_engine, system_carnot_engine))>
<Nov 17, 2011 5:54:18 PM EST> <Warning> <ag.carnot.workflow.runtime.beans.AuditTrailLogger> <000000> <Skipping event handling for aborted Process instance = 3081027 (Process Definition: Engine Report Extract) (User: system_carnot_engine (Realm: system_carnot_engine) (system_carnot_engine, system_carnot_engine))>
<Nov 17, 2011 5:54:18 PM EST> <Warning> <ag.carnot.workflow.runtime.beans.AuditTrailLogger> <000000> <Skipping event handling for aborted Process instance = 3081008 (Process Definition: Engine Report Extract) (User: system_carnot_engine (Realm: system_carnot_engine) (system_carnot_engine, system_carnot_engine))>


How do you analyze and fix this?
Re: Warnings about skipped event handling in Stardust log file [message #758081 is a reply to message #758066] Mon, 21 November 2011 20:44 Go to previous message
Jan Hendrik Scheufen is currently offline Jan Hendrik Scheufen
Messages: 61
Registered: October 2011
Member

This problem was seen in older versions of Stardust (Infinity Process Platform) when process instances were aborted and entries in the EVENT_BINDING table were not cleaned up properly. Since these represent scheduled events that are obsolete (due to the process having been aborted), these entries can be removed. The following SQL statements help identifying and deleting these entries (process instance state "1" -> aborted).

select * from  PROCESS_INSTANCE p
join ACTIVITY_INSTANCE a on p.oid = a.processinstance 
join EVENT_BINDING e on a.oid = e.OBJECTOID
where e.type=1 and p.state=1;

delete from EVENT_BINDING
where OID in (select e.oid from  PROCESS_INSTANCE p
join ACTIVITY_INSTANCE a on p.oid = a.processinstance 
join EVENT_BINDING e on a.oid = e.OBJECTOID
where e.type=1 and p.state=1);
Previous Topic:IPP - Displaying Popup window for External Web UI
Next Topic:Infinity Process Plattform - installation
Goto Forum:
  


Current Time: Fri Sep 19 21:56:40 GMT 2014

Powered by FUDForum. Page generated in 0.01636 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software