WorkManager Subsystem Messages

The WorkManager1.0 catalog contains messages in the range
BEA-002900 - BEA-002999. Messages in this catalog are part of the
weblogic.work
Internationalization package and the weblogic.work Localization package.

Info: Thread priority of request class name changed from current to new

Description

Thread priority of request class name changed from current to new

Cause

Thread priority changed for this request class

Action

no action required

BEA-002916

Info: Request belonging to WorkManager wmName, application appName is rejected as the WorkManager is shutdown

Description

Request belonging to WorkManager wmName, application appName is rejected as the WorkManager is shutdown

Cause

Request is refused entry as the work manager is shutdown

Action

no action required

BEA-002917

Info: Enqueued Request belonging to WorkManager wmName, application appName is cancelled as the WorkManager is shutdown

Description

Enqueued Request belonging to WorkManager wmName, application appName is cancelled as the WorkManager is shutdown

Cause

Request is refused as the work manager is shutdown

Action

no action required

BEA-002918

Warning: Server detected execute queue(s) in self-tuning mode. Execute queues will not be self-tuned. They retain their behaviour from earlier releases. Consider using WorkManagers to take advantage of self-tuning

Description

Server detected execute queue(s) in self-tuning mode. Execute queues will not be self-tuned. They retain their behaviour from earlier releases. Consider using WorkManagers to take advantage of self-tuning

Cause

Execute queues detected in self-tuning server

Action

Consider removing the execute queues. The server automatically adjusts the thread pool size for optimal performance. WorkManagers can be used to change the default behaviour where needed.

BEA-002919

Warning: Unable to find a WorkManager with name workManagerName. Dispatch policy workManagerName will map to the default WorkManager for the application applicationName

Description

Unable to find a WorkManager with name workManagerName. Dispatch policy workManagerName will map to the default WorkManager for the application applicationName

Cause

There is no WorkManager with the given name

Action

This could mean a configuration error. Check the dispatch-policy and ensure that it matches the name of a WorkManager defined either within the same application or one defined globally.

BEA-002920

Info: An instance of the mSA WorkManager

BEA-002921

Info: The name of the WorkManager

BEA-002922

Info: The number of waiting requests in the queue

BEA-002923

Info: The number of requests that have been processed

BEA-002924

Info: An instance of the MinThreadsConstraint for a particular WorkManager

BEA-002925

Info: Completed request count

BEA-002926

Info: Pending requests that are waiting for an available thread.

BEA-002927

Info: Number of requests that are currently executing.

BEA-002928

Info: Number of requests executed out of turn to satisfy this constraint.

BEA-002929

Info: Number of requests that must be executed to satisfy the constraint.

BEA-002930

Info: The max time a request had to wait for a thread. Only requests whose execution is needed to satisfy the constraint are considered.

BEA-002931

Info: Number of requests that must be executed to satisfy the constraint.

BEA-002932

Info: An instance of the MaxThreadsConstraint for a particular WorkManager

BEA-002933

Info: Number of requests that are currently executing.

BEA-002934

Info: Number of requests that are denied a thread for execution because the constraint is exceeded.