Skip to Main Content
Forums

Java Programming

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 limitations on Windows 32-bit

807607Oct 13 2006 — edited Oct 16 2006
Developing a memory - intensive application, I'm currently limited by the heap size of my jvm. Using -Xmx or -XX:AggressiveHeap options did not help : I'm still unable to allocate more than 1GB (50% of my RAM) to my jvm. When setting -Xmx to more than 1GB, the java command fails with "Could not create the Java virtual machine" error

I'm using JSE5.0 on a 2 CPU - 2GB -32 bit Windows XP 2002 professional.

Is that a limitation of Windows 32-bit ? I've read that Windows kidnaps 50% of RAM for kernel/system purpose...

I'm also using the "-server" option for performance reason : may that be influent on available heap size ?

Can any one help me ?

Thanks

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 Nov 13 2006
Added on Oct 13 2006
5 comments
438 views