The WseeRm1.0 catalog contains messages in the range
BEA-224000 - BEA-224499. Messages in this catalog are part of the
weblogic.wsee
Internationalization package and the weblogic.wsee
Localization package.
BEA-224000
|
Error: Conversation seqId was specified/retained directly by the client, but has expired or has been terminated or destroyed. Please use a new service or dispatch instance.
Description
| Conversation seqId was specified/retained directly by the client, but has expired or has been terminated or destroyed. Please use a new service or dispatch instance. |
Cause
| A service or Dispatch instance was reused after a reliable sequence was created and completed on it. You should use a new service/Dispatch instance to avoid using the same saved sequence ID for a new sequence. |
Action
| Use a new service/Dispatch instance before invoking more reliable operations after a prior sequence of invocations. |
|
BEA-224001
|
Error: SourceSequence not ready to send sequence messages. Retry after CreateSequenceResponse and Sequence.getState() == CREATED.
Description
| SourceSequence not ready to send sequence messages. Retry after CreateSequenceResponse and Sequence.getState() == CREATED. |
Cause
| An attempt was made to use or modify a sequence from the RM source side before that sequence has completed the RM handshake process (when the CreateSequenceResponse message arrives and is processed). |
Action
| Retry the operation after the RM sequence has been properly initialized, and the CreateSequenceResponse message for the sequence has been processed. |
|
BEA-224002
|
Error: Protocol exception, detected a response to a response on the client side. Since there is no protocol-specific back-channel on a client-side response, we attempted to send the secondary response via a new outbound connection, and this failed. This response cannot be delivered. Response was: msg Send error was: error
Description
| Protocol exception, detected a response to a response on the client side. Since there is no protocol-specific back-channel on a client-side response, we attempted to send the secondary response via a new outbound connection, and this failed. This response cannot be delivered. Response was: msg |
Cause
| Runtime code attempted to send a response after processing a response on the client-side protocol-specific back-channel. The back-channel can only support one message delivery, so we attempted, and failed, to send this secondary response via a new outbound connection. Because of this failure, the secondary response cannot be delivered. |
Action
| Contact technical support. |
|
BEA-224003
|
Error: Client-side couldnt determine if we have RM policy on target service/port
Description
| Client-side couldnt determine if we have RM policy on target service/port |
Cause
| Runtime code on the client or sending side of an RM sequence couldnt retrieve a policy. |
Action
| Contact technical support. |
|
BEA-224004
|
Error: Server-side couldnt determine if we have RM policy on target service/port
Description
| Server-side couldnt determine if we have RM policy on target service/port |
Cause
| Runtime code on the service or receiving side of an RM sequence couldnt retrieve a policy. |
Action
| Contact technical support. |
|
BEA-224005
|
Error: No header header found on CreateSequenceResponse. Cannot identify sequence to handle this message
Description
| No header header found on CreateSequenceResponse. Cannot identify sequence to handle this message |
Cause
| A protocol violation has occurred, and RM cannot identify the message ID of the CreateSequence message by looking at the CreateSequenceResponse message. |
Action
| Contact the vendor that supplied the RM destination implementation (receiver of CreateSequence message) and indicate a protocol violation. |
|
BEA-224006
|
Error: Got CreateSequenceResponse/Accept when no offer was made on sequence with destination-side ID: destSeqId
Description
| Got CreateSequenceResponse/Accept when no offer was made on sequence with destination-side ID: destSeqId |
Cause
| A CreateSequenceResponse message in response to a CreateSequence message that does not contain an Offer element must not itself contain an Accept element. |
Action
| Contact the vendor that supplied the RM destination implementation (receiver of CreateSequence message) and indicate a protocol violation. |
|
BEA-224007
|
Error: Null sequence ID specified/found
Description
| Null sequence ID specified/found |
Cause
| A null value was passed to some internal method taking a sequence identifier where that method does not accept null values. |
Action
| Contact technical support. |
|
BEA-224008
|
Error: Null message ID specified/found
Description
| Null message ID specified/found |
Cause
| A null value was passed to some internal method taking a message identifier where that method does not accept null values. |
Action
| Contact technical support. |
|
BEA-224009
|
Error: Attempt to add a sequence that is null or has already been added: seqId
Description
| Attempt to add a sequence that is null or has already been added: seqId |
Cause
| A null sequence (or a sequence that already has been added to the list of valid sequences) has been detected. |
Action
| Contact technical support. |
|
BEA-224010
|
Error: Attempt to update a sequence that is null or has not been added via addSequence: seqId
Description
| Attempt to update a sequence that is null or has not been added via addSequence: seqId |
Cause
| A null sequence (or a sequence that never has been added to the list of valid sequences) has been referenced in an update operation. |
Action
| Contact technical support. |
|
BEA-224011
|
Error: Cannot accept/process this request, and can't assume async response is forthcoming because ReplyTo is anonymous. Cannot continue.
Description
| Cannot accept/process this request, and can't assume async response is forthcoming because ReplyTo is anonymous. Cannot continue. |
Cause
| An incoming request to the RM destination has failed a quality-of-service check (e.g. duplicate or out-of-order) and there is no ReplyTo address to which we can send a fault. Thus, we'll completely abort the processing of this request in order to indicate the failure to the sender. |
Action
| Send requests according to the quality-of-service requirements of the service. |
|
BEA-224012
|
Error: Could not find sequence seqId on side side
Description
| Could not find sequence seqId on side side |
Cause
| No sequence with the given identifier exists on the given side of the RM message exchange. |
Action
| Specify a different sequence identifier in the protocol message or contact technical support. |
|
BEA-224013
|
Error: WsrmClient feature not enabled on this port/stub
Description
| WsrmClient feature not enabled on this port/stub |
Cause
| A Port/Dispatch instance was used as if it referenced a reliable service, but the service is in fact not reliable (no WS-RM policy attached to it). |
Action
| Make the target service reliable (by attaching WS-RM policy to it) or pick a different target service. |
|
BEA-224014
|
Error: Cannot call method on a sequence that has not yet been fully initialized (no destination sequence ID or CreateSequenceResponse received yet). Source sequence ID: sourceSeqId
Description
| Cannot call method on a sequence that has not yet been fully initialized (no destination sequence ID or CreateSequenceResponse received yet). Source sequence ID: sourceSeqId |
Cause
| Youve called a WsrmClient method to interact with the sequence before calling (or getting a true result) from WsrmClient.isInitialized(). |
Action
| Please wait until you have completed a synchronous reliable invocation or have gotten true from WsrmClient.isInitialized before calling such a method. |
|
BEA-224015
|
Error: Got a message using the wrong WS-RM version for action action. Expected expected but got actual.
Description
| Got a message using the wrong WS-RM version for action action. Expected expected but got actual. |
Cause
| An RM sequence was negotiated using one version of the RM protocol, and a subsequent message was received indicating a different version. |
Action
| Make sure all messages related to a given sequence use the same RM protocol version. |
|
BEA-224016
|
Error: An unexpected error occurred: msg
Description
| An unexpected exception has occurred. |
Cause
| An unexpected exception has occurred. |
Action
| Contact technical support. |
|
BEA-224017
|
Error: ClientIdentityFeature not enabled or clientId not specified on this port/stub. This is required for WS-RM to track requests and responses for this client.
Description
| ClientIdentityFeature not enabled or clientId not specified on a port/stub that has requested/implied async/persistent WS-RM mode. ClientIdentityFeature is required for WS-RM to track requests and responses for this client. |
Cause
| A Port/Dispatch instance was created without specifying an 'identity' via the ClientIdentityFeature JAX-WS feature when RM requires such an identity. |
Action
| Add a ClientIdentityFeature when creating your Port/Dispatch stub instance, and make sure that feature has its clientId field set to a unique, repeatable client ID. |
|
BEA-224018
|
Warning: No ReliabilityErrorListener provided via WsrmClient for a Port/Dispatch instance portId. The sequence started on the Port/Dispatch instance encountered the following error: error
Description
| No WsrmReliabilityErrorListener provided via WsrmClient for a Port/Dispatch instance portId. The sequence started on the Port/Dispatch instance encountered the following error: error |
Cause
| A Port/Dispatch instance was created without specifying an error listener via the WsrmClient interface. Subsequently, a WS-RM sequence being managed on that Port/Dispatch instance encountered an error and could not notify the client of this error directly. |
Action
| Add a ReliabilityErrorListener on the Port/Dispatch instance by calling WsrmClient.setErrorListener(). |
|