Skip to Main Content
Forums

Java HotSpot Virtual Machine

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.

totalMemory Decreases Over Time

843829Jan 28 2009 — edited Feb 10 2009
We have a Java application running on the Sun 1.5.0_09 JVM on a Solaris 8 server. When we started the application, we set the heap size settings as follows: -Xms256m -Xmx256m. With these settings we have typically found that a call to Runtime.getRuntime().totalMemory() will return a constant value over time, because we essentially set the maximum and minimum heap size values to the same size. However, we have a couple of systems where the value returned by Runtime.getRuntime().totalMemory() is decreasing over time. Can anyone explain how the total heap size can decrease when it has been set to a constant value? Note that we didn't have this problem on 1.4.2. We have only seen it on 1.5.0.

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 Mar 10 2009
Added on Jan 28 2009
#java-virtual-machine-jvm
2 comments
161 views