The message forwarding processor is a message processor that consumes messages in a message store and sends them to an endpoint. If the message was successfully delivered to the endpoint, the processor will delete the message from the message store. In case of a failure, it will retry after a configured interval.
...
Additional message forwarding processor parameters
Following are the additional parameters In addition to the mandatory endpoint name and message store parameters, you can set the following additional parameters when adding a message forwarding message processor:
Parameter Name | Value | Required |
|---|---|---|
Processor State (is.active) | Activate (true) or Deactivate (false) | Yes |
Forwarding Interval (interval) | Interval in milliseconds in which processor consumes messages | No (The default value is 1000) |
Retry Interval ( | Message retry interval in milliseconds | No (The default is value is 1000) |
| Non retry HTTP status codes (non.retry.status.codes) | Message Processor look at this parameter before it decides if it has to retry. If the response's HTTP status code is one of the specified status codes, it won't retry. | No |
Maximum Delivery Attempts ( | Maximum redelivery attempts before deactivating the processor | No |
Axis2 Client Repository ( | Axis2 Client repository path. This is the location where services and modules reside. | No |
Axis2 Configuration ( | Axis2 Configuration to be used to send messages | No |
Reply Sequence Name ( | Name of the sequence where the message reply should be sent | No |
Fault Sequence Name ( | Name of the sequence where the fault message should be sent to in case of a SOAP fault | No |
Quartz Configuration File Path ( | Quartz configuration file path. This properties file contains the Quartz configuration | No |
Cron Expression ( | Cron expression to be used to configure the retry pattern | No |
Pinned Servers (pinnedServers) | A comma-separated list of server names where the message processor should be started, so that when you start the message processor on an ESB server, it is only started on that server if the server name is in this list. This is useful when you have multiple ESB instances in a cluster. | No |
...