-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The warning message "AS-CONCURRENT-00001" is written to server.log many times. #21561
Comments
@glassfishrobot Commented |
@glassfishrobot Commented This pach changes Managed(Scheduled)ExecutorService's behavior so that the "AS-CONCURRENT-00001" message is written only once for each task when the task processing time exceeds the "hung-after-seconds". This patch requires another patch for "cu-javaee" project.
If you want the previous behavior (before patch), set Managed(Scheduled)ExecutorService's additional property "log-hung-thread-policy" to "repeat".
|
@glassfishrobot Commented |
@glassfishrobot Commented |
|
This issue has been marked as inactive and old and will be closed in 7 days if there is no further activity. If you want the issue to remain open please add a comment |
TODO: Cherrypick to 6.2.4 too |
The commit for 6.2.4 was: 0b114d5 ;) |
User application submits a task to ManagedExecutorService or ManagedScheduledExecutorService.
Once the task processing time exceeds the "hung-after-seconds" value of ManagedExecutorService or ManagedScheduledExecutorService, a warning message "AS-CONCURRENT-00001" is written to server.log file repeatedly every minute until the task finishes.
When a lot of tasks do hang, a large amount of same "AS-CONCURRENT-00001" messages are written to server.log file.
In that case, there is a risk that other important messages are missed or lost by rotating the server.log file.
Therefore, I hope to change behavior so that the "AS-CONCURRENT-00001" message is written only once for each task when the task processing time exceeds the "hung-after-seconds".
I also hope to maintain compatibility by adding an additional property to ManagedExecutorService and ManagedScheduledExecutorService, so user can specify the behavior when the task processing time exceeds the "hung-after-seconds".
The "hung-after-seconds" value of ManagedExecutorService can be specified by the command below:
Affected Versions
[4.1]
The text was updated successfully, but these errors were encountered: