This page describes features that allows you to keep track of the resources being used by EASA Server together with any diagnostic messages from the EASA Server.

You can see how EASA is running on the EASA Server by selecting Diagnostics under the System menu while in Administrator mode. On the Diagnostics page, you can access five other pages:

• Summary
• Server Output
• Logging
• Active Commands
• Free Resources

Each of these pages will be described in more detail in the following sections.

On the Summary page, the computer resources being used by EASA are shown below the System Information heading. By default, the following values will be displayed under System Information:

• Current memory usage
• Peak memory usage since EASA was last started
• Maximum memory usage allowed
• Java version being used
• Free disk space
• Number of threads being run by EASA
• Number of commands running

Additional system resource values can be configured to be displayed under System Information by making use of Performance Logs defined in the Computer Management tool available in Windows. See Adding a System Resource Monitor Value for details.

The next section on the Summary page having the Throughput heading displays the following throughput values accumulated since EASA Server software was last started:

• Time EASA Server has been running
• Web pages generated
• HTTP requests processed
• Number of runs submitted to EASAP queue
• Maximum number of runs in the EASAP queue at any one time
• Number of commands previously run

On the Server Output page, the diagnostics messages that are output from EASA on the EASA Server are shown in the box below the Server Output heading. This server output is made up of a variety of messages about such things as:

• Initialization of EASA
• Transactions within the EASAP queue
• Error messages

Many of the messages are time and date stamped to help track down when and why problems may have occurred on your EASA system. There are several actions available to you under the ‘Actions’ dropdown beneath the log window:

• Refresh – Updates the display of messages in the log window.
• Start New – Begins a new log file.
• Download All – The current log, along with old log files, are downloaded in a .zip file.
• Delete Old Logs – Old log files are deleted from the filesystem.

Tip: The messages shown on the Diagnostics page under the Server Output heading are stored in a text file called server.txt in the <SERVERDATA>/admin/logs folder. Older archived log files are also stored here with date stamps added to the file names.

Output from the HTML Server is also available from this page, and can be accessed via the radio buttons above the log window. This corresponds to the information from

 tomcat/webapps/jsf-easa/admin/logs/jsf-easa.log.

On the Logging page, you have the ability to set the level or quantity of logging performed by EASA, which is stored in the server.txt file and displayed on the Server Output page described in the previous section. There are two different types of diagnostic messages that can be controlled on the Logging page, Queue messages and Web Page request messages. To change the logging level, just perform the following two steps:

1. Select the logging level using the Queue and Web Pages choice lists
2. Click on the Update Settings button

This table lists all the system commands currently being run by EASA. These typically are associated with submitted EASAP processes being run either locally on the EASA Server acting as a compute server or via rsh commands to a remote compute server.

By pressing the Free Resources button, you initiate a request for the EASA Server to free up any computer memory that it no longer needs to be using. The information on the Free Resources page shows memory usage information before and after the memory free up process.

Under Thread Details you can see Current number of threads, Peak number of threads, Total started threads, Deadlocked Threads and Monitor-Deadlocked Threads. Many threads make up EASA. Their roles and how they work are not in the scope of this document and therefore they are for advanced users only. The Log Stacktraces button is used for printing all data related to threads into the server log (found under System → Diagnostics → Server Output → EASA Server).

Under All Threads, you can see a list of the current threads and their respective status.

Note: During normal operation, memory is also freed up by EASA automatically from time to time.

In addition to the default system resource values displayed on the Summary page under the Diagnostics selection, it is possible for you to monitor more system resource values by making use of Performance Logs defined in the Computer Management tool available in Windows.

Note: The procedures and functionality described in this section will not apply to EASA Servers running under Linux.

To add a new System Resource Monitor Value for display on the Summary page under the Diagnostics selection, you need to complete two separate procedures:

1. Create a new Counter Log using the Computer Management tool available in Windows.
2. Add an entry for the new monitor in the System.properties file located under <SERVERDATA*>/admin/config within the EASA installation.

To create the new Counter Log in Windows XP, please follow the instructions given below:

1. On an EASA Server running Windows XP, select Settings → Control Panel → Administrative Tools → Computer Management under the Start menu.
2. On the Computer Management window that appears, expand Performance Logs and Alerts under System Tools.
3. Right click on Counter Logs and select New Log Settings… on the pop-up menu. Then type in a name for the new counter and click on OK.
4. After entering a name, a window will appear for configuring the new counter. On the General tab, click on the Add Counter… button to open the Add Counters window. On this next window, add counters by first selecting the desired Performance object from the list, then selecting the desired Counter in the next list and finally clicking on the Add button. You can add more than one counter. When you are finished click on the Close button.
5. Next you configure the counter log file, by clicking on the Log Files tab, clicking on Configure… to specify the file Location and File name. It is also suggested that you set the Log file size to a specified Limit of say 500 KB or 1 MB at this time and then click on OK. Next, set the Log file type to ‘Text File (Comma delimited)’.
6. Finally, you set the schedule for the log file by clicking on the Schedule tab, leaving the Start log setting to the current date and time, and then setting the Stop log settings to stop When the log file is full and to Start a new log file when a log file closes.
7. Click on OK to start the new counter log file.

Counter Log functionality in Windows 7 differs to Windows XP in that they are organized into Data Sets. However, we can still achieve the desired results with a few configuration options. To create the new Counter Log in Windows 7, please follow the instructions given below:

1. On an EASA Server running Windows 7, you can simply type “Computer Management” under the Start menu to find the program.
2. On the Computer Management window that appears, expand Performance, and then Data Collector Sets.
3. Right click on User Defined and select New → Data Collector Set. Then type in a name for the new set, choose Create Manually and click Next. Tick the Performance Counter box and click Next.
4. Next to the performance counters pane, click Add… and in the next window, select a performance counter from the list. Add this counter to the Added counters pane by clicking Add». You can add more than one counter. When you are finished, click OK to close the Add counters window, and click Finish to create the Data Collector Set.
5. In the middle pane for your newly created Data Collector Set, right click the Performance Counter object and click Properties. Set the Log format to “Comma Separated” in the dropdown box, and on the File tab, give it a relevant name and choose the Log mode as Overwrite. We’re doing this because we need a CSV file for EASA to work with, and we’re more interested in current performance information.
6. Next, we will define where and how to store the log file by right clicking on the Data Collector Set in the tree and selecting Properties. Here you can set the root directory for the log files under the Directory tab (such as C:\perflogs, for simplicity). In order to keep a consistent file name for EASA to locate, we need to clear the Subdirectory name format field and unselect the Prefix subdirectory with computer name option. This will ensure that the log file is always in the same place – the root folder.
7. Finally, set the schedule for the log file by clicking on the Schedule tab, adding a default Start log setting with the current date, and then clicking the Stop Condition tab and selecting the Restart the data collector set at limits box. Check the Maximum Size box and set a value of say, 1MB.
8. Click on OK, right click the Data Collector Set and click Start to start the new counter log file immediately.

Now that the new counter log file has been initiated, you can proceed to adding an entry for the new monitor in the System.properties file located under <SERVERDATA>/admin/config in your EASA installation. To add the entry and complete the addition of the new System Resource Monitor Value, please follow the instructions given below:

• Open the System.properties file in a text editor such as Notepad or Wordpad.

• You will be adding an entry for each new counter added to the counter log file created in the previous procedure above. These entries take the following form:

 easa.server.systemmonitor<text>=<location_of_log_file>,<column_number>,<title_shown_on_summary_page>

where <text> is unique identifier such as a number, <location_of_log_file> is the full path to the log file including the file name, <column_number> is the number corresponding to the column containing the monitor value data in the log file, and <title_shown_on_summary_page> is the text shown on the Summary page under the System Information heading.

Examples:

 easa.server.systemmonitor1=C\:/PerfLogs/cpu.csv,2,% CPU Time

 easa.server.systemmonitor2=C\:/PerfLogs/mem.csv,2,RAM Usage

• Once you have finished adding your entries, save the System.properties file and exit the text editor.

• Finally, you need to stop and restart the EASA software on the EASA Server for the new System Resource Monitor Value to be displayed on the Summary page under the Diagnostics selection.