Using the J-Web UI can sometimes result in slow response times. While efforts are underway to help improve response times, there are a few actions that can be taken to eliminate any external factors.

This article lists some of these actions.

How can I increase the response-time performance when performing management actions on an SRX device from J-Web? For instance, when I click an action or an interface, it takes several seconds for the page to load.

Several measures can be undertaken to help improve performance issues:

• Check the applicable Junos OS Release Notes to ensure that the OS, the browser, and the browser versions are supported in the current Junos software release that is installed and running on the SRX device.

Currently, IE 7.0 as well as Mozilla Firefox 3.0 are supported.

• If a supported browser and OS are used to manage the SRX device through J-Web, go to the browser and delete all cookies and browsing history.

• If the problem persists, download another supported browser application and check to see if the problem is still present.

• Check the number of system users currently logged in to the SRX device by running the show system users command.

• By default, an unlimited number of users can log in to the J-Web interface on a routing platform, and each session remains open for 24 hours (1440 minutes). Using CLI commands, you can limit the maximum number of simultaneous J-Web user sessions and set a default session timeout for all users.

To limit the number of simultaneous J-Web user sessions, execute the commands below:

user@host# edit system services web-management session
user@host# set session-limit session-limit
Range: 1 through 1024. Default: Unlimited

To change the J-Web session idle time limit, execute the commands below:

user@host# edit system services web-management session
user@host# set idle-timeout minutes
Range: 1 through 1440. Default: 30

You can also configure the maximum number of simultaneous subordinate HTTP processes that the routing platform creates in response to user requests.

To configure the maximum number of subordinate HTTPD processes, execute the commands below:

user@host# edit system services web-management limits
user@host# active-child-process process-limit
Range: 0 through 32. Default: 5

• Check system storage by entering the show system storage command, and delete any unnecessary files.

• The SRX platform has configuration size limitations. When these are reached, J-Web will not be able to manage the SRX device. Details on this can be found in KB20520 - [SRX] Unable to manage devices via J-Web due to large configuration [juniper.net] , which explains how to check configuration file size as well as the maximum configuration file size for various SRX series platforms.

• If the performance is still slower than expected after all the above items are addressed, refer to the applicable SRX series Junos Release Notes for information about changes being made to help improve the performance of J-Web management.

2020-06-17: Changed the default idle-timeout value from 1440 to 30