Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0031961Openbravo ERPA. Platformpublic2016-01-19 21:212016-01-21 08:41
Production - QA Approved
3.0PR15Q4 [^]
0031961: Incorrect posting data when not defining an external connection pool on the
Having on the file the parameter without value the documents are posted on the previous date than the accounting date.

The configuration is:

The problem happens by default when updating to PR15Q4.

It is reproducible as:

Edit the file by replacing




Then compile with
ant smartbuild
and restart tomcat.
Then access to the application.

Reset accounting for invoices
Schedule the accoounting background process.

When it finishes check the invoices and see that the accounting date of the fact_acct entries is one day before the accounting date of the documents.

REstoring the file solves the problem.
No tags attached.
blocks defect 0031959 closed caristu Incorrect posting data when not defining an external connection pool on the 
Issue History
2016-01-20 09:09alostaleTypedefect => backport
2016-01-20 09:09alostaleTarget Version => 3.0PR15Q4.2
2016-01-20 19:32hgbotCheckin
2016-01-20 19:32hgbotNote Added: 0083472
2016-01-20 19:32hgbotStatusscheduled => resolved
2016-01-20 19:32hgbotResolutionopen => fixed
2016-01-20 19:32hgbotFixed in SCM revision => [^]
2016-01-20 19:32caristuReview Assigned To => alostale
2016-01-20 19:32caristuIssue Monitored: alostale
2016-01-21 08:18alostaleRegression introduced by commit [^] => [^]
2016-01-21 08:31alostaleNote Added: 0083482
2016-01-21 08:33alostaleTriggers an Emergency PackNo => Yes
2016-01-21 08:41alostaleNote Added: 0083484
2016-01-21 08:41alostaleStatusresolved => closed
2016-01-21 08:41alostaleFixed in Version => 3.0PR15Q4.2

2016-01-20 19:32   
Repository: erp/backports/3.0PR15Q4.2
Changeset: 08ab0b08fa66b4508c4b1d21d1ff2a99253e4a5b
Author: Carlos Aristu <carlos.aristu <at>>
Date: Wed Jan 20 19:01:04 2016 +0100
URL: [^]

fixes issue 31961: Incorrect posting data using postgresql jdbc connection pool

There was a problem in the binary transfer of Dates performed by the postgresql library version 9.4-1201. This problem is not happening on version 9.4-1207 because when the queries are executed it now includes a mechanism to identify if the fields of the query need to update their format to binary.

For this reason, to fix the problem the postgresql jdbc driver has been upgraded to version 9.4-1207

M build.xml
M legal/Licensing.txt
A lib/runtime/postgresql-9.4.1207.jre6.jar
R lib/runtime/postgresql-9.4-1201.jdbc4.jar
2016-01-21 08:31   
This issue affects PostgreSQL instances using Apache Commons DBCP Pool, this is externalPoolClassName property in is empty, which is the default values for instances updating to >=PR15Q4 from a previous version. Note that even this value is changed to use Tomcat Pool, if the instance was executing old value for a time, data generated in this period might be affected.

It affects accounting process. But it can also affect ANY other process implemented in XSQL (or using direct JDBC connections) doing operations on date fields read from database. It DOES NOT affect processes using DAL nor PL/SQL processes.

It is caused by issues 376 [1] and 387 [2] in PostgreSQL JDB.

[1] [^]
[2] [^]
2016-01-21 08:41   
Code reviewed

Tested accounting process using Commons DBCP and Tomcat pool, in both cases there are not mismatches in accounting dates.