-d64 does not work on JDK1.5.0.10

[aycf]

After upgrading to JAVA1.5.0.4 to 1.5.0.10 on HPUX11.11 PA-RISC 2.0, application is unable to start with -d64 option. It just hangs. If I remove the -d64, it can start. Why? We need -d64 for optimization.


JAVA_OPTS="-d64 -XX:+ForceMmapReserved -Xms1g -Xmx1g -Xmn256m -XX:+UseParallelGC -XX:Paralle
lGCThreads=8 -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+DisableExplicitGC -Djava.rmi.server.hostname=$HOST -Djava.rmi.server.useLocalHostname=false -Dpowercomp.server.id=$INSTANCE"

[Steven E. Protter]

Shalom,

Problem introduced by Java. There are at least two new subversion released. 1.5.0.0.12

http://www.hp.com/go/java

SEP

[aycf]

Thanks, SEP. I installed the latest JDK1.5.0.14 and I am still unable to start the application. Once I removed the "-d64", it started. Any other ideas?
The patches are all up-to-date.

[Jov]

Hi,

Check the actual version you're running and ensure path and symlink are all updated after the installation.


Jov

[aycf]

Thanks, Jov. I updated the path and it still does not start. It doesn't even create any logs. The java process does not even initiate.

[Dennis Handly]

>It doesn't even create any logs. The java process does not even initiate.

You might want to use "tusc -fp -o tusc.out ..." to trace what's going on.

>We need -d64 for optimization.

What did you mean by that? You need -d64 because you need the large size. I suppose you could use the large size and changed algorithms to be faster.

[aycf]

I get the following VM initialization error.
Once, I omit the "-d64" in the $JAVA_OPTS parameter, jboss now starts so I am convinced that Java works! I am out of ideas now. :(

/opt/jboss/jboss-4.0.3SP1/bin > =========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /opt/jboss/jboss-4.0.3SP1

JAVA: /opt/java1.5/bin/java

JAVA_OPTS: -d64 -XX:+ForceMmapReserved -Xms1g -Xmx1g -Xmn256m -XX:+UseParallelGC -XX:ParallelGCThreads=4 -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+DisableExplicitGC -Xverbosegc:file=/opt/jboss/jboss-4.0.3SP1/server/dendev/log/20080808122407.8380.gc -Djava.rmi.server.hostname=hpux04.insureworx.com -Djava.rmi.server.useLocalHostname=false -Dpowercomp.server.id=8380 -Dprogram.name=run.sh

CLASSPATH: /opt/jboss/jboss-4.0.3SP1/bin/run.jar:/opt/java1.5/lib/tools.jar

=========================================================================

Error occurred during initialization of VM
java.lang.NoSuchMethodError: java.lang.Thread.start()V
./run.sh[174]: 4492 Abort

[aycf]

By the way, the above init error was done on JDK1.5.0.14 and the -d64 still fail.

Much appreciations to those who response.

[Dennis Handly]

>I get the following VM initialization error.
>Error occurred during initialization of VM
java.lang.NoSuchMethodError: java.lang.Thread.start()V

Have you talked to the Response Center about this problem?

Did you try using tusc to trace for system call failures?

[aycf]

Dennis,

No, I have not talked to the Response Center as I don't have a support contract with them.

I tried tusc but it is not installed on the system.

What I found out is that the JDK that HP provides on the download site is not 64 bit to begin with...just 32. I've posted a question to their download team. Hopfully, I will get a fix soon.

When I do a "./java -d64 -version", it core dumps.