Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002032Openbravo ERPA. Platformpublic2007-10-03 10:192008-06-12 09:43
Reporteriperdomo 
Assigned Toiperdomo 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version2.35 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0002032: Some connections remain active in the pool
DescriptionEnvironment
Release: 2.34
Database: Oracle

Some connections remain active after executing a prepared statement and don't releasing the connection.

This behavior was identified on the ExecuteQuery and ExportGrid class.

Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange

Notes
(0005621)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1806777 [^]
(0002270)
iciordia   
2007-10-03 13:28   
(edited on: 2008-06-12 09:22)
Logged In: YES
user_id=1455356
Originator: NO

This bug is the root cause for the "Http 500 Error: no connections available". In highly active Openbravo installations the number of database session increases up to system limit so the the system becomes unavailable. If the activity is not so high the pool itself releases these locked sessions after a while.
(0002271)
pjuvara   
2007-10-24 10:10   
(edited on: 2008-06-12 09:22)
Logged In: YES
user_id=1871571
Originator: NO

It is not possible for QA to verify this fix. Skipping.
P.S.: after several hours of usage of two testers, we have not run out of connections, which is an indication that the problem does not exist to the same extent of severity that we had in 2.34.