The BPEL Interpreter catalog contains messages in the range
BEA2031500 - BEA2031599. Messages in this catalog are part of the
com.bea.bpel.interpreter.exception.messages Internationalization package and the
com.bea.bpel.interpreter.exception.messages Localization package.
|
BEA-2031500
|
Error: Unable to determine which inbound messaging activity to deliver message to. The message matches multiple inbound messaging activities with the same operation 'operation' but different correlation sets.
|
Description
| The inbound message has been rejected because it matches more than 1 enabled inbound messaging activity with the same partner link and operation but different correlation sets. It cannot be determined which inbound messaging activity the message should be delivered to. This is potentially due to a timing issue. See WS-BPEL 2.0, section 10.4 for more detail. |
|
|
BEA-2031501
|
Error: The completion condition for counter 'counter' can never be true.
|
Description
| The counter will never complete. See WS-BPEL 2.0, section 11.7 for more detail. |
|
Action
| Revise the counter so that it can complete. |
|
|
BEA-2031502
|
Error: An inbound messaging activity is already enabled for operation 'operation'.
|
Description
| A receive activity was processed that, if successfully enabled, would have resulted in more than 1 receive waiting for the same message. If more than 1 receive is enabled for the same partner link, operation and correlation set it would result in multiple targets for inbound messages. This is potentially due to a timing issue. See WS-BPEL 2.0, section 10.4 for more detail. |
|
|
BEA-2031503
|
Error: An inbound messaging activity is already enabled for operation 'operation'.
|
Description
| It is illegal to have more than 1 inbound messaging activity enabled with the same partner link, operation and message exchange token. See WS-BPEL 2.0, section 10.4.1 for more detail. |
|
|
BEA-2031504
|
Error: The counter 'counter' defines 'remaining' iterations but the completion condition requires 'required', so it will never complete.
|
Description
| The counter has processed to the point where it will never complete (For example, the counter may require 8 more iterations but there will only be 6). See WS-BPEL 2.0, section 11.7 for more detail. |
|
|
BEA-2031505
|
Error: The join condition has evaluated to false.
|
Description
| A join condition of a branch of a flow has evaluated to false. See WS-BPEL 2.0, section 11.6.2 for more detail. |
|
|
BEA-2031506
|
Error: The expression evaluated to a type of 'requiredType' but a type of 'actualType' was expected.
|
Description
| An expression evaluated to an incompatible type for assignment. See WS-BPEL 2.0, sections 8.4.2 and 8.4.3 for more detail. |
|
|
BEA-2031507
|
Error: The message for operation 'operation' has not been replied to.
|
Description
| The partner link for an outstanding message exchange has just gone out of scope so the exchange will never be replied to. See WS-BPEL 2.0, section 10.4.1 for more detail. |
|
|
BEA-2031508
|
Error: Unknown message exchange for operation 'operation'.
|
Description
| An attempt was made to reply to a non-existent message exchange. See WS-BPEL 2.0, section 10.4.1 for more detail. |
|
|
BEA-2031509
|
Error: Executing an expression caused an unhandled fault: exceptionMessage.
|
Description
| An unexpected error occurred while executing an expression. The exception message should provide details of the cause. |
|
Action
| Correct the error specified in the exception message. |
|
|
BEA-2031510
|
Error: The partner role 'partnerLink' is uninitialized.
|
Description
| An attempt was made to access a partner link before it was initialized. This should never happen (it should be caught by validation during deployment). |
|
Action
| Contact Technical Support. |
|
|
BEA-2031511
|
Error: The source for doXslTransform has noItems items, when exactly 1 is required.
|
Description
| The source for the doXslTransform function contains an XML document with other than 1 root node. |
|
Action
| Ensure that the source contains only 1 root node. |
|
|
BEA-2031512
|
Error: The source for doXslTransform is of unsupported type 'actualType'. Supported types are requireTypes.
|
Description
| The source for doXslTransform is an unsupported type. This should never happen. |
|
Action
| Contact Technical Support. |
|
|
BEA-2031513
|
Error: The XSL stylesheet 'stylesheetURI' was not found.
|
Description
| The XSL stylesheet could not be found on the class loader hierarchy. |
|
Action
| Ensure that the stylesheet can be found on the class loader hierarchy. |
|
|
BEA-2031514
|
Error: The message for process 'process' and operation 'operation' is rejected because a previous message for the same is waiting to be processed (possible out of order).
|
Description
| A message was received by the process for a partner link, operation and correlation sets when one is already waiting to be processed. One possible reason for this is that the messages were received out of order. |
|
Action
| Resend the message. |
|
|
BEA-2031515
|
Error: The element 'fromElement'is not substitutable for the element 'toElement'.
|
Description
| The EII selected by the from-spec is not substitutable for the EII selected by the to-spec. If the from-spec and the to-spec select EIIs with different element names, then the from-spec element must belong to the substitutionGroup of the to-spec element (as determined by the schema definitions for the elements). |
|
|
BEA-2031516
|
Info: Cannot find process instance instanceID. The process instance has probably been terminated.
|
Description
| A process instance cound not be found. This generally happens when a ForEach is used with a completion condition. |
|
Action
| If this is not expected, contact Technical Support. |
|
|
BEA-2031517
|
Error: Link status for 'link' is being referenced before is has been set.
|
Description
| The link is being referenced before it has been set. This is generally a problem with the process definition but it could be a timing issue. |
|
Action
| Modify the process to ensure that the link is always set before it is referenced. |
|
|
BEA-2031518
|
Error: Variable 'variable' is being referenced before it has been initialized with a value.
|
Description
| The variable is being referenced before it has been initialized. This is generally a problem with the process definition but it could be a timing issue. |
|
Action
| Modify the process to ensure that the variable is always initialized before it is referenced. |
|
|
BEA-2031519
|
Error: Inbound message 'messageType' cannot initialize variable because it is incomplete.
|
Description
| The inbound message is missing at least one part. |
|
Action
| Ensure that the message contains all the parts defined on the message type for the input message of the operation. |
|
|
BEA-2031520
|
Error: Outbound message 'messageType' cannot be sent because it is incomplete.
|
Description
| The outbound message is missing at least one part. |
|
Action
| Ensure that the message contains all the parts defined on the message type for the output message of the operation. |
|
|
BEA-2031521
|
Error: Expression 'expression' returned noItems items when exactly 1 is required.
|
Description
| Expressions (particularly those used in Copy) should return a single item. If the expression evaluates to 0 or more than 1 item it is an exception. |
|
Action
| Ensure that the expression selects a single item. |
|
|
BEA-2031522
|
Error: Nested transactions are not supported.
|
Description
| An attempt was made to start a new transaction when one was already active. This is not supported. This should never happen (because transactions cannot be explicitly started currently). |
|
Action
| Contact Technical Support. |
|