| |
Create a SAF Error Handling Policy
Configuration Options Related Tasks Related Topics
Use this page to configure error handling policy properties for SAF imported destinations. Error handling policies define the action to be taken when the SAF service fails to forward messages to a remote destination.
Configuration Options
Name Description Name The name of this error handling configuration.
MBean Attribute:
WebLogicMBean.NameChanges take effect after you redeploy the module or restart the server.
Policy The error handling policy for this SAF error handling resource.
Discard - By default, expired messages are simply removed from the system. The removal is not logged and the message is not redirected to another location.
Log - Removes expired messages and writes an entry to the server log file indicating that the messages were removed from the system. You define the actual information that will be logged in the Log Format field.
Redirect - Moves expired messages from their current location into the Error Destination defined for imported SAF destinations.
Always-Forward - Ignores the SAF Default Time-to-Live value set on the imported destination and the expiration time set on the message, and so forwards the message to a remote destination even after it has expired.
Any change to this parameter affects only incoming messages; stored messages are not affected.
MBean Attribute (Does not apply to application modules) :
SAFErrorHandlingBean.PolicyChanges take effect after you redeploy the module or restart the server.
Log Format Specifies how information is logged when
Message Handling Policyis set toLog.Any change to this parameter affects only incoming messages; stored messages are not affected.
The valid values are:
- %header%
- All JMS header fields are logged.
- %properties%
- All user-defined properties are logged.
- JMSDeliveryTime
- This WebLogic JMS-specific extended header field is logged.
- JMSRedeliveryLimit
- This WebLogic JMS-specific extended header field is logged.
- foo
- Any valid JMS header field or user-defined property is logged.
When specifying multiple values, enter them as a comma-separated list. The
%header%and%properties%values are not case sensitive. For example, you could use"%header%,%properties%"for all the JMS header fields and user properties. However, the enumeration of individual JMS header fields and user-defined properties are case sensitive. To enumerate only individual JMS header fields you could use"%header, name, address, city, state, zip".Note: The
JMSMessageIDfield is always logged and cannot be turned off. Therefore, if the Log Format is not defined (i.e., null) or is defined as an empty string, then the output to the log file contains only theJMSMessageIDof the message.MBean Attribute (Does not apply to application modules) :
SAFErrorHandlingBean.LogFormatChanges take effect after you redeploy the module or restart the server.
Error Destination Specifies the error destination when
Policyis set toRedirect.Any change to this parameter affects only incoming messages; stored messages are not affected.
MBean Attribute (Does not apply to application modules) :
SAFErrorHandlingBean.SAFErrorDestinationChanges take effect after you redeploy the module or restart the server.
|