-d64 does not work on JDK1.5.0.10

[aycf]

Here are the kernel parameters that differ between the 2 machines.

-d64 does NOT work on HPUX04.
-d64 works on HPUX05.

I updated max_thread_proc in HPUX04 and rebooted. Still having the same error.

Any thing else I should change?
--------------------
HpUX04 HPUX05
Ksi_alloc_max 32768 32928
Max_thread_proc 256 3000
Maxfiles 256 2048
Maxswapchunks 16384 2048
Maxuprc 4000 500
msgmap 4098 2050
msgmni 4096 1024
msgtql 4096 2048
ncsize 72704 10820
nfile 63488 16272
ninode 34816 5700
nkthread 7184 7219
Nproc 4096 4116
nsysmap 8192 8232
nsysmap64 8192 8232
semmap 4098 2050
semmni 4096 2048
semmns 8192 4096
semmnu 4092 1024
shmmax 0xaccccccc 966367642

[Dennis Handly]

>I updated max_thread_proc in HPUX04 and rebooted. Still having the same error.

That would be my first guess but I don't remember any errors in thread creation.

There is also: maxfiles 256 2048
These seem too close to worry about:
nkthread 7184 7219
nproc 4096 4116
nsysmap 8192 8232
nsysmap64 8192 8232

You could use tusc on the good system to see where things diverge.
And use -fpl for both instead of just -fp.

[aycf]

I am attaching the "goodtusc" and "badtusc" for review.

Thanks ALOT, Dennis!!

[aycf]

here's the badtusc.out with the error

[aycf]

Does anyone know what "lwp_self" is? I do not see that kernel parameter at all.

goodtusc.out
_lwp_self() ...................... = 8925981
badtusc.out
_lwp_self()...................... = 17313

[Don Morris_1]

That's not a parameter, that's a function.

http://docs.hp.com/en/5992-3373/ch10s09.html

[aycf]

updated to these but still didn't fix the -d64 issue. I am giving up now. :-(

max_thread_proc 3000
maxfiles 2048
maxfiles_lim 2048
Maxdsiz 2097152000
Nkthread 7219
Nproc 4116
Nsysmap 8232
Nsysmap64 8232
Shmmax 966367642

[Dennis Handly · Accepted solution]

>I am attaching the "goodtusc"

Was this 1.5.0.10? The path to java was different: /pwrcomptmp/...

>here's the badtusc.out with the error

The java engineer and I looked at it. It seems the working one does a mmap(2), the bad one uses read(2).

He also noticed that there are some bad symlinks in /usr/lib/pa20_64/ that point to /opt/java1.4/. This will fail if you are using 1.5.0.10! You need to remove these symlinks.

========================================================
readlink("/usr/lib/pa20_64/libverify.sl", "/opt/java1.4/jre/lib/PA_RISC2.0W/libverify.sl",
readlink("/usr/lib/pa20_64/libjava.sl", "/opt/java1.4/jre/lib/PA_RISC2.0W/libjava.sl"
readlink("/usr/lib/pa20_64/libzip.sl", "/opt/java1.4/jre/lib/PA_RISC2.0W/libzip.sl"

[aycf]

Thank you very much,Dennis. That did it! For some reasons, those system libraries link to an old version of java.

Now, what I don't understand is how come -d64 works for the existing jdk1.5.0.4. It all just stopped working after I installed 1.5.0.10 and 1.5.0.14.

[Dennis Handly]

>Thank you very much, Dennis. That did it!

You're welcome. Since you're new to the forums, please read the following about assigning points:
http://forums.itrc.hp.com/service/forums/helptips.do?#33

Note: Every reply is eligible for points, where the amount depends on how helpful they were in answering your many questions.

>what I don't understand is how come -d64 works for the existing jdk1.5.0.4. It all just stopped working after I installed 1.5.0.10 and 1.5.0.14.

I assume they have added functionality to 1.5.0.10 and then the 1.4 libverify.sl no longer liked it.