Best Practices from Oracle Development's A‑Team

WebLogic Server: Saving Disk Space in /tmp

Olaf Heimburger
Workload Architect - Security


Many WebLogic Server (WLS) implementations use JRockit 28 as the JVM implementation. JRockit 28 comes with the very useful JRockit Flight Recorder which helps in many troubleshooting situations.


In high volume WLS implementations with many domains and many managed servers the Flight Recorder could fill up the disk of the temporary file storage (often located at /tmp). This works good for some time, but suddenly results in failures during restarts of some servers. It often helps to remove old and outdated data in the temporary file storage.


Monitoring the disk space requires a lot of discipline or a decent tool like Oracle Cloud Control 12c and may be forgotten in peak hours. A simple solution is to use a file store with a much higher disk capacity. This can be done by setting the JRockit Flight Recorder output repository to the new location by passing the following parameter to the JVM: -XX:FlightRecorderOptions=disk=true,maxsize=1GB,repository=/u01/app/jfrtmpfiles. Here is how (pick only one of these options):

At the command line:

export JAVA_OPTIONS=-XX:FlightRecorderOptions=disk=true,maxsize=1GB,repository=/u01/app/jfrtmpfiles ./startWeblogicServer.sh

In DOMAIN_HOME/bin/setDomainsEnv.sh add it right after the export WL_HOME:

WL_HOME="C:/oracle/wls/1036/wlserver_10.3" export WL_HOME JAVA_OPTIONS=-XX:FlightRecorderOptions=disk=true,maxsize=1GB,repository=/u01/app/jfrtmpfiles export JAVA_OPTIONS

For Fusion Applications only update the file DOMAIN_HOME/config/fusionapps_start_params.properties in each Fusion Applications Domain:

fusion.default.default.sysprops=-XX:FlightRecorderOptions=disk=true,maxsize=1GB,repository=/u01/app/jfrtmpfiles -Dapplication.top...


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha