Bug 1008725

Summary:	Installation does not work for macs using JDK 1.6
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Catherine Robson <crobson>
Component:	Build and Assembly	Assignee:	Ryan Zhang <rzhang>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marek Baluch <mbaluch>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	jowest, jtyrrell, kverlaen, msalatin, rrajasek
Target Milestone:	ER4	Flags:	kverlaen: needinfo+
Target Release:	6.0.0
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:13:17 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:
Bug Depends On:
Bug Blocks:	1006308

Description Catherine Robson 2013-09-16 23:24:48 UTC

Description of problem:
When installing on a mac with JDK 1.6, the installation does not work properly.  Users are unable to start the web consoles.

Appears that it can't create the H2 database on OSX, which caused JBPM to fail on login
 
In theory it might be a JDK 1.6 issue, the 3 Macs with the issue seemed to be running JDK 1.6.  java -version
java version "1.6.0_51"
Java(TM) SE Runtime Environment (build 1.6.0_51-b11-456-10M4508)
Java HotSpot(TM) 64-Bit Server VM (build 20.51-b01-456, mixed mode)
  Eric S., Mac with 1.7 seemed to work.

Version-Release number of selected component (if applicable):
6.0.0.ER2

Comment 2 Kris Verlaenen 2013-09-17 00:07:19 UTC

Is there any more information available, like a server log containing the error, or an exception stack trace somewhere?

Comment 3 Catherine Robson 2013-09-17 00:18:36 UTC

I have added Josh West and Jim Tyrrell who ran into this bug so they can add more information.

Comment 4 Mauricio Salatino 2013-09-20 14:32:19 UTC

I've tested in mac with JDK 1.7 and it was working ok.. so probably it's JDK 1.6 the problem

Comment 5 Maciej Swiderski 2013-09-23 11:03:43 UTC

based on the investigation it is not directly related to the Java version although it's much more visible when running on Java 1.6. This issue is mainly related to the order which applications are deployed in. Since dash builder.war depends on business-central.war it cannot be deployed earlier that business-central but this is actually happening when running on Java 1.6. Most likely it's due to different ordering returned from deployment-scanner and thus first dashbuilder fires and tries to be deployed.

JBoss AS7.2/EAP6.1 has a direct support ot enforce ordering of deployments - deployment dependencies. So to enable this support following needs to take place:
1. create file jboss-all.xml inside dashbuilder.war/META-INF
2. place following content int jboss-all.xml:
<jboss umlns="urn:jboss:1.0">
<jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">
<dependency name="business-central.war" />
</jboss-deployment-dependencies>
</jboss>

with this dashbuilder.war will wait until business-central is completely deployed which of course will make the deployment of these wars be performed sequentially. Another aspect that is important to mention here is that after jboss-all.xml is placed in dashbuilder.war it won't be able to deploy separately as the deployment dependency is mandatory.
Note that this issue will only happen when data base has not been created previously - like with in memory data base and hibernate ddl auto is enabled.

Reassigning to Ryan for inclusion in product if he finds this as appropriate solution.

https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html/Administration_and_Configuration_Guide/Control_the_order_of_Deployed_Applications_on_JBoss_Enterprise_Application_Platform.html

Comment 7 Ryan Zhang 2013-10-08 07:27:40 UTC

Yep, the deployment order has already been forced as requested since ER3.
It worths to re-verify this issue.
(In reply to Maciej Swiderski from comment #5)
> based on the investigation it is not directly related to the Java version
> although it's much more visible when running on Java 1.6. This issue is
> mainly related to the order which applications are deployed in. Since dash
> builder.war depends on business-central.war it cannot be deployed earlier
> that business-central but this is actually happening when running on Java
> 1.6. Most likely it's due to different ordering returned from
> deployment-scanner and thus first dashbuilder fires and tries to be deployed.
> 
> JBoss AS7.2/EAP6.1 has a direct support ot enforce ordering of deployments -
> deployment dependencies. So to enable this support following needs to take
> place:
> 1. create file jboss-all.xml inside dashbuilder.war/META-INF
> 2. place following content int jboss-all.xml:
> <jboss umlns="urn:jboss:1.0">
>     <jboss-deployment-dependencies
> xmlns="urn:jboss:deployment-dependencies:1.0">
>         <dependency name="business-central.war" />
>     </jboss-deployment-dependencies>
> </jboss>
> 
> with this dashbuilder.war will wait until business-central is completely
> deployed which of course will make the deployment of these wars be performed
> sequentially. Another aspect that is important to mention here is that after
> jboss-all.xml is placed in dashbuilder.war it won't be able to deploy
> separately as the deployment dependency is mandatory.
> Note that this issue will only happen when data base has not been created
> previously  - like with in memory data base and hibernate ddl auto is
> enabled.
> 
> Reassigning to Ryan for inclusion in product if he finds this as appropriate
> solution.
> 
> 
> https://access.redhat.com/site/documentation/en-US/
> JBoss_Enterprise_Application_Platform/6.1/html/
> Administration_and_Configuration_Guide/
> Control_the_order_of_Deployed_Applications_on_JBoss_Enterprise_Application_Pl
> atform.html

Comment 9 Marek Baluch 2013-10-31 10:31:50 UTC

Verified on ER4.

Mini-mac mac-mini.lab.eng.brq.redhat.com with JDK 1.6.