Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajorhave not tried2020-07-30 15:062020-09-28 12:33
ReportershuehnerView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionout of dateFixed in VersionPR20Q4
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseOracleJava version
OS VersionDatabase version11.2Ant version
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0044726: jdbc connection to Oracle 11 sometimes fails

DescriptionWeekly CI job to run 'oldest stack' try-retail Java8 and Oracle11 fails with following error.

/home/openbravo/tools/ant_rm.xml:43: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found

For info: That ant_rm.xml is effectively just using ant 'Sql' task reusing jdbc libraries from the local workspace. i.e. and create.database behaves the Same.

Example build log: [^]

Running the same job with ora11 but Java11 does NOT fail.

Trying to reproduce locally with Oracle 11.2 showed the following.
1.) does NOT fail with java8 or java11 by default
2.) Setting 'export TZ="Etc/UTC" before the ant call causes the error to happen
3.) Using step 2.) error happens with both Java8 and Java11

4.) Going back to git-commit: commit 01c921dc431db07a321435ec51b3333d7bda6099
which is commit just before last jdbc driver update from issues [^] does NOT fail even with export from step 2 active

So apparently several triggers to cause the problem:
a.) new jdbc driver jar
b.) Setting timezone to Etc/UTC via TZ variable (for info that is what is active in CI system) with both java8 and java11
c.) Unknown why in CI the problem only happens with Java8 but not 11 (even with system-wide timezone being Etc/UTC)

So far error has been seen with Oracle11 + Java8 combination in CI
It is NOT known if happens only with Oracle11
Steps To ReproduceSee description as several cases to cause the error with it being happening in CI + reproducible locally with different steps.

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
caused by defect 0043137 closedalostale oracle jdbc driver needs to be updated to support Oracle 19c 

-  Notes
shuehner (administrator)
2020-07-30 15:08

Maybe relevant info:
All those talk about oracle not being happening with some timezone values and how to override those. None of them gives any hint on the CI 'only with java8' issue. [^] [^] [^]
shuehner (administrator)
2020-07-30 15:15

Updated testing status:
Local testing with Oracle 19.3 does NOT produce the error (having TZ set as described in this issue). Works fine with both Java8+Java11
shuehner (administrator)
2020-09-28 12:33

20Q4 release stopped support of Oracle 11 so no change is required in the product as this issue only affected that old oracle version. [^]

- Issue History
Date Modified Username Field Change
2020-07-30 15:06 shuehner New Issue
2020-07-30 15:06 shuehner Assigned To => platform
2020-07-30 15:06 shuehner Modules => Core
2020-07-30 15:06 shuehner Triggers an Emergency Pack => No
2020-07-30 15:06 shuehner Relationship added caused by 0043137
2020-07-30 15:08 shuehner Note Added: 0121715
2020-07-30 15:15 shuehner Note Added: 0121716
2020-09-28 12:33 shuehner Note Added: 0123424
2020-09-28 12:33 shuehner Status new => closed
2020-09-28 12:33 shuehner Resolution open => out of date
2020-09-28 12:33 shuehner Fixed in Version => PR20Q4

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker