Bug 1023463

Summary: Server could not start when running with 32bit java on 64bit system
Product: [JBoss] JBoss Operations Network Reporter: Libor Zoubek <lzoubek>
Component: InstallerAssignee: Jay Shaughnessy <jshaughn>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: hrupp, myarboro, theute
Target Milestone: ER05   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-28 13:26:16 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:
Bug Depends On:    
Bug Blocks: 1012435    

Description Libor Zoubek 2013-10-25 13:26:54 UTC
Description of problem:

Server could not start when running with 32bit java on 64bit system

Version-Release number of selected component (if applicable):
JON 3.2.ER4

How reproducible: always


Steps to Reproduce:
1. install ONLY 32b java on your system
2. install JON using rhqctl install
3. start JON server

Actual results:

JON server cannot start 

ERROR [org.jboss.as.ejb3.invocation] (pool-9-thread-1) JBAS014134: EJB Invocation failed on component StartupBean for method public abstract void org.rhq.enterprise.server.core.StartupLocal.init(): javax.ejb.EJBException: java.lang.RuntimeException: Startup failed: java.io.tmpdir 'C:\Windows\system32\config\systemprofile\AppData\Local\Temp' does not exist
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInNoTx(CMTTxInterceptor.java:191) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
        at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:237) [jboss-as-ejb3-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

but C:\Windows\system32\config\systemprofile\AppData\Local\Temp exists. If you switch to 64b java, you'll not hit this issue.

Expected results:
JON server starts up

Additional info:

Comment 1 Jay Shaughnessy 2013-10-28 13:26:16 UTC
This is the same issue as bug 1022620, marking as duplicate.

*** This bug has been marked as a duplicate of bug 1022620 ***