1.1.1

Display Installed AsyncEventListeners
You can join the SYSTABLES, MEMBERS, and ASYNCEVENTLISTENERS tables to display the listener
implementations associated with a table as well as the data store ID on which the listener is installed:
select t.*, m.ID DSID from SYS.SYSTABLES t, SYS.MEMBERS m,
SYS.ASYNCEVENTLISTENERS a
where t.tablename='<table>' and groupsintersect(a.SERVER_GROUPS,
m.SERVERGROUPS)
and groupsintersect(t.ASYNCLISTENERS, a.ID);
See SYSTABLES on page 677 and ASYNCEVENTLISTENERS on page 655.
Stop or Remove an AsyncEventListener Configuration
To stop a running AsyncEventListener configuration, first use the SYS.WAIT_FOR_SENDER_QUEUE_FLUSH
procedure to ensure that no queued events are lost. Then use SYS.STOP_ASYNC_EVENT_LISTENER and
specify the identifier to the configuration to stop:
java.sql.Connection conn = getConnection();
CallableStatement cs1 = conn.prepareCall("call
SYS.WAIT_FOR_SENDER_QUEUE_FLUSH(?,?,?);
cs1.setString(1, "MyID");
cs1.setString(2, "TRUE");
cs1.setString(3, "0");
cs1.execute();
CallableStatement cs2 = conn.prepareCall("call
SYS.STOP_ASYNC_EVENT_LISTENER( ? )");
cs2.setString(1, "MyID");
cs2.execute(); CallableStatement cs2 = conn.prepareCall("call
SYS.STOP_ASYNC_EVENT_LISTENER( ? )");
cs2.setString(1, "MyID");
cs2.execute();
This waits for all queued events to flush, and then stops dispatching events to the callback listener class. Also,
the close() method of the Callback AsyncEventListener class is invoked so that the implementation can
perform any necessary cleanup.
You can also remove a listener implementation from the cluster using DROP ASYNCEVENTLISTENER on
page 517.
vFabric SQLFire User's Guide202
Caching Data with vFabric SQLFire