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.

maximum heap size suddenly decreased

843829Aug 23 2006 — edited Aug 23 2006
I have a Windows 2003 64-bit server w/ 20GB that I'm running the 32-bit VM on. For the past several months I have been able to run VMs with the maximum heap set to 1500M. Recently I am no longer able to allocate 1500M. The maximum I can get now is about 1024M. The system has over half of the physical memory available when I'm am trying this allocation.

What could cause this change in behavior? The system experienced several OS patches and upgrades recently. Is it possible that these are causing Java to be unable to allocate a 1.5GB continugous memory space? After a bit of googling and discussions with others I am told that a new DLL could potentially be splitting up my virtual address space and preventing me from ever getting a continguous allocation of more than a gig. Is there anyway to confirm this and figure out what the culprit is? I was directed to vadump or ProcessExplorer but I haven't been able to parse the output well enough to determine what's going on.

Thanks in advance.

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 Sep 20 2006
Added on Aug 23 2006
#java-virtual-machine-jvm
1 comment
116 views