public class NullConnectionErrorHandler extends ConnectionErrorHandlerImp
Implementation of ConnectionErrorHandler
for use with polling consumers where you do not want an Exception thrown
back to run to re-init the Channel.
In the adapter configuration file this class is aliased as null-connection-error-handler which is the preferred alternative to the fully qualified classname when building your configuration.
log
Constructor and Description |
---|
NullConnectionErrorHandler() |
Modifier and Type | Method and Description |
---|---|
void |
close()
Closes the component.
|
void |
handleConnectionException()
Handle the error.
|
void |
init()
Initialises the component.
|
void |
start()
Starts the component.
|
void |
stop()
Stop the component
|
allowedInConjunctionWith, getRegisteredChannels, registerConnection, restartAffectedComponents, retrieveConnection, retryWaitTimeMs
public void handleConnectionException()
ConnectionErrorHandler
public void init() throws CoreException
ComponentLifecycle
Component initialisation includes config verification, creation of connections etc.
CoreException
- wrapping any underlying Exception
spublic void start() throws CoreException
ComponentLifecycle
Once a component is started it should be ready to process messages. In the case of AdaptrisMessageConsumer
, calling start
will begin message delivery.
CoreException
- wrapping any underlying Exception
spublic void stop()
ComponentLifecycle
A stopped component is not expected to be ready to process messages. In the case of AdaptrisMessageConsumer
, calling stop
will pause message delivery. Throwing a RuntimeException
may cause unintended consequences
public void close()
ComponentLifecycle
A closed component should release any connections it uses, etc. and clean up completely. Throwing a RuntimeException
may
cause unintended consequences