When using the WS-RM 1.2 functionality, if an application message is not delivered to the destination, the message is automatically resent from RMS for the maximum number of times as set in the WS-RM Policy for resending the application message. If the application message is not delivered even after resending it for the specified number of times, javax.xml.ws.WebServiceException is returned to the client application.

The following are the conditions for resending the messages:

• If a timeout occurs due to no response even after the read timeout value or the connection timeout value set in the JAX-WS Operation definition file or the request context for the client socket is exceeded.
• If the connection with the server is unexpectedly disconnected and no response could be received.
• If an Ack message with the blank Body element is received as a response to the application message or automatically resent application message.
• If HTTP status code 202 is received as a response to the application message or automatically resent application message.
• If the HTTP status code 2012, 300 to 399, 400 to 499, or 500 to 599 is received as a response to the application message that is automatically resent.

When you receive a message that is same as the message received earlier, it is not delivered to the destination and is destroyed at RMD. The application is not invoked.

The following messages are returned to the client, if duplicate messages are received:

• If you receivea request that is duplicating the request for which the response is already returned, contents same as theresponseoncereturnedare returned.
• While processing a request, if the same request is received again, an Ack message with a blank Body element is returned to the client. However, if there is no Ack to return, HTTP status code 202 is returned.