Class NullConnectionErrorHandler
- All Implemented Interfaces:
ComponentLifecycle,ConnectionErrorHandler
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.
-
Field Summary
Fields inherited from class com.adaptris.core.ConnectionErrorHandlerImp
log -
Constructor Summary
Constructors -
Method Summary
Methods inherited from class com.adaptris.core.ConnectionErrorHandlerImp
allowedInConjunctionWith, getRegisteredChannels, registerConnection, restartAffectedComponents, retrieveConnection, retryWaitTimeMs
-
Constructor Details
-
NullConnectionErrorHandler
public NullConnectionErrorHandler()
-
-
Method Details
-
handleConnectionException
public void handleConnectionException()Description copied from interface:ConnectionErrorHandlerHandle the error. -
init
Description copied from interface:ComponentLifecycleInitialises the component.Component initialisation includes config verification, creation of connections etc.
- Throws:
CoreException- wrapping any underlyingExceptions
-
start
Description copied from interface:ComponentLifecycleStarts the component.Once a component is started it should be ready to process messages. In the case of
AdaptrisMessageConsumer, calling start will begin message delivery.- Throws:
CoreException- wrapping any underlyingExceptions
-
stop
public void stop()Description copied from interface:ComponentLifecycleStop the componentA stopped component is not expected to be ready to process messages. In the case of
AdaptrisMessageConsumer, calling stop will pause message delivery. Throwing aRuntimeExceptionmay cause unintended consequences -
close
public void close()Description copied from interface:ComponentLifecycleCloses the component.A closed component should release any connections it uses, etc. and clean up completely. Throwing a
RuntimeExceptionmay cause unintended consequences
-