Bug 1074483
| Summary: | Web service task with ASYNC mode fails with javax.persistence.TransactionRequiredException | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||||
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.1 | CC: | kverlaen, mbaluch, mbiarnes, rrajasek | ||||||
| Target Milestone: | CR1 | ||||||||
| Target Release: | 6.0.1 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 20:03:41 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: |
|
||||||||
Created attachment 872627 [details]
error stacktrace
fixed by making use of RuntimeManager for async work item completion if available jbpm master: https://github.com/droolsjbpm/jbpm/commit/4cac63f044346187e2f8527fffddf9ac411036c8 6.0.x: https://github.com/droolsjbpm/jbpm/commit/cfa4d56f116364b8035671f5b9176f7e6b0f7021 Ticket cherry-picked into 6.0.1.CR1. Commit: 55e83b0f619ce876726b0f5bf485e360715c9dc6 Verified with BPMS-6.0.1.CR1 |
Created attachment 872626 [details] process definition with ASYNC WS task Having a process definition with WS task configured to operate in ASYNC mode, javax.persistence.TransactionRequiredException raises when the process is being executed in business-central. See the attached process definition and stacktrace. Steps to Reproduce: 1. start a business-central 2. opem jbpm designer, import attached process definition, save 3. build & deploy project, start the process definition and check the server log for errors.