Breadcrumb(); > Message Index (by Number) (by Subsystem) > WorkManager Subsystem Messages

WorkManager Subsystem Messages

The WorkManager1.0 catalog contains messages in the range BEA002900 - BEA002999. Messages in this catalog are part of the weblogic.work Internationalization package and the weblogic.work Localization package. BEA-002900 Info: Initializing self-tuning thread pool Description Initializing self-tuning thread pool and creating internal work managers Cause server is starting up Action no action needed BEA-002901 Info: Creating WorkManager "name" for module "module" and application "app" Description Creating app WorkManager for application module Cause application is getting initialized Action no action needed BEA-002902 Info: Creating execute queue "name". Description Creating null WorkManager for application name Cause application is getting initialized Action no action needed BEA-002903 Info: Creating WorkManager from "name" WorkManagerMBean for application "app" 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-002904(retired) Notice: Adding incr threads to the common thread pool. Its thread count now is total Description Adding incr threads to the thread pool to prevent deadlocks or increase performance Cause Server needs to increase threads to improve performance or prevent deadlocks Action no action needed as the server auto tunes BEA-002905 Notice: removing incr threads from the thread pool Description removing incr threads from the thread pool as they are no longer needed Cause Server has realized that some threads are not needed to handle the present load Action no action needed as the server auto tunes BEA-002906(retired) Debug: name has been busy for "elapsedTime" seconds working on the request "currentWork", which is more than the max hog time of "hogThreshold" seconds. Description It was found that a request was using a thread for much more time than other threads that completed Cause Either the requests execution has slowed or the thread is hung. Action No action required. The server will backfill this thread with a new one. Configure StuckThreadMaxTime attribute to detect hung threads BEA-002907(retired) Debug: name has become available again to take new requests Description A previously hogging thread has become free to take new requests Cause A previously hogging thread has become free to take new requests Action No action necessary BEA-002908 Critical: Unable to create runtime mbean for work manager name. th Description Fatal error while creating the runtime mbeans Cause Fatal error while creating the runtime mbeans Action Please contact support with the server logs. BEA-002909 Debug: name Description debug Cause debug Action no action BEA-002910(retired) Info: Allocating incr dedicated threads to wm WorkManager. WorkManager wm now has total threads. Description Allocating incr dedicated threads to wm WorkManager. Total thread count now is total Cause Server is allocating dedicated threads to a high throughput WorkManager as an optimization Action no action needed as the server auto tunes BEA-002911 Critical: WorkManager wm failed to schedule a request due to th Description WorkManager wm failed to schedule a request due to th Cause WorkManager failed to schedule a request due to a fatal failure Action This is a critical failure. Report to BEA support with log BEA-002912 Info: OverloadManager wm rejected request as current length curLength exceeds max capacity of capacity Description OverloadManager wm rejected request as current length curLength exceeds max capacity of capacity Cause A request is rejected as overload capacity is reached or exceeded. Action No action required BEA-002913 Info: WorkManager wm rejected request as the server is low on memory Description WorkManager wm rejected request as the server is low on memory Cause A request is rejected as server is low on memory. Action No action required BEA-002914 Error: Shutdown callback invocation failed with:\nth Description Invocation of the app container shutdown callback threw an exception Cause Internal error in app shutdown Action Please report to support with logs BEA-002915(retired) 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. BEA-002935 Warning: request-class-name reference within ContextCase element for entry entry with value: value ;cannot be resolved for WorkManager. Description request-class-name reference within ContextCase element for entry entry with value: value ;cannot be resolved for WorkManager.