Bug 1051459
| Summary: | The first time call of a web service task is always unsuccessful | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ivo Bek <ibek> | ||||
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivo Bek <ibek> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.0 | CC: | kverlaen, rrajasek | ||||
| Target Milestone: | ER1 | ||||||
| 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:23 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: |
|
||||||
issue was caused by cached class loader that was taken while application was starting and thus using main jboss class loader instead of deployment's one. Fix was to get class loader on request basis if it was not given - when users might setup their own class loaders. jbpm master: https://github.com/droolsjbpm/jbpm/commit/162c419c551439a587601fbf9fdb3f09f909ceea 6.0.x: https://github.com/droolsjbpm/jbpm/commit/5456377c09a8c87b7137442333bf0f87f0b2994b This no longer has a target release of 6.0.0. Verified in BPMS 6.0.1.ER1 |
Created attachment 848128 [details] server log Description of problem: The first time I call a web service task, a classes from wsdl are generated but the proxy objects cause some exceptions. I have to send an another request to start a new process instance which will have the right proxy objects and the operations are done. Then it works until I restart the applications server where the processes run. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start a process with a web service task 2. See the server log for exceptions. 3. Start a new process once again - this will pass Actual results: Expected results: Additional info: