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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0011857
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] B. User interfacemajoralways2009-12-23 11:542012-09-24 23:41
ReporterplujanView Statuspublic 
Assigned Tomarvintm 
PriorityhighResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0011857: 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.
TagsNewRebuildWindow-QA
Attached Filespng file icon 2_50mp10_MessageIsNotCorrect.PNG [^] (34,811 bytes) 2009-12-23 11:54

- Relationships [ Relation Graph ] [ Dependency Graph ]
duplicate of defect 0015841 closedalostale Remove second option "Reload" after rebuild process 

-  Notes
(0035414)
plujan (manager)
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 (administrator)
2012-09-24 23:41

 Effort: 1
Impact: mid
Plan: short

- Issue History
Date Modified Username Field Change
2009-12-23 11:54 plujan New Issue
2009-12-23 11:54 plujan Assigned To => marvintm
2009-12-23 11:54 plujan File Added: 2_50mp10_MessageIsNotCorrect.PNG
2009-12-23 11:54 plujan Status new => scheduled
2009-12-23 11:54 plujan fix_in_branch => pi
2009-12-23 13:07 plujan Tag Attached: NewRebuildWindow-QA
2011-03-31 12:30 iperdomo Relationship added duplicate of 0015841
2011-03-31 12:30 iperdomo Status scheduled => closed
2011-03-31 12:30 iperdomo Resolution open => duplicate
2011-03-31 12:53 plujan Note Added: 0035414
2011-03-31 12:53 plujan Status closed => new
2011-03-31 12:53 plujan Resolution duplicate => open
2011-04-11 10:29 alostale Status new => scheduled
2012-06-08 11:32 alostale Type defect => design defect
2012-06-08 11:32 alostale fix_in_branch pi =>
2012-09-24 23:41 AugustoMauch Note Added: 0052516
2012-09-24 23:41 AugustoMauch Priority urgent => high

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker