Bug 1102802
| Summary: | Errors in server.log while using the same curl commands for project deploy with PPI strategy | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jiri Svitak <jsvitak> | ||||||
| Component: | Business Central | Assignee: | Shelly McGowan <smcgowan> | ||||||
| Status: | CLOSED EOL | QA Contact: | Marek Baluch <mbaluch> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.2 | CC: | ibek, kverlaen, mbaluch | ||||||
| Target Milestone: | --- | Keywords: | Regression | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-03-27 19:44:29 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 900399 [details]
server.log
application-users.properties: guest=b5d048a237bfd2874b6928e1f37ee15e application-roles.properties: guest=admin Hi Jiri, Good eyes! Fortunately, there are no problems here. I'm simply logging too much. In my haste to get the fix in, I left a little too much logging in. When this BZ is moved to 6.1, I'll fix the code to make sure the logging is clearer and less verbose, and then set it to modified. FYI: - "Instance 2 of the DynamicJaxbContext created": For some reason the DynamicJaxbContext (@ApplicationScoped) class is instantiated twice -- but only one of them is used, so it's fine. I need to set this to debug or delete it. - "No JAXBContext available for deployment": when the deployment hasn't been deployed yet, then no JAXBContext can be created on the basis of the deployment (because it isn't deployed yet.. :) ). This message should only be shown when doing something with the deployment (startprocess, etc.), not during deployment operations where the input/output doesn't contain any class instances from the deployment. I need to fix the code to do that. - "Unable to retrieve status of job com.bpms.flood:bpms-perf:1.0.0.Final/DEPLOY": this is logged when the Future object returned by the jbpm-executor (which is asynchronously deploying or undeploying the job), times out on a get. It just means that the job is still running (status "DEPLOYING", not "DEPLOYED"). I will also fix this in 6.1. eh, sorry. Mixed things up a little: - the Future object (see above) is *not* from jbpm-executor in 6.0.x, but it is from an asynchronous thread (ExecutorService). So it's still a Future object. (in 6.0.x, the async jobs (knowledge store and BPMS deploy) are run by the jbpm-executor code from Maciej). Hi Marco, Great, good to know. Thanks for the detailed reply! Fyi: I have tested this again with BPMS 6.0.2.CR2 and only one of the error messages persists: 13:32:54,044 ERROR [org.kie.remote.services.rest.jaxb.DynamicJaxbContext] (http-localhost.localdomain/127.0.0.1:8080-1) Instance 2 of the DynamicJaxbContext created! Jiri, could you test this one more time?
The exception that you mention ("Instance 2 of the DynamicJaxbContext"...) is not related to this bug.
Thanks.
It is a long time since this issue has been reported. I believe this bugzilla tracks an outdated problem and I have not seen these errors recently on project deploy. I consider this bugzilla as resolved. If there are some errors on project deploy, new bugzilla will be filed. Verified in BPMS 6.1.0.ER2. |
Created attachment 900396 [details] setupDeployment.sh I use the same curl commands to initialize BPMS instance since v6.0.0. I have tried only with ER3 (in 6.0.2 context), but the following errors appear. I don't know, perhaps they related just to errors already reported by Ivo: 08:37:35,551 ERROR [org.kie.remote.services.rest.jaxb.DynamicJaxbContext] (http-/0.0.0.0:8080-1) Instance 2 of the DynamicJaxbContext created! 08:37:45,734 ERROR [org.kie.remote.services.rest.jaxb.DynamicJaxbContext] (http-/0.0.0.0:8080-1) No JAXBContext available for deployment 'com.bpms.flood:bpms-perf:1.0.0.Final', using default JAXBContext instance. 08:37:46,746 ERROR [org.kie.remote.services.rest.jaxb.DynamicJaxbContext] (http-/0.0.0.0:8080-1) No JAXBContext available for deployment 'com.bpms.flood:bpms-perf:1.0.0.Final', using default JAXBContext instance. 08:37:46,748 WARN [org.kie.remote.services.rest.async.AsyncDeploymentJobExecutor] (http-/0.0.0.0:8080-1) Unable to retrieve status of job com.bpms.flood:bpms-perf:1.0.0.Final/DEPLOY The script with curl commands used has been attached. BPMS on EAP instance need to be already setup, with user guest and password guest. I can provide setup scripts to do that. Current behavior: Error messages are in server.log. However the project is deployed correctly with desired PPI strategy. Expected behavior: Project is deployed without any errors in the log. My env: BPMS 6.0.2.ER3 EAP 6.1.1