Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0036291Openbravo ERPA. Platformpublic2017-06-20 10:432022-02-01 08:08
Reporteralostale 
Assigned ToTriage Platform Base 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
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
Summary0036291: even not configured, RO pool uses a different pool instance
DescriptionWhen OBDal.getReadOnlyInstance() is used to get the read only pool, even if read only pool is not configured, a new instance of pool is created. As consequence of this, read only queries are always performed in a different connection.
Steps To Reproduce1. Install DB Pool log module
2. Configure Openbravo.properties to log threads borrowing more than one connection:
     db.pool.logger.enabled=true
     db.pool.logger.logMultipleConnectionsPerThread=true
3. Login
  -check Utility.getImageLogoObject uses two connections because it uses read only pool
Proposed SolutionTo decide whether this is the wanted behavior.

Pros: it makes more consistent the behavior when read only pool is configured and when it is not, in both cases 2 independent connections are used.
Cons: 2 connections are used when 1 might be enough
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0034816 closed caristu Support a second database for reporting 
related to defect 0035855 closed alostale many standard requests borrow more than one connection from DB 
related to defect 0037055 closed caristu Connection leak in threads that makes use of the read only pool and are not encapsulated inside DalThreadHandler  
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-06-20 10:43alostaleNew Issue
2017-06-20 10:43alostaleAssigned To => platform
2017-06-20 10:43alostaleOBNetwork customer => No
2017-06-20 10:43alostaleModules => Core
2017-06-20 10:43alostaleTriggers an Emergency Pack => No
2017-06-20 10:43alostaleRelationship addedrelated to 0034816
2017-06-20 10:44alostaleStatusnew => acknowledged
2017-06-20 10:45alostaleRelationship addedrelated to 0035855
2017-10-11 14:17caristuRelationship addedrelated to 0037055
2022-02-01 08:08alostaleAssigned Toplatform => Triage Platform Base

There are no notes attached to this issue.