I managed to fix this by forcing the jdk 1.6 directory into the path
# export PATH=/usr/java/jdk1.6.0/bin:$PATH
before I executed the jar, which leads me to think that there is something inside the jar that is spawning its own java child process and that is using the path, not the java that it was originally run from.
If this is the case, the instructions may need amending for those systems that have multiple JDKs installed.
Chris
[Message sent by forum member 'krustyfur' (krustyfur)]
http://forums.java.net/jive/thread.jspa?messageID=233340