Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0030920Openbravo ERPA. Platformpublic2015-09-24 12:222015-10-02 07:39
alostale 
platform 
immediateminorhave not tried
closedopen 
5
 
3.0PR15Q3.3 
Core
Production - Confirmed Stable
2011-01-19
3.0RC4
https://code.openbravo.com/erp/devel/pi/rev/7fc34fd92373 [^]
No
0030920: can't use DB connection defined as JNDI service
It is not possible to use DB connection defined as JNDI service because even having it configured, direct connection is tried to be created in some places.

The behavior is different depending on OB version:

* 3.0RC4-current pi (pre PR15Q4), this error is risen:
   [main] ERROR org.openbravo.database.ConnectionProviderImpl - Error getting connection java.sql.SQLException: No suitable driver found for null/null
    at java.sql.DriverManager.getConnection(DriverManager.java:689)
    at java.sql.DriverManager.getConnection(DriverManager.java:270)
    at org.openbravo.database.OpenbravoDriverManagerConnectionFactory.createConnection(OpenbravoDriverManagerConnectionFactory.java:55)
* current pi (pre PR15Q4), in same place a ClassCastException is thrown trying to cast JNDIConnectionProvider to ConnectionProviderImpl

Additionally, when it is combined with JdbcExternalConnectionPool:
* it tries to create two pools: one for DAL and another one for xsql connections
* DAL connections try to use direct DB connection rather than JNDI resulting in NPE if those properties are not set
* Configure Openbravo to use JNDI (removing the rest of direct DB connection settings) [1] removing from Openbravo.properties settings to use direct DB connection
* Start Tomcat

[1] follow documentation in http://wiki.openbravo.com/wiki/Projects:JNDI_Service/Technical_Documentation [^] until 0030918 is fixed
No tags attached.
blocks defect 00309193.0PR16Q1 closed alostale can't use DB connection defined as JNDI service 
Issue History
2015-09-24 12:39alostaleTypedefect => backport
2015-09-24 12:39alostaleTarget Version => 3.0PR15Q3.3
2015-10-02 07:39alostaleNote Added: 0080795
2015-10-02 07:39alostaleStatusscheduled => closed

Notes
(0080795)
alostale   
2015-10-02 07:39   
It won't be fixed as backport due the risk it would add and the low usage of this feature.