Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 894040

Summary: Designer Error with BRMS 5.3.1 deployable in EAP6
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Martin Weiler <mweiler>
Component: DeploymentAssignee: Julian Coleman <jcoleman>
Status: CLOSED UPSTREAM QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: BRMS 5.3.1CC: alazarot, bmaxwell, tkobayas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:27:14 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 Flags
Log file with compressed designer.war
none
Log file with exploded designer.war none

Description Martin Weiler 2013-01-10 15:08:47 UTC 
Description of problem:
Deploying BRMS 5.3.1 GA in EAP 6 results in an "XML parser error" when I try to open the Designer in Guvnor. This happens if auto-deploy-exploded flag is set to true.

Version-Release number of selected component (if applicable):
BRMS 5.3.1 deployable
EAP 6.0.0

How reproducible:
always

Steps to Reproduce:
1. Follow instructions from https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Getting_Started_Guide/Installing_the_Deployable_Package1.html
2. Change standalone.xml: <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-exploded="true"/> to avoid having to add .dodeploy markers manually on each startup
3. Start the server, open Guvnor, and create a new BPMN2 process
  
Actual results:
Browser shows error: XML Parsing Error: no element found
Location: http://localhost:8080/designer/editor/?uuid=7d795e9a-f8df-424a-a274-cc8adad762e6&profile=jbpm
Line Number 1, Column 1:

server.log file shows that designer.war gets reloaded, and the following message:
WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'


Expected results:
Process designer works as expected.

Additional info:
Workarounds:
- keep designer.war exploded, but add .dodeploy methods on each server start
- compress designer.war
Comment 1 Martin Weiler 2013-01-10 15:10:11 UTC 
Created attachment 676389 [details]
Log file with compressed designer.war
Comment 2 Martin Weiler 2013-01-10 15:10:39 UTC 
Created attachment 676390 [details]
Log file with exploded designer.war
Comment 7 lcarlon 2013-01-24 22:34:32 UTC 
Hi Alessandro,

Yes, we'll update the docs. We've been working on this in response to other feedback we've received, and our solution has been to instruct users to recreate the .dodeploy (not simply rename the existing files) each time they restart the server.

I've created bug 903848 to track the docs component.

Lee
Comment 10 lcarlon 2013-02-14 04:36:33 UTC 
Hi Alessandro,

A new installation procedure for deploying to EAP6[1] was added for bug 888669. As stated above, users are instructed to recreate the .dodeploy files each time they restart the server.

Thanks
Lee

[1]https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html-single/BRMS_Getting_Started_Guide/index.html#Installing_on_JBoss_Enterprise_Application_Platform_61
Comment 11 Toshiya Kobayashi 2013-02-18 05:47:01 UTC 
Miguel (mreyesab) reported:
=======
I just verified BRMS 5.3.1 with EAP 6.0.1 and this problem has been fixed and it deployment is working as it should. It is no longer necessary to use the flag auto-deploy-exploded="true" nor the .dodeploy files need to be recreated with every server restart.

Just like bmaxwell said on 1/24/2013:
"In EAP 6.0.1 a bug is fixed, if you have auto-deploy-exploded=false (default) then an exploded app is deployed by creating a <deployment-name>.dodeploy this triggers JBoss to deploy. Upon restart the .deployed will not be deleted and JBoss will deploy the war since it was deployed successfully before the restart."
=======
Comment 12 Lukáš Petrovický 2013-02-19 07:50:29 UTC 
(In reply to comment #11)

> I just verified BRMS 5.3.1 with EAP 6.0.1 and this problem has been fixed
> and it deployment is working as it should.

Can this be closed then?
Comment 13 Toshiya Kobayashi 2013-02-19 08:04:40 UTC 
(In reply to comment #12)
> (In reply to comment #11)
> 
> > I just verified BRMS 5.3.1 with EAP 6.0.1 and this problem has been fixed
> > and it deployment is working as it should.
> 
> Can this be closed then?

I believe, yes. It is an issue only with EAP 6.0.0 and we have published a knowledge base article for it.

https://access.redhat.com/knowledge/solutions/290913
Comment 14 Lukáš Petrovický 2013-02-19 08:06:30 UTC 
Closing.
Comment 18 Red Hat Bugzilla 2025-02-10 03:27:14 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.