Breadcrumb(); > Message Index (by Number) (by Subsystem) > Kernel Subsystem Messages
![]()
Kernel Subsystem Messages
The Kernel1.0 catalog contains messages in the range BEA800 - BEA899. Messages in this catalog are part of the
weblogic.kernel Internationalization package and the
weblogic.kernel Localization package.
Critical: name stopped.
Description
The server name was shut down unintentionally. Cause
A ThreadDeath exception caused a shut down. Action
No action required. Info: ExecuteRequest: name cancelled.
Description
This message indicates that an in-flight request was cancelled. Cause
This only happens when WebLogic Server is used in conjunction with an IDE, which uses JVMDI to cancel in-flight requests. If this occurs in normal operation, please contact BEA support. Action
No action required. Error: ExecuteRequest failed\n t.
Description
Server t was shutdown unintentionally. Cause
An execute request threw an exception that was not handled. Action
Please contact BEA support. Error: The Class cls has a setter method for attribute attribute which does not have a constructor that could be initialized from a String value of value.
Description
No constructor found for the attribute type. Cause
No constructor found for the declared attribute type that takes a String argument. Action
Provide a constructor with a String argument. Error: The Class Class attribute attribute could not be initialized with value value. The exception message is exception.
Description
There was an exception thrown when the setter method was called for the attribute. Cause
See the exception stack trace detail. Action
Take appropriate action based on the error message. Notice: Self-tuning thread pool is disabled. An execute queue will be created for each WorkManager definition.
Description
Self-tuning thread pool is disabled. An execute queue will be created for each WorkManager definition. Cause
Server is starting up Action
no action needed Critical: A request belonging to work manager workManagerName is being scheduled for execution again after it has completed. This indicates a fatal thread scheduler error.
Description
The scheduler is executing a work entry again after previously executing it Cause
WorkManager bug Action
report to support with the server logs Info: WorkManager wmName has reached its capacity. It is rejecting from thread threadName. The message is msg. Throwable is t.
Description
Queue capacity reached. Cause
WorkManager bug Action
No action required
![]()