Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #23882 All Revisions ] Back to Issue ]
Summary 0023882: 2 dangling DB connections after Tomcat start
Revision 2015-11-11 11:11 by alostale
Steps To Reproduce * Using pg9 (just to better monitor)
* Ensure there are no scheduled background processes
* Close all browsers and restart Tomcat
* Check connections (select * from pg_stat_activity): 2 connections are opened
* Operate the application for a while. Check the 2 connections that were present at the beginning are still there, the last query executed for each of them and their state change time have not been modified, this means they are not reused.



select state_change, substr(query,0,100) from pg_stat_activity where state = 'idle' order by state_change;
         state_change | substr
-------------------------------+-----------------------------------------------------------------------------------------------------
 2015-10-28 14:52:25.521975+00 | SET extra_float_digits = 3
 2015-10-28 14:52:40.112256+00 | UPDATE AD_SYSTEM_INFO SET SYSTEM_STATUS = $1
 2015-11-11 10:07:02.736565+00 | UPDATE AD_Session SET SESSION_ACTIVE = 'N' WHERE AD_Session.AD_Session_ID =
 2015-11-11 10:09:10.412948+00 | SELECT AD_AVAILABLE_UPDATE_ID, ISACTIVE, COMPONENT, OPTION_NAME, OPTION_VERSION, DESCRIPTION, U
 2015-11-11 10:10:46.469835+00 | COMMIT
(5 rows)
Revision 2015-03-17 14:38 by alostale
Steps To Reproduce * Using pg9 (just to better monitor)
* Ensure there are no scheduled background processes
* Close all browsers and restart Tomcat
* Check connections (select * from pg_stat_activity): 3 connections are opened
* Operate the application for a while. Check the 3 connections that were present at the beginning are still there, the last query executed for each of them and their state change time have not been modified, this means they are not reused.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker