|
BEA-000800
|
Critical: name stopped.
|
Description
| The server name was shut down unintentionally. |
|
Cause
| A ThreadDeath exception caused a shut down. |
|
Action
| No action required. |
|
|
BEA-000801
|
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. |
|
|
BEA-000802
|
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. |
|
|
BEA-000803
|
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. |
|
|
BEA-000804
|
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. |
|
|
BEA-000805
|
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 |
|
|
BEA-000806(retired)
|
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 |
|
|
BEA-000807
|
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 |
|
|
BEA-000808
|
Warning: Executing thread is a non WLS thread. Please modify the application to use the Commonj WorkManager API.
|
Description
| Set the System property "weblogic.kernel.debug.JavaThreadAccess" to true to see all java.lang.Thread threads that are being spawned by the application. System property should only be turned on in development environments. |
|
Cause
| Use of an application spawned Java thread instead of the Commonj WorkManager API. |
|
Action
| Modify the application to use the Commonj WorkManager API's. |
|
|
BEA-000809
|
Debug: Executing thread details is a non WLS thread. Please modify the application to use the Commonj WorkManager API.
|
Description
| Commonj WorkManager APIs provides app/server lifecycle integration - Consider modifying the application to use the provided APIs. |
|
Cause
| Use of an application spawned Java thread instead of the Commonj WorkManager API. |
|
Action
| Modify the application to use the Commonj WorkManager APIs. |
|
