Unstable 64bit Standalone OC4J With 4GB
(Doc ID 762904.1)
Last updated on OCTOBER 09, 2023
Applies to:
Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.4.0 [Release AS10gR3]Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Sun Solaris SPARC (64-bit)Sun Solaris x86-64 (64-bit)
Symptoms
Application was deployed on Standalone OC4J with -Xmx3072m.
Experience shows that the application would need more heap memory,
but being restricted because of the necessity of compilation in 32bit mode.
After a short time, java memory problems showed up.
The JVM was then configured with -D64 -Xmx4096m.
But the application became unstable after that, so got back to 32bit and 3072m heapsize.
The OC4J is running stable now, but the application does not work (internal server error).
In the logfiles, seeing OutOfMemoryError messages.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |