Eclipse Community Forums: Eclipse Process Manager (Stardust) » Warnings about skipped event handling in Stardust log file

Home » Eclipse Projects » Eclipse Process Manager (Stardust) » Warnings about skipped event handling in Stardust log file(Dangling references in AuditTrail cause massive logging output)

Show: Today's Messages :: Show Polls :: Message Navigator

Warnings about skipped event handling in Stardust log file [message #758066]

Mon, 21 November 2011 15:31

Jan Hendrik Scheufen is currently offline

Jan Hendrik Scheufen
Messages: 46
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?

Report message to a moderator

Re: Warnings about skipped event handling in Stardust log file [message #758081 is a reply to message #758066]

Mon, 21 November 2011 15:44

Jan Hendrik Scheufen
Messages: 46
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);

Report message to a moderator

Previous Topic:	IPP - Displaying Popup window for External Web UI
Next Topic:	Infinity Process Plattform - installation

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 12:09:29 EDT 2013