Project:
View Revisions: Issue #33438 | [ Back to Issue ] | ||
Summary | 0033438: DalConnectionProvider.getTransactionConnection does not obtain connection from common pool | ||
Revision | 2016-07-06 10:14 by alostale | ||
Description | DalConnectionProvider.getTransactionConnection method used to keep transaction in sqlc, obtains the new connection directly from Hibernate's pool regardless how Openbravo pool is configured. The consequences are:
|
||
Revision | 2016-07-06 10:13 by alostale | ||
Steps To Reproduce | Using Oracle, install 3.1.1200 version of the aging balance module: https://code.openbravo.com/erp/mods/org.openbravo.agingbalance [^] Go to Receivables Aging Balance. Launch the report with the parameters: *Organization: F&B España *General Ledger: F&B España *As of date: 27-06-2016 *Show Details: Checked The rest of the parameters can be set with the default values It should throw an error: 55585 [http-8081-2] ERROR org.openbravo.base.exception.OBException - Error javax.servlet.ServletException: @CODE=1843@ORA-01843: not a valid month at org.openbravo.agingbalance.ad_reports.AgingDaoData.selectDetail(AgingDaoData.java:492) at org.openbravo.agingbalance.ad_reports.AgingDao.getOpenReceivablesAgingScheduleDetails(AgingDao.java:217) at org.openbravo.agingbalance.ad_reports.AgingProcess.printPageDetails(AgingProcess.java:391) at org.openbravo.agingbalance.ad_reports.AgingProcess.doPost(AgingProcess.java:156) at org.openbravo.base.HttpBaseServlet.doGet(HttpBaseServlet.java:294) This behavior is not always consistent. |
||
Revision | 2016-07-06 10:13 by alostale | ||
Description | DalConnectionProvider.getTransactionConnection method used to keep transaction in sqlc, obtains the new connection directly from Hibernate's pool regardless how Openbravo pool is configured. The consequences are:
|
||
Revision | 2016-07-06 10:06 by alostale | ||
Steps To Reproduce | Install the latest version of the aging balance module: https://code.openbravo.com/erp/mods/org.openbravo.agingbalance [^] Go to Receivables Aging Balance. Launch the report with the parameters: *Organization: F&B España *General Ledger: F&B España *As of date: 27-06-2016 *Show Details: Checked The rest of the parameters can be set with the default values It should throw an error: 55585 [http-8081-2] ERROR org.openbravo.base.exception.OBException - Error javax.servlet.ServletException: @CODE=1843@ORA-01843: not a valid month at org.openbravo.agingbalance.ad_reports.AgingDaoData.selectDetail(AgingDaoData.java:492) at org.openbravo.agingbalance.ad_reports.AgingDao.getOpenReceivablesAgingScheduleDetails(AgingDao.java:217) at org.openbravo.agingbalance.ad_reports.AgingProcess.printPageDetails(AgingProcess.java:391) at org.openbravo.agingbalance.ad_reports.AgingProcess.doPost(AgingProcess.java:156) at org.openbravo.base.HttpBaseServlet.doGet(HttpBaseServlet.java:294) This behavior is not always consistent. |
||
Revision | 2016-07-06 10:06 by alostale | ||
Description | There is a problem in the Aging Balance Report with Oracle. Sometimes it throws the error ora-01843 not a valid month. But this behavior is not always consistent. This is happening since we started to use a new ConnectionProvider for launching the query: new DalConnectionProvider(false) This might be related to some problem while creating a new connection, it might be that the date preferences are not correctly set in the database connection we are using. |
Copyright © 2000 - 2009 MantisBT Group |