topic Re: Java process on Tru64 in Operating System - Tru64 Unix

Java process on Tru64

Rajesh Karelia — Fri, 18 Apr 2008 11:23:11 GMT

Hi,

The specification of my system is:
HP Tru64Unix v5.1b with true cluster
Database Oracle 9.2.0.5
Java version 1.4.2-3
TeMIP Framework v5.0 Level 1 Rev G

One of the presentation modules of TeMIP framework stops working when Java virtual memory reaches certain level. We need to stop the process and restart it in order to get it back into action.

Before restart of the process:

dybpsp02.nat.bt.com> ps auxw |grep java

temip 1140490 0.0 8.3 500M 341M ?? S Apr 11 01:08:35 /usr/bin/java -mx600M -

After restart of the process:

dybpsp02.nat.bt.com> ps auxw |grep java

temip 1430736 0.0 2.0 287M 83M ?? S 10:39:17 0:20.83 /usr/bin/java -mx600M -

It can be noted that before restart, the memory being used was 500M and after restart it came down to 287M.

What would be the reason for the process to hang? Is it a memory problem with Java?

How can I avoid such a condition to occur again and again.

Many thanks

Rajesh

Re: Java process on Tru64

Hein van den Heuvel — Fri, 18 Apr 2008 18:27:14 GMT

Maybe the java memory settings ( -Xmx, -Xms ) are not in line with the memory available through 'ulimit' and sysconfig max_per_proc_address_space
and per_proc_address_space,

Check
#sysconfig -q proc

Check
#ulimit -a

hth,
Hein.

Re: Java process on Tru64

Hein van den Heuvel — Fri, 18 Apr 2008 18:36:26 GMT

Specifically, check the per_proc_data_size.
It would not surprise me if it is set to 500MB.
The default is 'only' 128MB.

The command seemd to specificy to allow Java use 600MB... but that might not be there.
'More is better?'

Also, Did you see:

http://h18012.www1.hp.com/java/faq/unix.html

Google for +tru64 +java +xmx shows good stuff.

Hein.

Re: Java process on Tru64

Rajesh Karelia — Mon, 21 Apr 2008 08:05:16 GMT

Hi,

The output of the commands is:

-----------------------------------------------------------------
dybpsp02.nat.bt.com> sysconfig -q proc
proc:
max_proc_per_user = 4096
max_threads_per_user = 16384
per_proc_stack_size = 33554432
max_per_proc_stack_size = 33554432
per_proc_data_size = 1073741824
max_per_proc_data_size = 1073741824
max_per_proc_address_space = 4294967296
per_proc_address_space = 4294967296
executable_stack = 0
autonice = 0
autonice_time = 600
autonice_penalty = 4
open_max_soft = 4096
open_max_hard = 4096
ncallout_alloc_size = 8192
round_robin_switch_rate = 0
sched_min_idle = 0
give_boost = 1
maxusers = 4096
num_wait_queues = 4096
num_timeout_hash_queues = 4096
enhanced_core_name = 1
enhanced_core_max_versions = 16
exec_disable_arg_limit = 0
dump_cores = 1
dump_setugid_cores = 1
executable_data = 0

-----------------------

dybpsp02.nat.bt.com> ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 32768
memory(kbytes) 4059208
coredump(blocks) unlimited
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
-------------------------------

Kindly suggest what requires tuning.

Many thanks

Rajesh

Re: Java process on Tru64

Hein van den Heuvel — Tue, 22 Apr 2008 12:58:11 GMT

That looks good.
No 500mb limitation in sight.

You'll have to work with the folks that support TeMIP.
Does it leave an error message in a log?

Good luck,
Hein.

Re: Java process on Tru64

Rajesh Karelia — Tue, 22 Apr 2008 13:13:18 GMT

Well, I have recently heard of some problems of Java version 1.4.2-3 on Tru64 Unix v5.1b.

It says - 'A potential vulnerability has been identified that affects the
Software Development Kit (SDK) and Run Time Environment (RTE)
for the Tru64 UNIX Operating System for the Java(TM) Platform.
Object deserialization may allow a remote attacker to cause the
Java Virtual Machine to become unresponsive, resulting in
Denial of Service (DoS) for the runtime environment and servers
that run on the runtime environment.'

The solution is upgrade SDK and RTE to version 1.4.2-4.

I wanted to know whether this java version upgrade impacts the Oracle version on the platform. Rightnow its 9.2.0.5. Do I need to upgrade it to Oracle 10g Rel 2?

Thanks.