0006126: Weak alarm can not be handled forever if there is no idle thread pool item

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0006126

[Resin]

major

always

01-09-18 00:45

01-15-18 14:07

Reporter

cyflhn

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

3.1.13

Summary

0006126: Weak alarm can not be handled forever if there is no idle thread pool item

Description

If resin wants to invoke an Alarm, in the class of CoordinatorTask, it will extract an object of Alarm and invoke "ThreadPool.getThreadPool().startPriority(alarm)".(line 654 in Alarm.java). Then look at the file of ThreadPool.java, the method of "startPriority" will invoke the method of "schdule" of which the last paramter is false, which means that if _idleHead is NULL, the method of "schedule" returns, and this alarm will not be added to the queue so that the alarm will not be handler forever. There is a big chance that some alarms such as ConnectionPool will not be handled forever in this situation. Many database connections will not be released. This brings a greate damage to our system. This problem still exists in version of 3.1.14

Additional Information

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
01-09-18 00:45	cyflhn	New Issue
01-15-18 14:07	ferg	Assigned To	=> ferg
01-15-18 14:07	ferg	Status	new => closed
01-15-18 14:07	ferg	Resolution	open => fixed
01-15-18 14:07	ferg	Fixed in Version	=> 3.1.17
01-23-18 20:02	cyflhn	Issue Monitored: cyflhn

Mantis 1.0.0rc3[^]

28 total queries executed.
25 unique queries executed.