Manage Log Size and Rotation Policy in IBM WebSphere Application Server

Log files are essential for troubleshooting and monitoring applications on IBM WebSphere. Here’s how to set up log size and rotation policies for an application server in Websphere:

    1. Access the Administrative Console.
    2. Navigate to “Troubleshooting” > “Logs and trace”.
    3. Select the server you want to set up the log size and rotation policy for.
    4. Configure log file size.
    5. Set “Maximum Number of Historical Files” for retention.
    6. Click ok and save changes.
    7. Restart the application server for it to take effect.

Efficient log management ensures optimal performance and storage utilization in WebSphere Application Server. Refer to official IBM documentation for version-specific details.

Auto Restart Websphere JVM after a Crash

Auto-restarting the WebSphere JVM after a crash can be a useful feature for ensuring uptime and minimizing downtime. In this blog post, we will discuss how to enable the auto-restart setting in WebSphere.

First, navigate to the Monitoring Policy under Java and Process Management section for the Application Server in the WebSphere administrative console. In the Monitoring Policy, you will find the option to set the Node Restart State. Change this setting to “Running” for the JVM in question.

It’s worth noting that this setting will also bring the JVM up when the node is started, ensuring that your application is always running and available.

Additionally, it is recommended to monitor the JVM logs, and in case the JVM crashes frequently, it’s best to investigate the root cause of the crash.

For more information, refer to the following link:

In conclusion, auto-restarting the WebSphere JVM after a crash can be a useful feature that helps to ensure uptime and minimize downtime. By following the steps outlined in this post and the reference link provided, you can easily enable the auto-restart setting in WebSphere and keep your application running smoothly.