Mantis - Resin
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6126 major always 01-09-18 00:45 01-15-18 14:07
Reporter: cyflhn Platform:  
Assigned To: ferg OS:  
Priority: normal OS Version:  
Status: closed Product Version: 3.1.13  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.1.17  
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
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:

There are no notes attached to this issue.