## org.autoplot.EventThreadResponseMonitor

This utility regularly posts events on the event thread, and measures processing time. This should never be more than 500ms (warnLevel below). See org.das2.util.awt.LoggingEventQueue, which was a similar experiment from 2005. This now monitors the event thread for hung events. Bugs found: https://sourceforge.net/p/autoplot/bugs/863/ If the file HOME/autoplot_data/log/request_dump.txt is found, this will trigger a heap dump and the file will be deleted.

## EventThreadResponseMonitor( )

## addToMap

addToMap( String key, Object value ) → void

add to the information.

### Parameters

key - see GuiExceptionManager
value - an Object

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## dumpPendingEvents

dumpPendingEvents( ) → String

show all the events on the event thread by unqueuing and requeuing them. This should not be used in production use.

### Returns:

String representation
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## main

main( String[] args ) → void

### Parameters

args - a java.lang.String[]

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## setLogFile

setLogFile( java.io.File f ) → void

set to the name of a file where event thread response times will be logged. This should be a folder local to the machine.

### Parameters

f - a File

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## start

start( ) → void

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]