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

View Revisions: Issue #34496 All Revisions ] Back to Issue ]
Summary 0034496: CostingAlgorithmAdjustmentImp class is not thread safe
Revision 2016-11-14 16:04 by caristu
Description The application scoped class CostingAlgorithmAdjustmentImp[1] is not stateless[2]. This means that it is thread unsafe and therefore it does not guarantee its correct execution (even working in a single node) when being executed by different threads in parallel.


[1] https://code.openbravo.com/erp/devel/pi/file/3b0fb57e7fed/src/org/openbravo/costing/CostingAlgorithmAdjustmentImp.java [^]
[2] http://docs.oracle.com/javaee/6/tutorial/doc/gipjg.html#gipim [^]
Revision 2016-11-14 16:03 by caristu
Description The application scoped class CostingAlgorithmAdjustmentImp[1] is not stateless[2]. This means that it is thread unsafe and therefore it does not guarantee its correct execution (even working in a single node) when being executed by different threads in parallel.


[1] https://code.openbravo.com/erp/devel/pi/file/3b0fb57e7fed/src/org/openbravo/costing/CostingAlgorithmAdjustmentImp.java [^]
[2] http://docs.oracle.com/javaee/6/tutorial/doc/gipjg.html#gipin [^]
Revision 2016-11-14 16:01 by caristu
Description The application scoped class CostingAlgorithmAdjustmentImp is not stateless[1]. This means that it is thread unsafe and therefore it does not guarantee its correct execution (even working in a single node) when being executed by different threads in parallel.


[1] http://docs.oracle.com/javaee/6/tutorial/doc/gipjg.html#gipin [^]


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker