0006338: add logging for when ThreadPool2 taskQueue is full

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0006338

[Resin]

minor

always

04-03-20 11:03

04-24-20 14:29

Reporter

nam

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

4.0.64

Summary

0006338: add logging for when ThreadPool2 taskQueue is full

Description

(rep by Yoo)

Needs more detailed logging to help debug the issue:

    1. time of event
    2. class of Runnable
    3. size of queue
    4. peek of other Runnables in the queue (optional)
    5. execution stats (optional)
    7. triggering of health system events just like for priority tasks (optional)

> Phenomenon
> -. In the jvm-web.log file, the following error was found.
> ThreadPool: scheduleImpl TASK_FULL
> ThreadPool: scheduleImpl TASK_FULL
> ThreadPool: scheduleImpl TASK_FULL
> ...
> -. Service connection was not smooth after an error occurred.
> -. Incoming requests responded quickly.(in the access-web.log)

Additional Information

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
04-03-20 11:03	nam	New Issue
04-03-20 11:10	nam	Description Updated
04-15-20 02:45	nam	Description Updated
04-24-20 14:29	ferg	Assigned To	=> ferg
04-24-20 14:29	ferg	Status	new => closed
04-24-20 14:29	ferg	Resolution	open => fixed
04-24-20 14:29	ferg	Fixed in Version	=> 4.0.65

Mantis 1.0.0rc3[^]

29 total queries executed.
25 unique queries executed.