1 Reply Latest reply on May 7, 2013 1:05 PM by Cvele_new_account

    zero byte flight recorder files and missing jrockit.oomdiagnostics file

      We have an app in production using the latest 64-bit version of JRockit that is throwing OutOfMemory errors. JRockit version info is:

      java version "1.6.0_22"
      Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
      Oracle JRockit(R) (build R28.1.1-14-139783-1.6.0_22-20101206-0241-linux-x86_64, compiled mode)

      Weblogic version is 10.3.4.

      Redhat Linux version:
      2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:52:51 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

      The weblogic domain has the admin server and a single managed server. The latter is throwing Out of memory errors with the message: allocLargeObjectOrArray. Based on searching forums and these two threads, I 'm going to try and tweak -XXlargeObjectLimit and XXtlaSize options.

      Default XX:MaxPermSize on WebLogic Server
      Thread Local Area and OutOfMemoryError: nativeGetNewTLA

      But I was hoping to use a couple of Jrockit's diagnostic features to better understand the problem but I 'm not having much success.

      1. All of the managed server's Flight recording files (.jfr) files under $DOMAIN/servers/ManagedServerA/logs/diagnostic_images are zero byte sized! I thought by default this version of Jrockit is supposed to create a .jfr file that we can use to figure out what happened. I even tried a second recording using 'jrcmd' and gave it another file path but that is zero byte sized as well. I 'm sure both directories are writable by the user running the managed server process.

      2. The managed server has been started with the option -Djrockit.oomdiagnostics.filename=/path/to/oom-diags-file. However that file is not getting created when the server runs out of memory.

      Any ideas?