0036291: even not configured, RO pool uses a different pool instance

Description

When 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 Reproduce

1. 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 Solution

To 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

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

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

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2017-06-20 10:43	alostale	New Issue
2017-06-20 10:43	alostale	Assigned To	=> platform
2017-06-20 10:43	alostale	OBNetwork customer	=> No
2017-06-20 10:43	alostale	Modules	=> Core
2017-06-20 10:43	alostale	Triggers an Emergency Pack	=> No
2017-06-20 10:43	alostale	Relationship added	related to 0034816
2017-06-20 10:44	alostale	Status	new => acknowledged
2017-06-20 10:45	alostale	Relationship added	related to 0035855
2017-10-11 14:17	caristu	Relationship added	related to 0037055
2022-02-01 08:08	alostale	Assigned To	platform => Triage Platform Base