Errors Sending Responses
When messages come into Duplicate Detect, a response is returned to the client if there is a JMS reply destination set in the original JMS message. JMS destinations represent a queue in a messaging system such as IBM® WebSphere® MQ.
Responses contain information about what Duplicate
Detect found when processing the original
message. Duplicate
Detect sends the response to the JMS reply destination. If the response message
cannot be sent to the reply destination, the message is written to the file system for later processing by the
administrator. Some reasons a response cannot be returned may be due to the queue being full or the
communication link not being available.
Note: The message file in the file system is not a text file that can
be viewed in a text editor.
When an error is received, the file system location used for writing
the response messages is determined by the following configuration
properties:
- izh.filesystem.root – the root directory location
- izh.filesystem.root.error – the name of the error directory located under the root
For a further description of these properties, see Configuration Properties.
If the directories do not exist, Duplicate Detect attempts to create them.
The file naming convention is
response type.namespace.group id.uow name.client id.status.system
time.extension
| Filename Part | Values |
|---|---|
| response type | The message response type, for example dupCheck, dupRemove, dupDelUow, dupResponse, dupReviewed and dupRemoveResp |
| namespace | The namespace for the message, such as DUP_PAYMENT. |
| group ID | The group ID for the message |
| uow name | The unit of work for the message |
| client ID | The client ID for the message |
| status | The status of the message for example, success, error, complete, rerun. |
| system time | The timestamp in milliseconds |
| extension | The value is msg |
If the value of the filename part is not available, the value none is used.