Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011857Openbravo ERPB. User interfacepublic2009-12-23 11:542012-09-24 23:41
Reporterplujan 
Assigned Tomarvintm 
PriorityhighSeveritymajorReproducibilityalways
StatusscheduledResolutionopen 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0011857: Risks about choosing other options but "Restart Tomcat" are not properly displayed
DescriptionAfter a Rebuild, I have three options with following message:

In order for the changes to take effect, you need to restart the servlet container or reload the Openbravo application.
(o) Restart servlet container now
( ) Reload the Openbravo application now
( ) Don't do anything now. I will reload the Openbravo application manually later


The issue is that default action should be the only available option. Other options could take the system down if, for example, user forgets to manually restart. This is specially important after a Core update, since Database was actually updated although tomcat was not restarted yet, so you are in an intermediate stage until Tomcat restart.
Steps To ReproduceSimply rebuild the system after any module (or Core) update
Proposed SolutionRestart Tomcat option should be the default and recommended option. The rest should be clearly separated, and some confirmation javascript window asking the user to fully understand the risks about operating the system until Tomcat restart should be displayed.
Additional Information
TagsNewRebuildWindow-QA
Relationships
duplicate of defect 0015841 closed alostale Remove second option "Reload" after rebuild process 
Attached Filespng 2_50mp10_MessageIsNotCorrect.PNG (34,811) 2009-12-23 11:54
https://issues.openbravo.com/file_download.php?file_id=2081&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2009-12-23 11:54plujanNew Issue
2009-12-23 11:54plujanAssigned To => marvintm
2009-12-23 11:54plujanFile Added: 2_50mp10_MessageIsNotCorrect.PNG
2009-12-23 11:54plujanStatusnew => scheduled
2009-12-23 11:54plujanfix_in_branch => pi
2009-12-23 13:07plujanTag Attached: NewRebuildWindow-QA
2011-03-31 12:30iperdomoRelationship addedduplicate of 0015841
2011-03-31 12:30iperdomoStatusscheduled => closed
2011-03-31 12:30iperdomoResolutionopen => duplicate
2011-03-31 12:53plujanNote Added: 0035414
2011-03-31 12:53plujanStatusclosed => new
2011-03-31 12:53plujanResolutionduplicate => open
2011-04-11 10:29alostaleStatusnew => scheduled
2012-06-08 11:32alostaleTypedefect => design defect
2012-06-08 11:32alostalefix_in_branchpi =>
2012-09-24 23:41AugustoMauchNote Added: 0052516
2012-09-24 23:41AugustoMauchPriorityurgent => high

Notes
(0035414)
plujan   
2011-03-31 12:53   
This issue is not a duplicate of 0015841. That issue is included in this one, so the 0015841 should have been rejected as duplicated of this one.

In order to properly solve this issue, now that it was partially solved by solving the other issue, a message should alert to the user that the "don't do anything now" actually means that the database was updated and the Tomcat should be restarted as soon as possible.
(0052516)
AugustoMauch   
2012-09-24 23:41   
Effort: 1
Impact: mid
Plan: short