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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0019671
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminorhave not tried2012-02-06 19:312016-03-24 07:59
ReportershuehnerView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionduplicateFixed in Version3.0PR15Q3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0019671: Create new check with verifies that postgres timezone == system (tomcat-server) timezone

DescriptionIn case that the time (hour) reported by the dbms and the time reported by java code running inside tomcat are not in sync the application will fail in various ways.

Example: update.database triggers local changes check directly after install.source (as last_db_update timstamp is not in sync with the various created/updates timestamp of the data).

As that is difficult/time-consuming to debug the application should have a check of the environment and warn the admin/developer of that.

Example locations:
- on install.source, on update.database, each tomcat startup
Steps To ReproduceLinux system with timezone not being UTC (i.e. gmt+1)
Reconfigure postgres to use UTC timezone (TimeZone='utc' in main config file)
do install.source
install some module (i.e. spanish comminuty localization pack)
rebuild
Notice: that update.database step will fails with 'database has local changes' message.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of feature request 00296753.0PR15Q3 closedcaristu check DB and Tomcat have the same time at Tomcat start 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2012-02-06 19:31 shuehner New Issue
2012-02-06 19:31 shuehner Assigned To => alostale
2012-02-06 19:31 shuehner Modules => Core
2016-03-24 07:58 alostale Status new => closed
2016-03-24 07:58 alostale Fixed in Version => 3.0PR15Q3
2016-03-24 07:58 alostale Triggers an Emergency Pack => No
2016-03-24 07:58 alostale Resolution open => duplicate
2016-03-24 07:58 alostale Relationship added has duplicate 0029675
2016-03-24 07:59 alostale Relationship replaced duplicate of 0029675


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker