Page History

...

1. Deprecate existing internal boolean system property: REMOVE_FROM_QUEUE_ON_EXCEPTION
   1. Continue to support default behavior if boolean set to false by setting # retries on receiver to -1

2. Create new Java API

   1. Define callback API for senders to set callback to dispatchers

   2. Invoke callback if batch exception occurs prior to batch removal

   3. Implement a default callback API (see item 8 5 below)

   4. Add parameters on gateway receiver factory for # retries and wait time between retries.

3. Modify Gfsh commands

   1. Add option to gfsh ‘create gateway sender’ command to specify custom callback

   2. Add options to gfsh ‘create gateway receiver’ command to set # retries and wait time between retries
      

   3. Store new options in cluster config
      

      1. Sender: callback implementation
         

      2. Receiver: # of retries and wait time between retries

4. Add support in cache.xml for specifying new callback for gateway sender and setting new options for gateway receiver

5. Create example implementation of Sender callback that writes event(s) and associated exceptions to a file

6. Security features  

   1. Define privileges needed to deploy and configure sender callback

   2. With security, callback should only write eventId's and exceptions, i.e. no entry values should be written to disk

7. Add logging and statistics for callback

   1. Log messages for gateway receiver for start time and results of retries

   2. Add statistics and MBean for callbacks in-progress, completed, # and duration

New workflow for setting up WAN gateway using gfsh:

1. Create gateway receiver including new options for specifying # of retries and wait time between retries
2. Deploy jar on gateway sender(s) containing callback implementation
3. Create gateway sender with option to add callback

API Change

1. TBD
   
   

Risks and Unknowns

1. How to handle class not found exception for sender callback

2. Default behavior when no callback is provided for sender? - Should be same as current behavior
3. Backward compatibility behavior
   1. old sender connected new receiver using new options
   2. new sender with callback implemented connected to old receiver without new options
4. Sort out security privileges needed for deploying vs installing with sender vs reading values for failed events written to disk.