Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014261Openbravo ERPA. Platformpublic2010-08-21 12:412010-09-13 12:38
Reporterjpabloae 
Assigned Toiperdomo 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS20OS VersionCommunity Appliance
Product Version2.50MP20 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0014261: Error activating the heartbeat with Core in Test maturity level
DescriptionWhen using a 2.50MP20 community appliance you get a NullPointerException if you try to enable the heartbeat after setting the maturity level to "Test". The goal I'm looking for is to update core to 2.50MP21, currently located in the "Test" maturity level of the CR.

After that if you insist and try to update core again it seems that it succeeds and doesn't show the error again.
Steps To Reproduce1. Start a 2.50MP20 community appliance.
2. Go to "General setup -> Application -> Activation" and activate the instance.
3. Go to "General setup -> Application -> Module management". Then enter the "Settings" tab and set Core to the "Test" maturity level (see test-level.png).
4. Go to the "Installed modules" tab and click on "Scan for updates".
5. You'll see 1 update available. Click on "Install Updates Now".
6. You are asked to activate the heartbeat. When you click in "OK" it throws a NullPointerException (see npe.log).
Proposed Solution
Additional Information
TagsRegression
Relationships
Attached Filespng test-level.png (132,125) 2010-08-21 12:41
https://issues.openbravo.com/file_download.php?file_id=2889&type=bug
png

log npe.log (4,745) 2010-08-21 12:41
https://issues.openbravo.com/file_download.php?file_id=2890&type=bug
Issue History
Date ModifiedUsernameFieldChange
2010-08-21 12:41jpabloaeNew Issue
2010-08-21 12:41jpabloaeAssigned To => alostale
2010-08-21 12:41jpabloaeFile Added: test-level.png
2010-08-21 12:41jpabloaeOBNetwork customer => No
2010-08-21 12:41jpabloaeFile Added: npe.log
2010-08-21 12:43jpabloaeDescription Updatedbug_revision_view_page.php?rev_id=706#r706
2010-08-23 09:41shuehnerAssigned Toalostale => shuehner
2010-08-23 16:02iperdomoAssigned Toshuehner => iperdomo
2010-08-23 16:02iperdomoStatusnew => scheduled
2010-08-23 16:02iperdomofix_in_branch => pi
2010-08-23 16:02iperdomoStatusscheduled => resolved
2010-08-23 16:02iperdomoFixed in SCM revision => https://code.openbravo.com/erp/devel/pi/rev/d1ae61b55653 [^]
2010-08-23 16:02iperdomoResolutionopen => fixed
2010-08-23 16:04iperdomoNote Added: 0030228
2010-08-23 17:06shuehnerNote Added: 0030232
2010-08-23 17:06shuehnerStatusresolved => closed
2010-08-24 18:32shuehnerNote Added: 0030265
2010-08-25 13:22psarobeTag Attached: Regression
2010-09-13 12:38anonymoussf_bug_id0 => 3065178

Notes
(0030228)
iperdomo   
2010-08-23 16:04   
The commit comment is associated to issue 0014262 but the changeset fixes this issue.
(0030232)
shuehner   
2010-08-23 17:06   
Reviewed and tested on pi/pgsql (rev: e4855af0983e)
Tested:
- Initial heartbeat popup after installtion
- enabling/disabling heartbeat in heartbeat configuration window
The following tests both with heartbeat enabled & disabled before doing the test
- install modules
- Having multiple updates available, update a single module
- Having multiple updates available, update all at once

All working fine -> closing
(0030265)
shuehner   
2010-08-24 18:32   
Adding comment for link to changeset fixing this (which is mentioned in note 0030228):
https://code.openbravo.com/erp/devel/pi/rev/d1ae61b55653 [^]

Fixes issue 14262: Fixes module update when hearbeat is not active
The flow when updating a module (e.g. core) is to enable heartbeat first (if
is not active), then after a successfull activation the flow is returned to
the Module Management window. This flow redirection was sending a INSTALL
command so the execution flow was changed, and a NPE was thrown.