• System diagnostics are grouped together and linked on the page,
  • EASA→Administrator→System→Diagnostics

• These five links are described below,
  • Summary
  • Server Output
  • Logging
  • Active Commands
  • Free Resources

The System Information heading lists details of EASA's resource footprint, by default this includes

• current memory usage
• peak memory usage since EASA was last started
• maximum memory usage allowed
• Java version in use
• free disk space
• number of threads being run by EASA
• number of commands running

Additional system resource values can be configured for display 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.

• Throughput show values accumulated since the EASA Server 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

The Server Output page provides diagnostic messages from the EASA Server.

• these include messages about
  • 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 an EASA system.

• there are several actions available under the Actions dropdown beneath the log window,
  • Refresh → Update the display of messages in the log window.
  • Start New → Begin a new log file.
  • Download All → The current and old logs, are downloaded in a .zip file.
  • Delete Old Logs → Delete old log files from the filesystem.

• the messages shown on the Diagnostics page are stored in a text file
  • <SERVERDATA>\admin\logs\server.txt

• older archived log files are also stored in <SERVERDATA>\admin\logs\ with date stamps added to the file names
  • logs are rolled over once they reach a certain size, modify the properties below in
    • <SERVERDATA>\easa\admin\config\context.properties
      • easa.server.syslog.rolloverMaxSizeInMB=10.0
        • → when <SERVERDATA>\easa\admin\config\server.txt exceeds 10MB, start a new log
      • easa.server.syslog.rolloverCheckInHours=4
        • → check every 4 hours to see if the server log exceeds rolloverMaxSizeInMB

The output from the Tomcat HTTP server (HTML localhost:80) is also available from this page, access it via the radio buttons above the log window.

• this information is also found at
  • <EASAROOT>\tomcat\logs\jsf-easa.log

• finally EASAP Server logs are found at
  • <SERVERDATA>\jsf-eas\admin\logs\jsf-easa.log
  • EASAP-specific logs are found in the same folder

On the Logging page, set the level or quantity of logging performed by EASA, stored in the server.txt file and displayed on the Server Output page.

• There are two different types of diagnostic messages,
  • Queue messages
  • Web Page request messages

• To change the logging level, 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.

Press the Free Resources button to free up computer memory that the EASA Server no longer needs. 'Before' and 'after' memory usage is displayed.

• Thread Details link shows,
  • Current number of threads
  • Peak number of threads
  • Total started threads
  • Deadlocked Threads
  • Monitor-Deadlocked Threads

EASA uses many threads though the roles of each are not in the scope of this document.

• The Log Stacktraces button prints all data related to threads into the server log,
  • EASA→System→Diagnostics→Server Output→EASA Server

All Threads shows the current status for all EASA threads.

Memory is freed up 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 to monitor additional system resources by making use of Performance Logs defined in the Computer Management tool available in Windows.

• To add a new System Resource Monitor Value for display on the Summary page under the Diagnostics selection,
  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/System.properties

• on an EASA Server running Windows XP select…
  • Start Menu→Settings→Control Panel→Administrative Tools→Computer Management
• sn the Computer Management window that appears, expand…
  • System Tools→'Performance Logs and Alerts'
  • right click→Counter Logs
  • select New Log Settings… on the pop-up menu
  • type in a name for the new counter
  • Click on OK.
• a window appears to configure the new counter
• on the General tab,
  • click on the Add Counter… button
  • the Add Counters window opens
• add a counter
  • select the desired Performance object from the list
  • select the desired Counter in the next list
  • click on the Add button.
• repeat for other counters.
• once other counters have been added
  • click on the Close button
• configure the counter log file
  • click on the Log Files tab
  • click on Configure. . .
    • specify the file Location and File name
• set the Log file size to a specified Limit of say 500 KB or 1 MB
• click on OK
• set the Log file type to ‘Text File (Comma delimited)’
• set the schedule for the log file by clicking on the Schedule tab,
• leave the Start log setting to the current date and time
• set the Stop log settings to,
  • stop When the log file is full
  • Start a new log file when a log file closes.
• click on OK to start the new counter log file.

Unlike in Windows XP, Counter Logs in Windows 7 are organized into Data Sets. To create a new Counter Log in Windows 7, please follow these instructions.

• on an EASA Server running Windows 7
  • type 'Computer Management' under the Start menu to find the program
• in the Computer Management window,
  • expand Performance
  • expand Data Collector Sets
  • right click on User Defined
  • select New→Data Collector Set
  • type in a name for the new set
    • choose Create Manually
    • click Next
  • tick the Performance Counter
  • click Next
• next to the Performance Counters pane
  • click Add…
• in the next window, select a performance counter from the list
• add this counter to the Added counters pane by clicking Add»
• add more than one counter, if desired
• when finished, click OK to close the Add counters window
• click Finish to create the Data Collector Set
• in the middle pane for the newly created Data Collector Set
• right-click the Performance Counter object and click Properties
• set the Log format to 'Comma Separated' in the drop-down box
• on the File tab, give it a relevant name and choose the Log mode as Overwrite
• → this creates a CSV file for EASA to work with, and we’re more interested in current performance information
• define where and how to store the log file
  • right-click on the Data Collector Set in the tree
  • select Properties
• set the root directory for the log files under the Directory tab
  • (such as C:\perflogs, for simplicity)
• to keep a consistent file name for EASA to locate
  • clear the Subdirectory name format field
  • unselect the Prefix subdirectory with computer name option

The log file is stored in the root folder.

• finally set the schedule for the log file,
  • click on the Schedule tab
  • add a default Start log setting with the current date
  • click the Stop Condition tab
  • select the Restart the data collector set at limits box.
  • check the Maximum Size box,
    • set a value of say, 1MB.
• click on OK,
  • right-click the Data Collector Set
  • click Start to start the new counter log file immediately

• after creating the new counter log file, proceed to add an entry for the new monitor in the file
  • <SERVERDATA>/admin/config/System.properties

• to add the entry and complete the addition of the new System Resource Monitor Value
  • open the System.properties file in a text editor such as Notepad or Wordpad
  • add an entry for each new counter added to the counter log file created 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 of the column containing the monitor value data in the log file
      • <title_shown_on_summary_page> is the text shown on the Sytem Information→Summary page

Examples,

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

• once finished add entries
• save the System.properties file
• exit the text editor

• finally stop and restart the EASA Server for the new System Resource Monitor Value to be displayed at
  • EASA→Administrator→System→Diagnostics