Red Hat Bugzilla – Bug 810503
Deployment of designer.war to SOA 5.2 failed
Last modified: 2012-05-29 02:31:52 EDT
Description of problem:
When server SOA 5.2 starts, an exception occurs (is attached).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Server's profile contents designer.war in "deploy" folder
2. Start server, open browser, open jboss-brms
3. Open any BPMN process
there should be a canvas and tools for creating a BPMN process (screenshot is attached)
there is HTTP status 404 (screenshot is attached)
Created attachment 575748 [details]
Logger of server
Created attachment 575749 [details]
the exception from server.log
Created attachment 575750 [details]
Created attachment 575751 [details]
It seems that Bugzilla changed components of this issue to components of bug 810503 when I linked this issue from there. I'm fixing the component value to Configuration.
What is the version of designer.war? where is the designer.war get from ?
I test against designer.war and jboss-brms.war from ER5 and ER6 on soa-p 5.2. Both are fine. I didn't see the error reported。
Does this still happen in ER6 ?
(In reply to comment #9)
> Does this still happen in ER6 ?
I tested it again, maybe there is some mistake. There are steps to reproduction:
1. Download from http://jawa05.englab.brq.redhat.com/candidate/BRMS-5.3.0-ER6/
2. Download from http://porkchop.devel.redhat.com/released/JBossSOAP/5.2.0/
3. Copy from "deployable" zip-file: jboss-jbpm-console.zip/designer.war and jboss-brms-manager.zip/jboss-brms.war to SOA-5.2/jboss-as/server/default/deploy/*.war
4. Run server
- occur exceptions
- designer is unreachable in Guvnor
I use DEFAULT profile.
after removing libraries:
from designer.war/WEB-INF/lib this problem disappears.
The server starts without exceptions and it seems that the designer works without problems.
Yes, Sona, it's true, this issue occures to 5.2.0.GA.
Sorry for confusion, I tested it with a small version later than 5.2.0.GA which I didn't noticed.
This issue is not happen to SOA 5.3.0 ER versions too.
Had a futher look that, it should be enough to remove
The designer.war also deployed fine with BRMS-standalone, EWS if we removed the two jars.
Asking Tihomir that if it is possible to remove the xercesImpl-2.9.1.jar as deps or exclude it in wars.
If this does not break deployment in AS 5 since the community war targets that then sure I can remove in the code, if it does I would ask for product build to remove it during its work. Will test today and add more comments here.
(In reply to comment #15)
> Had a futher look that, it should be enough to remove
Sorry, this is wrong. Sona's comments 13 is correct.
xmlParserAPIs-2.0.2.jar is also need to remove.
It would cause the runtime CCE problem.
Tihomir, is this fixed in upstream or this still required patch on productization level.?
I saw this status has been in Modified status.
> The designer.war also deployed fine with BRMS-standalone, EWS if we removed
> the two jars.
> Asking Tihomir that if it is possible to remove the xercesImpl-2.9.1.jar as
> deps or exclude it in wars.
I think they should be removed by the product build.
(In reply to comment #19)
> I think they should be removed by the product build.
Ok, I would do .
Let me update the status to ASSIGNED .
Excluded the following file in the jboss-jbpm-console.zip:
Change committed in /trunk/brms-p/src/main/assembly/jbpm-console.zip.xml revision: 11098
Please verify them on ER8.