Bug 1271904
| Summary: | TaskEventListener is not working as expected with "Per-Process-Instance and per-request" runtime strategies | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Abhijit humbe <abhumbe> | ||||
| Component: | jBPM Core | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Radovan Synek <rsynek> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.1.0 | CC: | abhumbe, kverlaen | ||||
| Target Milestone: | --- | Flags: | abhumbe:
needinfo-
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-10-16 15:03:52 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1206506 that is already fixed in 6.3.x and master shall we then close it? *** This bug has been marked as a duplicate of bug 1206506 *** |
Created attachment 1083131 [details] reproducer Description of problem: Custom task event listener firing only for "afterTaskAddedEvent" but not any of the task update events like afterTaskActivatedEvent/afterTaskClaimedEvent/afterTaskStartedEvent if we use "Per-Process-Instance/per-request" runtime strategies while deploying kjar. Its working fine with singleton runtime strategies. Version-Release number of selected component (if applicable): How reproducible: With Per-Process-Instance/per-request runtime strategies Steps to Reproduce: 1.Create custom TaskEventListener register it using kie-deployment-descriptor.xml 2. Deploy kjar with Per-Process-Instance/per-request runtime strategies 3. Start process instance and and check output Actual results: TaskEventListener not working as expected with Per-Process-Instance and per-request runtime strategies Expected results: TaskEventListener should work with all runtime strategies Additional info: Output of attached reproducer: With singleton runtime strategies ================================= INFO [stdout] (http-127.0.0.1:8080-4) **beforeTaskAddedEvent** INFO [stdout] (http-127.0.0.1:8080-4) **afterTaskAddedEvent** INFO [stdout] (http-127.0.0.1:8080-1) **beforeTaskStartedEvent** INFO [stdout] (http-127.0.0.1:8080-1) **beforeTaskCompletedEvent** INFO [stdout] (http-127.0.0.1:8080-1) **afterTaskCompletedEvent** With per-Process-Instance runtime strategies =============================== INFO [stdout] (http-127.0.0.1:8080-4) **beforeTaskAddedEvent** INFO [stdout] (http-127.0.0.1:8080-4) **afterTaskAddedEvent**