-> solution was found in the kernelparameters for the proc-Subsystem (see below) and with JAVA140 beta Version, 512 MB memory.
No Problems with
proc: (its not reviewed from HPQ, but it runs)
max_proc_per_user = 2048
per_proc_stack_size = 134217728
max_per_proc_stack_size = 134217728
per_proc_data_size = 3000000000
max_per_proc_data_size = 3000000000
max_per_proc_address_space = 6708000
per_proc_address_space = 4294967296
Before the solution (old Params):
10737418240 max_per_proc_data_size=
10737418240 max_per_proc_address_space =
per_proc_address_space = 4294967296
5368709120 per_proc_stack_size=
33554432 max_per_proc_stack_size=
5368709120 per_proc_data_size=
thanks to
Francois Vanderpoorte -> tuning examples
Jan Mark Holzer
McGuinness Todd
Cable, Randall
daesang hwang
My original question was:
Dear Managers
Please any ideas about the following JVM error on tru64
5.1. , java 131 beta1 :
If i try this:
>java -classic BapiInfo
-> no Problems
If i try this:
>java BapiInfo
could not allocate code space: No such file or directory, file /sys/alpha/md.c (***),
line 128
(***) I've found this in folowing directorie: /usr/sys/arch/alpha/md.c
The Difference between the to java-call statements is that second use the default fast-virtual machine.
Have i a memory problem ? (DS10, Oracle IAS 817, Rel 3 ,256 MB-Memory)
Any ideas how can i solve this ?
Is there another mailgroup(s) for such problems ? -> let us know
Thanks for all feedbacks.
Olaf Kasper
Systemengineer
co Kantonsspital Basel Universitätskliniken
tel gesch. +41 61 265 3866
e-mail okasper_at_uhbs.ch
Received on Fri Jun 14 2002 - 12:03:26 NZST