0054090: connection leak on Tomcat start if a process is missfired

Description

When there are missfired background processes on Tomcat start, one connection is leaked not being returned to the pool.

Steps To Reproduce

1. Configure the connection pool to use very few connections, ie. 4. (This step is not necessary but it make it easier to see the problem).
2. Schedule a process (ie. alert process) to run every 5 seconds.
3. Stop Tomcat and wait 5 secs.
4. Start Tomcat and wait 30 secs for quartz to start.
  - There will be a missfired instance of the scheduled process (OK)
5. Log in BO and perform some operations (ie. open a couple of windows and refresh grid some times).
  - ERROR: check pg_stat_activity, there is an idle connection whose state_change is at the time Tomcat was started and the query is INSERT INTO AD_Process_Run...
  Configuring the pool to log abandoned connections (db.pool.logAbandoned=true and db.pool.suspectTimeout=10), it will point to ProcessMonitor.triggerMisfired

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to	defect	0054081		closed	Triage Platform Base	Regression: Number of database connection kept open in idle tomcat went up by +10
related to	defect	0054029		closed	AugustoMauch	Connection leak when using scheduling process requests based on process groups

Notes
(0158251) hgbot (developer) 2023-12-15 08:32	Repository: https://gitlab.com/openbravo/product/openbravo [^] Changeset: dda300b5e5a8d9bf67f4d26d2ad05e636ff03458 Author: Asier Lostalé <asier.lostale@openbravo.com> Date: 15-12-2023 07:32:12 URL: https://gitlab.com/openbravo/product/openbravo/-/commit/dda300b5e5a8d9bf67f4d26d2ad05e636ff03458 [^] fixed BUG-54090: connection leak on Tomcat start if a process is missfired ProcessMonitor.triggerMissfired method retrieved a connection from the pool but it never returned it after termination. --- M src/org/openbravo/scheduling/ProcessMonitor.java ---

Issue History
Date Modified	Username	Field	Change
2023-12-11 09:35	alostale	New Issue
2023-12-11 09:35	alostale	Assigned To	=> Triage Platform Base
2023-12-11 09:35	alostale	OBNetwork customer	=> No
2023-12-11 09:35	alostale	Modules	=> Core
2023-12-11 09:35	alostale	Triggers an Emergency Pack	=> No
2023-12-11 09:36	alostale	Relationship added	related to 0054081
2023-12-11 09:36	alostale	Assigned To	Triage Platform Base => alostale
2023-12-11 09:38	alostale	Steps to Reproduce Updated	View Revisions
2023-12-11 09:54	alostale	Steps to Reproduce Updated	View Revisions
2023-12-11 09:58	alostale	Relationship added	related to 0054029
2023-12-15 08:32	hgbot	Resolution	open => fixed
2023-12-15 08:32	hgbot	Status	new => resolved
2023-12-15 08:32	hgbot	Fixed in Version	=> PR24Q1
2023-12-15 08:32	hgbot	Note Added: 0158251
2023-12-20 07:34	alostale	Status	resolved => closed
2023-12-20 07:34	alostale	Fixed in Version	PR24Q1 =>