here is my machine info:
- dual cpu (xeon 2.2G) IBM machine with 2x8 GB memory - work only for repository (plus postgredb) - with modjk to work with apache - using only xmlui-mirage - Current JAVA_OPTS="-Xmx8192M -Xms8192M -XX:MaxPermSize=1024M -XX:PermSize=1024M -XX:+UseParallelGC -XX:-UseLoopPredicate -Dfile.encoding=UTF-8 -Dcom.sun.management.jmxremote=true" - OS: RedHat Enterprise 5.6 64 bit - DSpace 3.1Thanks
On 06/26/2013 06:36 PM, Hilton Gibson wrote:Can you send the following system specs:
1. Server operating system.2. Server hardware, with RAM and CPU details.3. DSpace version and UI used.4. Details of guides or links used to setup the IR.
On 26 June 2013 12:04, Ady Wahyudi Paundu <email@example.com> wrote:
unfortunately my system still experiencing unscheduled tomcat shutdown
(even after i increase the heap and permgen).
this is the error message i got from catalina.out:
> # A fatal error has been detected by the Java Runtime Environment:
> # SIGSEGV (0xb) at pc=0x00002afaab76955d, pid=6604, tid=1081977152
> # JRE version: 7.0_21-b11
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode
> linux-amd64 compressed oops)
> # Problematic frame:
> # V [libjvm.so+0x69b55d] MachNode::in_RegMask(unsigned int) const+0x3d
> # Failed to write core dump. Core dumps have been disabled. To enable
> core dumping, try "ulimit -c unlimited" before starting Java again
> # An error report file with more information is saved as:
> # /home/dzpac3/hs_err_pid6604.log
> # If you would like to submit a bug report, please visit:
> # http://bugreport.sun.com/bugreport/crash.jsp
i know this is JVM problem (and not dspace's), but i'm asking this
can anybody help me for a solution?