|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 6338 | minor | always | 04-03-20 11:03 | 04-24-20 14:29 | |
|
|
|||||
| Reporter: | nam | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.64 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.65 | ||
|
|
|||||
| 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) |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |