Hi,
I can confirm that I got the same Problem on Linux with IBM JDK 1.5
(build pxi32dev-20070201 (SR4)). Using
PHOENIX_JVM_OPTS="-Xmx600M"
has mitigated the problem for me. Additionally, I restart JAMES every
night, just to be safe.
Michael
-----Ursprüngliche Nachricht-----
Von: SeaGizmo
Gesendet: 2007-04-19 12:19
Hey,
Got the exact same error on Linux.
I used the following jvm settings to the phoenix.sh start up script.
JAVA_HOME=/usr/java/jdk1.5.0_10
export JAVA_HOME
PHOENIX_JVM_OPTS="-Xmx1024m -Xms512m "
export PHOENIX_JVM_OPT
I haven't had a problem since (fingers crossed).
regards
Eoin
Stefano Bagnara wrote:
Bud Bach ha scritto:
Exception in thread "CompilerThread1" java.lang.OutOfMemoryError:
requested
134217744 bytes for Chunk::new. Out of swap space?
I guess this could not be a problem in James but something wrong in
the JVM.
What OS/JVM are you using?
Another user, SeaGizmo, reported the same identical error 1 month ago
(23/03/2007).
He was using jdk1.5.0_10 on linux.
The first suggestion was to upgrade to 1.5.0_11 or to downgrade to
1.4.2_13. Can you try?
Then Salvatore Orlando suggested this to proceed with analysis:
------------------
This crash seems to be related to a JVM bug. It sounds quite strange
that a
method requires more than 100MB heap for Jit Compilation. You can find
several similar failure reports in the hotspot bug database.
In this case it could be useful to monitor the following parameters
through
jvmstat:
1) sun.ci.lastFailedMethod
You should be able to identify which JIT compilation event leads to the
failure of the JVM. (You can also write a little JVMTI agent implementing
the compiledMethodLoad callback function).
2) sun.ci.lastFailedType
Once the faulty method has been identified it can be excluded from jit
compilation creating a .hotspot_compiler file (including the name of the
methods to exclude preceeded by the 'exclude' keyword) and passing
this file
to the JVM through the -XX:CompileCommandFile option.
3) sun.ci.nmethodSize
If several failures are observed, and they occur upon JIT-compilation of
different methods there may exist a problem with the native code
cache. This
parameter allows you to monitor the usage of this area (by default on
LinuxX86 the JVM reserves 48M to this aim)
--------------------------
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
