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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0034505
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 09. Financial managementminoralways2016-11-14 18:552017-05-24 12:26
ReportercaristuView Statuspublic 
Assigned ToAtulOpenbravo 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Toaferraz
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0034505: [clustering] review caching of isMigrated field in CostingStatus class

DescriptionisMigrated field is cached whether costing is migrated in CostingStatus class.

As CostingStatus is a singleton class, the value is being cached along all the life cycle of the application. Therefore, in a clustered environment that field could have a different value on each node.

This behavior must be reviewed in order to check if we should we care about it on a clustered environment.
Steps To ReproduceIn description
Tagsclustering
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
blocks design defect 0034490 acknowledgedTriage Platform Base [clustering] Support clustering 

-  Notes
(0096754)
aferraz (manager)
2017-05-24 12:26

 Whenever CostingStatus.isMigrated() method is called, we check if isMigrated flag has not been initialized and in this case we recalculate it again.
Every time CostingStatus.setMigrated() method is called, a previous call to CostingStatus.isMigrated() method is done in the same thread, so we make sure isMigrated flag has been initialized.

Only the thing is multiple JVM will have their own copy of isMigrated. Each JVM will initialize its own isMigrated but again once the ismigrated flag is set there is no way to change its value. There won't be chance of one JVM having isMigrated = true and other having isMigrated = false.

- Issue History
Date Modified Username Field Change
2016-11-14 18:55 caristu New Issue
2016-11-14 18:55 caristu Assigned To => Triage Finance
2016-11-14 18:55 caristu Modules => Core
2016-11-14 18:55 caristu Triggers an Emergency Pack => No
2016-11-14 18:55 caristu Relationship added related to 0034490
2016-11-15 09:14 caristu Relationship deleted related to 0034490
2016-11-15 09:14 caristu Relationship added causes 0034490
2016-11-15 09:15 caristu Relationship deleted causes 0034490
2016-11-15 09:15 caristu Relationship added blocks 0034490
2016-11-15 10:23 alostale Tag Attached: clustering
2017-03-23 15:02 markmm82 Assigned To Triage Finance => AtulOpenbravo
2017-05-24 12:26 aferraz Review Assigned To => aferraz
2017-05-24 12:26 aferraz Note Added: 0096754
2017-05-24 12:26 aferraz Status new => closed
2017-05-24 12:26 aferraz Resolution open => no change required

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker