Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015319Openbravo ERPA. Platformpublic2010-11-27 11:132011-01-21 00:00
Reporterpsarobe 
Assigned Toshuehner 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
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
Summary0015319: Once you update from RC2 to RC3 the ERP is not able to restart tomcat by itself
DescriptionOnce you update from RC2 to RC3 the ERP is not able to restart tomcat by itself and you need to restart tomcat manually
Steps To Reproduce1. Install RC2 appliance
2. Update to RC3. Here to steps:
  2.1 First you have to update core. Here seems there is no problems
  2.2 Second you update the template. After rebuilding the ERP is not able to restart tomcat
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0015709 closed shuehner Orphan jar-files are not deleted from deployed webapp in tomcat when they are not present anymore in WebContent (after upgrade) 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-11-27 11:13psarobeNew Issue
2010-11-27 11:13psarobeAssigned To => alostale
2010-11-27 11:13psarobeOBNetwork customer => No
2010-11-29 07:37alostaleAssigned Toalostale => shuehner
2010-11-29 07:37alostalePriorityimmediate => urgent
2010-11-29 07:38alostaleStatusnew => scheduled
2010-11-29 07:38alostalefix_in_branch => pi
2011-01-19 19:55shuehnerRelationship addedrelated to 0015709
2011-01-20 19:35shuehnerNote Added: 0033800
2011-01-20 19:35shuehnerStatusscheduled => closed
2011-01-20 19:35shuehnerResolutionopen => no change required
2011-01-21 00:00anonymoussf_bug_id0 => 3163027

Notes
(0033800)
shuehner   
2011-01-20 19:35   
Rejecting as issue triggering the change was reverted for rc2->rc3 updates. The real problem in the build-system has now been fixed in issue 15709.