Bug 779472 - JBPM-2263: Multiple timers in node cause EventSource reset
Summary: JBPM-2263: Multiple timers in node cause EventSource reset
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Deadline: 2010-03-08
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - within SOA, JBPM - standalone
Version: 5.0.0 ER7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Alejandro Guizar
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-21 07:55 UTC by Martin Weiler
Modified: 2012-07-13 04:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: SOA-1856
Environment:
Last Closed: 2010-05-12 08:26:49 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1856 0 Major Closed JBPM-2263: Multiple timers in node cause EventSource reset 2012-07-30 23:16:58 UTC

Description Martin Weiler 2010-01-21 07:55:16 UTC 
++ This bug is a clone of bug 779471 ++

Date of First Response: 2010-02-20 21:35:54
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/388093
project_key: SOA

Platform issue for JBPM-2263: Multiple timers in node cause EventSource reset
Comment 1 Martin Weiler 2010-01-21 07:55:34 UTC 
Link: Added: This issue depends JBPM-2263
Comment 2 Alejandro Guizar 2010-02-21 02:35:54 UTC 
Resolving, project issue JBPM-2263 is done.
Comment 3 David Le Sage 2010-02-25 07:01:07 UTC 
Please review the following draft text for the Resolved Issues section of the Release Notes:

https://jira.jboss.org/jira/browse/JBPM-2263

    When there were multiple timers on a node, the second and all subsequent ones would "lose" their
    relationship with the graphElement, due to a reset of the EventSource. This occured because
    the GraphElement.fireEvent() did not allow an event to "fire" whilst another event enclosed
    within it was firing. Consequently, there were serious problems with job execution times.

    To resolve this issue, the GraphElement.fireEvent() method has been changed to save
    the original event source to a local variable and then restore it once the enclosed event has
    run. As a result, the assocation between the timer and the graphElement is no longer lost and
    performance of job execution is no longer hampered.
Comment 5 Anne-Louise Tangring 2010-02-25 20:07:13 UTC 
Approved for SOA 4.3 CP03
Comment 7 trev 2010-03-30 09:45:43 UTC 
I've checked with fisheye, the fixes are in ER1.
Comment 8 Jiri Pechanec 2010-05-12 08:26:49 UTC 
Tests passing in CR2
Note You need to log in before you can comment on or make changes to this bug.