Installs an AsyncEventListener implementation to GemFire XD peers in a specified server group.


  LISTENERCLASS 'class-name'
  INITPARAMS 'init-params'
  [ MANUALSTART boolean-constant ]
  [ ENABLEBATCHCONFLATION boolean-constant ]
  [ BATCHSIZE integer-constant ]
  [ BATCHTIMEINTERVAL integer-constant ]
  [ ENABLEPERSISTENCE boolean-constant ]
  [ DISKSTORENAME  store-name]
  [ MAXQUEUEMEMORY integer-constant ]
  [ ALERTTHRESHOLD integer-constant ]
  SERVER GROUPS ( server_group_name [, server_group_name ]*)
The fully-qualified name of the class that implements the AsyncEventListener interface. For example, "user.application.TestAsyncEventListener". If you are configuring the built-in DBSynchronizer implementation, specify com.pivotal.gemfirexd.callbacks.DBSynchronizer.
Specify initialization parameters to pass to the init() method of the AsyncEventListener implementation.
GemFire XD passes a single string of initialization parameters when you execute the CREATE ASYNCEVENTLISTENER statement. You must include the INITPARAMS argument, even if it defines no parameters (INITPARAMS '').
As a best practice, Pivotal recommends that you supply only a single parameter in the string using the format file=path-to-file, where path-to-file references a file that defines each listener parameter on a dedicated line, similar to:
Using a separate parameter file enables you to change initialization parameters after you have configured the listener in GemFire XD. Only the file path is hard-coded in the listener configuration. If you define parameters in the string passed to INITPARAMS, then you must drop and re-create the listener in order to change any of those parameter values.
If you send user credentials in the initialization parameters, consider encrypting the password using encrypt-password with the external option. Your listener will need to use the AsyncEventHelper.decryptPassword method to decrypt the password before sending credentials to the outside data source.
The built-in DBSynchronizer implementation requires specific parameters in order to initiate a connection to a JDBC data source. If you supply these parameters in the INITPARAMS string, use the format: 'db-driver-class,db-url[,user=user-name,[,password=plan-text-password|secret=encrypted-password[,transformation=tranformation-name][,keysize=size]]'
In this initialization string:
  • db-driver-class specifies the fully-qualified class name of the JDBC driver to use for connecting to the external database.
  • db-url specifies the JDBC connection string to use to connect to the external database. For example, to connect to an external Apache derby database, you would specify a DBSynchronizer INITPARAMS string similar to 'org.apache.derby.jdbc.EmbeddedDriver,jdbc:derby:newDB;create=true;'.
    Note: Any password that you specify in the JDBC URL (for example by appending ?user=username&password=password) may appear in external exception messages. GemFire XD attempts to mask password values in exception messages by matching common patterns such as password=..., password=.., or pwd=... However, the actual value may appear in exception messages under certain circumstances. To prevent the password from appearing in external exceptions, omit the username and password from the URL and instead specify them using the remaining options.
  • [,user=user-name[,password=plan-text-password|secret=encrypted-password[,transformation=tranformation-name][,keysize=size]]' optionally specifies the username and password to use for the connection. If you do not specify these options, then GemFire XD uses the db-url value is used as-is. If you use the password option, specify the plaint-text password for the user.

    To avoid storing plain-text passwords in scripts used to start DBSynchronizer, you can instead specify the secret option with the encrypted password for the user. Use the encrypt-password command with the external option to encrypt the password. When you specify an encrypted password with the secret option, you can also include the transformation and keysize options to match the transformation algorithm and key size that you specified when encrypting the password with encrypt-password. If you do not include these options, the default transformation is AES with a keysize of 128 bits.

To specify the DBSynchronizer database driver and URL in a separate file (using INITPARAMS 'file=path-to-file', the parameter entries must use the format:
To specify the username and password outside of the JDBC URL, also include:
Or, to use an encrypted password in the properties file specify the required options for decryption:
A boolean value that specifies whether you need to manually start the listener with SYS.START_ASYNC_EVENT_LISTENER. If you do not supply a value, the default is "true" and you must start the listener manually using SYS.START_ASYNC_EVENT_LISTENER.
A Boolean value that determines whether GemFire XD should conflate messages. The default is false.
The maximum number of messages that a batch can contain. The default is 100 messages.
The maximum number of milliseconds that can elapse between sending batches. The default is 1000 milliseconds.
A Boolean value that determines whether GemFire XD persists the event queue to disk for high availability. The default is "False."
The named disk store to use for persisting the event queue. If you specify a value, the named disk store must exist. If you specify a null value, GemFire XD uses the default disk store for persistence.
The maximum amount of memory in megabytes that the queue can consume before overflowing to disk. The default is 100 megabytes.
The maximum number of milliseconds that an event can remain in this queue before GemFire XD logs an alert. The default is value is "0."
A comma-separated list of server group names. GemFire XD deploys the event listener implementation on all peers in the specified server group(s).
Note: The specified server groups must contain at least one data store member at the time you execute the CREATE ASYNCEVENTLISTENER statement.
Note: When you deploy an event listener (or DBSynchronizer) to listen for asynchronous events, specify a server group that contains no more than 3 data stores. GemFire XD automatically designates the first listener to startup as the "primary," and the remaining listeners become "secondaries." Every additional "secondary" can slow down the publisher. By default all GemFire XD members that store data are members of a single "default" server group.

When multiple data stores host an event listener, there is no direct way to ensure that a specific GemFire XD data store hosts the active instance. If you require a specific member to host the active instance, ensure that only that member is running in the target server groups when you deploy the listener and attach the table. You can then start the remaining data stores in the server group, and they will host redundant, standby instances.


Install a basic AsyncEventListener implementation to all data stores in the SG1 server group:

   LISTENERCLASS 'user.application.TestAsyncEventListener'

Install a DBSynchronizer configuration with a persistent event queue:

  LISTENERCLASS 'com.pivotal.gemfirexd.callbacks.DBSynchronizer'
  INITPARAMS 'org.apache.derby.jdbc.EmbeddedDriver,jdbc:derby:newDB;create=true;'

Create a new table and attach the installed DBSynchronizer:

     NAME VARCHAR(10)) 
Note: You can optionally install the AsyncEventListener configuration after you associate a table with the listener name. Make sure that you use the same listener name with both the CREATE ASYNCEVENTLISTNER command and the CREATE TABLE command.