https://issues.apache.org/bugzilla/show_bug.cgi?id=56134
Bug ID: 56134
Summary: java task with fork=true uses different JVM than the
one set in JAVACMD environment variable
Product: Ant
Version: 1.9.3
Hardware: PC
OS: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
Assignee: [email protected]
Reporter: [email protected]
Created attachment 31308
--> https://issues.apache.org/bugzilla/attachment.cgi?id=31308&action=edit
Proof of concept project for demonstration of the issue
Scenario
========
* Solaris 64bit OS with both a 32bit JVM and a 64bit JVM installed (Oracle)
* Setting the JAVACMD environment variable as per the documentation[0] to
specify the 64bit binary to be used
* Running a build which calls the java task with attribute fork="true"
Expected
========
Ant continues to use the java executable as specified in the environment
variable.
Actual
======
Ant spawns a JVM taken from the OS/environment defaults, thus mixing the build
process with 64bit and 32bit processes. This may result in build errors, esp.
when using native libraries which require a certain architecture.
How to reproduce
================
Please find attached a simple proof-of-concept. The Java main class simply
prints the architecture. In our case we can reproduce the behaviour like this:
--------------------------------------
-bash-3.2$ export JAVACMD=/opt/database/www/apps/java/bin/amd64/java
-bash-3.2$ $JAVACMD -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
-bash-3.2$ grep classname build.xml
<java fork="true" classname="Main">
-bash-3.2$ ant
Buildfile: /tmp/sup11111/build.xml
compile:
run:
[java] JVM Arch: 32bit
BUILD SUCCESSFUL
Total time: 1 second
-bash-3.2$
--------------------------------------
When removing the fork="true" park from build.xml, the correct JVM is takes, as
specified in the environment variable:
--------------------------------------
-bash-3.2$ grep classname build.xml
<java classname="Main">
-bash-3.2$ ant
Buildfile: /tmp/sup11111/build.xml
compile:
run:
[java] JVM Arch: 64bit
BUILD SUCCESSFUL
Total time: 0 seconds
--------------------------------------
I know that the java task allows the JVM to be specified explicitly using the
"jvm" attribute and other settings via the "jvmargs" etc. However, this would
not work when trying to reproducibly run the build on different environments
with different paths.
[0] http://ant.apache.org/manual/running.html#envvars
--
You are receiving this mail because:
You are the assignee for the bug.
