Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0032259 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| defect | [Openbravo ERP] A. Platform | minor | random | 2016-02-17 13:20 | 2022-02-01 08:05 | ||||||
| Reporter | plujan | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | pi | SCM revision | |||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0032259: A background process running while stopping Tomcat generates an exception | ||||||||||
| Description | During our regular integration process we've seen an exception in the openbravo log caused by the accounting server. This exception seems to be generated by the process running just when the last task of the job (stopping Tomcat) happens. | ||||||||||
| Steps To Reproduce | 1. With the ERP running the AcctServer process (the default installation will do) stop the Tomcat server. This error is not easy to reproduce, we've seen it in about 3% of the executions, and also the stack trace is not always the same. Only things in common among all the failures is that Tomcat was in process of stopping and that the failing process is the AcctServer. | ||||||||||
| Proposed Solution | The issue can be solved by: a. Improving the log to show in a clear way that Tomcat is in process of stopping, so any exception coming after that should not be taken into account. b. Improving the thread management to not show an exception in this specific case. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2016-02-17 13:20 | plujan | New Issue | |
| 2016-02-17 13:20 | plujan | Assigned To | => platform |
| 2016-02-17 13:20 | plujan | Modules | => Core |
| 2016-02-17 13:20 | plujan | Triggers an Emergency Pack | => No |
| 2016-02-17 13:22 | plujan | Proposed Solution updated | |
| 2016-02-17 13:31 | alostale | Status | new => acknowledged |
| 2022-02-01 08:05 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |