|
BEA-282000
|
Error: Unsupported class version version. Expected a value between min and max inclusive.
|
Description
| The version version is not between the expected versions min and max. This is an unexpected failure.
|
|
Cause
| While attempting to interoperate between different releases or service packs an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If version is larger than min then it is possible an attempt was made to access a newer version than the current version. Otherwise a possible attempt has been made to interoperate with an unsupported older version.
|
|
Action
| Make sure the versions of BEA products that are interoperating are supported. If the versions should be supported, contact BEA Systems, Inc. support
|
|
|
BEA-282001
|
Info: The messaging kernel name is beginning recovery of its persistent state
|
Description
| This message is logged when the messaging kernel begins recovering persistent messages. The messaging kernel is used by JMS and by the store-and-forward feature.
|
|
Cause
| Normal operation.
|
|
Action
| No action required.
|
|
|
BEA-282002
|
Info: The messaging kernel name has recovered numMessages persistent messages
|
Description
| This message is logged when the messaging kernel finished recovering persistent messages. The messaging kernel is used by JMS and by the store-and-forward agent.
|
|
Cause
| Normal operation.
|
|
Action
| No action required.
|
|
|
BEA-282003
|
Info: The messaging kernel name will use up to size bytes of memory before paging begins
|
Description
| This message is logged when the messaging kernel determines how many bytes it will use for paging. This parameter is controlled by the "MessageBufferSize" parameter on the JMSServerMBean or on the SAFAgentMBean. The messaging kernel is used by JMS and by the store-and-forward agent.
|
|
Cause
| Normal operation.
|
|
Action
| No action required.
|
|
|
BEA-282004
|
Error: Message redirection has failed in a non-recoverable way for the messaging kernel name. Restart the server in order to re-start message redirection.
|
Description
| In the event of a failure of the persistent store, redirection of messages by the messaging kernel may stop. In order to maintain data integrity, it is necessary to restart the WLS server so that it can determine what happened before the failure. This affects messages that expired or reached their maximum redelivery limit. The messaging kernel is used by JMS and by the store-and-forward agent.
|
|
Cause
| See the previous error messages, which should explain the cause.
|
|
Action
| Restart the WLS server.
|
|
|
BEA-282005
|
Warning: An error occurred while redirecting a message for the messaging kernel name: msg
|
Description
| There was an error while redirecting a message that has expired or reached its redelivery limit. The messaging kernel may recover from this error, or it may log another error message if it cannot.
|
|
Cause
| See attached detail message
|
|
Action
| No action required
|
|
|
BEA-282006
|
Warning: An error occurred while deleting an expired message for the messaging kernel name: msg
|
Description
| There was an error while deleting a message that has expired. The messaging kernel may recover from this error, or it may log another error message if it cannot.
|
|
Cause
| See attached detail message
|
|
Action
| No action required
|
|
|
BEA-282007
|
Error: An error occurred in the transaction prepare phase of a message send operation for the messaging kernel name
|
Description
| The transaction could not be prepared because of an error. The transaction will be rolled back.
|
|
Cause
| See attached stack trace
|
|
Action
| No action required
|
|
|
BEA-282008
|
Error: A message send transaction for the messaging kernel name could not be committed because the kernel has been shut down
|
Description
| The kernel was shut down, or the destination was undeployed or deactivated before the transaction was committed. The transaction will roll back.
|
|
Cause
| Shutting down a server or removing a destination while a transaction was in progress.
|
|
Action
| No action required
|
|
|
BEA-282009
|
Error: A message receive transaction for the messaging kernel name could not be committed because the kernel has been shut down
|
Description
| The kernel was shut down, or the destination was undeployed or deactivated before the transaction was committed. The transaction will roll back.
|
|
Cause
| Shutting down a server or removing a destination while a transaction was in progress.
|
|
Action
| No action required
|
|
|
BEA-282010
|
Error: A sequence number update transaction for the messaging kernel name could not be committed because the kernel has been shut down
|
Description
| The kernel was shut down, or the destination was undeployed or deactivated before the transaction was committed. The transaction will roll back.
|
|
Cause
| Shutting down a server or removing a destination while a transaction was in progress.
|
|
Action
| No action required
|
|
|
BEA-282011
|
Warning: There was an error making a message visible after a delivery delay: error
|
Description
| There was an error making a message visible after a delivery delay
|
|
Cause
| Most likely, a transient I/O error occurred.
|
|
Action
| Consider restarting the server if the error persists. The message will not be lost.
|
|
|
BEA-282012
|
Warning: There was a failure while performing paging I/O
|
Description
| There was a failure while performing paging I/O
|
|
Cause
| Either a transient I/O error occurred or the server did not have enough memory to complete the paging I/O request.
|
|
Action
| Consider restarting the server if the error persists.
|
|
