9.3 Messages from KDJR10000 to KDJR19999 : Messages

KDJR11001-W

A message will be resend. (SequenceID = aa....aa, MessageNumber = bb....bb, count = cc....cc, cause=dd....dd)

aa....aa: Sequence ID

bb....bb: Message number

cc....cc: Message resending count

dd....dd: Cause of resending

Description: The message is resend by the WS-RM functionality.
Action: Nothing in particular.For details on the cause of resending the message, reference the display contents of the cause.

KDJR11103-W

Unable to terminate RM sequence normally due to an unexpected exception.

Description

An attempt was made to invoke the close method to terminate the sequence in the client, but an error occurred. The sequence is terminated forcibly. The possible causes of the error are as follows:

When a sequence close message or a sequence termination message request is sent to the service, the service returns an invalid response.
When a sequence close message or a sequence termination message request is sent to the service, the connection is disconnected.
The sequence has expired.

Action

The addition processing need not be performed in the client. Review, and if necessary revise, the connection timeout value or read timeout value of the client and the sequence validity period, and then if the service returns an invalid response, contact the service.

KDJR11108-W

Response for the acknowledgement request is null.

Description

A request for Ack message has been sent at the background by the client; however, there is no response for the Ack message from the service side.

Initial message processing takes time. There are cases whereby the Ack message is not returned from the service side if the sending and receiving of the Ack message is performed at the background during the initial message processing.

Action

Contact the service for the cause.

KDJR11117-W

The sequence identifier in the terminate sequence response message aa....aa does not correspond to the terminating outbound sequence identifier bb....bb.

aa....aa: Received sequence ID

bb....bb: Sent sequence ID

Description: When the close method is invoked for terminating the sequence at the client side and when the request for terminating sequence message is sent at the service side, the sequence ID sent by the request and the sequence ID of the response returned by the service is different. The sequence is terminated forcibly.
Action: No additional processing is required at the client side. Contact the service for the cause.

KDJR11119-W

The sequence identifier in the close sequence response message aa....aa does not correspond to the closing outbound sequence identifier bb....bb.

aa....aa: Received sequence ID

bb....bb: Sent sequence ID

Description: When the close method is invoked for terminating the sequence at the client side and when the request for closing the sequence message is sent at the service side, the sequence ID sent by the request and the sequence ID of the response returned by the service is different. The sequence is terminated forcibly.
Action: No additional processing is required at the client side. Contact the service for the cause.

KDJR11127-W

An unexpected exception occurred while sending acknowledgement request.

Description: Received an invalid Ack message.
Action: Contact the message sender for the cause.

KDJR16017-W

The WS-RM property contains an invalid value. The default value will be used. (key = aa....aa, value = bb....bb, default = cc....cc)

aa....aa: Property name

bb....bb: Specified value

cc....cc: Applicable default value

Description: A value that is out of range is specified in the settings of the WS-RM 1.2 functionality of WSDL. Therefore, the default value is used.
Action: Check and, if necessary, revise the settings as and when required.

KDJR19999-W

An warning occurred during WS-RM execution. (detail=aa....aa)

aa....aa: Detailed message

Description: A minor error occurred during the execution of the WS-RM functionality.
Action: Check the detailed message, and determine the cause as and when required.