Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #33438 All Revisions ] 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:

  • New connection does not get initialized with the session config parameters, this can cause the problem reported in 0033429
  • These new connections are autonomously managed out of the declared pool
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:

  • New connection does not get initialized with the session config parameters, this can cause the problem reported in 0033429
  • These new connections are autonomously managed out of the declared pool
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
Powered by Mantis Bugtracker