Skip to Main Content

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Java Process takes around 3GB memory in AIX Environment

843830Jan 20 2006 — edited Jan 23 2006
Hi,

I am facing issue with Java process in AIX Machine. The issue is Java Process takes around 3GB memory, which is not acceptable in our environment.

We are running a Weblogic server in AIX environment with IBM JDK. JVM heap size is set to 512M for both maximum and minimum values. But still the process(java) is taking 3GB.

But the same application only takes 0.7GB for process in some other box with Websphere(AIX) and IBM JDK.

Is there any reason to occupy such a huge memory by Java process in AIX? Is there any way to control it?


Environmental Details:
========================

OS : AIX 5.2(Box is having 18CPUs and 14GB RAM)
Appserver : Weblogic 8.1 (SP4)
JDK : IBM JDK(1.4.2 ClassicVM)
JVM Command Parameters : -Xms1024m -Xmx1024m -verbose:gc -Xgcpolicy:optavgpause

Below command has been to get the process size of Java process (I never seen process size as 3GB. It was told by server admin).

ps -eo user,pid,pcpu,vsz,time,args

Here, vsz - gives memory size. Any idea why this is happening?

thanks,
Shanmuga perumal

Comments

handat

Restart OAAM instance. Best would be to shut down all OAAM instances, then update the password using EM before starting the OAAM instances again.

Khanh

I updated the QA_OAAM schema password in this path: weblogic domain/oam_domain/Security/credentials/oaam Map/oaam_db_key and restarted everything.  However, the QA_OAAM db account is still locked.

Where else do I need to update the password?

Thanks

Khanh

Khanh

I also unlocked the database account after restarting the oaam managed servers.

Khanh

Khanh

My issue has been resolved.

We updated the pwd in the database (to make sure we have the right pwd).

We updated the pwd in weblogic admin console/Service/Data Sources (for all 3 OAAM related data sources).

Shutdown all OAAM admin and managed servers

Logged into the database to unlock the oaam database account

Restarted the oaam admin server (monitor the oaam db account connection using sql developer) in weblogic

Restarted the oaam managed server in weblogic (monitor the oaam db account connection using sql developer).

Once all managed servers are up and running and the oaam db account is not locked, then the issue has been resolved.

Khanh

1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Feb 20 2006
Added on Jan 20 2006
1 comment
135 views