Bug 1011482
| Summary: | REST API: Inconsistent response type for error message | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Sona Mala <smala> | ||||||
| Component: | Business Central | Assignee: | Toni Rikkola <trikkola> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Svitak <jsvitak> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.0.0 | CC: | etirelli, mbaluch, smala | ||||||
| Target Milestone: | ER1 | Keywords: | TestBlocker | ||||||
| Target Release: | 6.0.1 | Flags: | jsvitak:
needinfo-
|
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||||
| Doc Text: |
Cause:
Deploying project into BPMS/BRMS on IBM java virtual machine cause an exception.
Consequence:
REST response is returned in requested format but the status of request does not correspond with an exception in server.log.
Workaround (if any):
no workaround
Result:
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 19:58:09 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: |
|
||||||||
|
Description
Sona Mala
2013-09-24 11:52:58 UTC
I couldn't reproduce the described error message. Not with XML nor with JSON. It is a long time since this was reported. Sona, it is necessary to run this on IBM JRE? Created attachment 849475 [details]
server.log
I've tested again with IBM JRE 6 ibm-java-x86_64-60-SR12 using the steps above and I got
org.kie.scanner.embedder.MavenEmbedderException: java.util.NoSuchElementException
in both cases - BRMS6 and BPMS6 ER7. Attaching BRMS server log to see the full stack trace.
I've tested the same steps in both BRMS and BPMS ER7 with OpenJDK 1.7.0_25 without problems, so it's IBM JRE specific problem, which still persists.
Regarding to previous comment - the project is however deployed. Project .jar is deployed in BRMS 'Artifact Repository' screen.
Also the client response is ok:
{"jobId":"1389630485338-1","status":"ACCEPTED","repositoryName":"myRepo","projectName":"console"}
So the problem is now only in misleading error message on IBM JRE.
I fixed the error caused by the IBM JVM, but I believe that is only one way to trigger this problem and not it's root cause. I am reassigning this to Toni so he could investigate why, more in general, errors are reported in the wrong format. After some investigations I think this is what should happen. The original bug that caused the error to show up had been fixed so I broke the codes in few different ways to get some errors. There are two ways that could fire exceptions: #1 The codes that are about to be built and deployed are broken. These kind of exceptions are picked up and do not affect the rest call. The rest call simply fires the build and it either passes or not. The result is not reported, just that the build & deploy was started. #2 The workbench codes are broken. This caused the java.util.NoSuchElementException in this BZ. These are all bugs that we should fix. I don't see any need for any more code changes. This no longer has a target release of 6.0.0. Verified in BPMS 6.0.1.ER2. |