most recent updatemanager patches 121118-13/121119-13 use the command fragment 'java -version:1.5+' to launch the application, and some users on x86 are now experiencing a problem where the application fails to launch, see
http://forum.java.sun.com/thread.jspa?threadID=5209110&start=0&tstart=0
updatemanager is not implicated in the underlying cause of the problem, but is serving to expose the issue -- the problem itself can easily be reproduced on x86 with the following piece of shell script
----
x=0 ; HOME=/ ; while [ $x -lt 40 ] ; do echo HOME=$HOME; export HOME; java -version:1.5+ > /dev/null; HOME=${HOME}x; (( x+=1 )); done
----
where HOME env var values of particular _length_ result in errors like
Unable to resolve /usr/jdk/jdk1.5.0_12
Unable to resolve /usr/jdk/jdk1.5.0_12
http://forum.java.sun.com/thread.jspa?threadID=5209110&start=0&tstart=0
updatemanager is not implicated in the underlying cause of the problem, but is serving to expose the issue -- the problem itself can easily be reproduced on x86 with the following piece of shell script
----
x=0 ; HOME=/ ; while [ $x -lt 40 ] ; do echo HOME=$HOME; export HOME; java -version:1.5+ > /dev/null; HOME=${HOME}x; (( x+=1 )); done
----
where HOME env var values of particular _length_ result in errors like
Unable to resolve /usr/jdk/jdk1.5.0_12
Unable to resolve /usr/jdk/jdk1.5.0_12
- duplicates
-
JDK-6597847 mJRE version matching sometimes fails
- Closed
-
JDK-6431847 Memory overflow in java launcher for Linux
- Resolved
- relates to
-
JDK-2152460 Memory overflow in java launcher for Linux
- Resolved
-
JDK-2152459 Memory overflow in java launcher for Linux
- Resolved