...
If the dynamic sequences are loaded to the memory at least once, the ESB will continue to use the cached version of the sequence, as long as the registry is unreachable. A warning will be logged every time ESB attempts to load the sequence from the registry and fails. As soon as the registry comes back on-line, ESB will load the sequence from the registry.
What is the recommended approach for dealing with *.back files that are created when there is an error in an ESB artifact?
You can delete the *.back file manually from the file system once you fix the error in the artifact. If an artifact fails during the process of creating it via the management console, the artifact can be deleted via the management console and the *.back file that is created will be deleted automatically.
| Info | ||
|---|---|---|
| ||
If you upload an erroneous artifact through a CAR file, a *.back file will not be created even if the deployment fails. |
...
Transports-Related Questions
...
This exception occurs when the <ESB_HOME>/repository/conf/axis2/axis2.xml file does not define any builders and/or formatters that can read the content type of the request received by the ESB. Update the axis2.xml file with a message builder and formatter which that can be used to read the content type of the relevant request in order to overcome this issue. See Configuring Message Relay for instructions on how to configure a message builder and a formatter as required. See Working with Message Builders and Formatters for Formatters for further information on how to use builders and formatters.
...