Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0029490 | Openbravo ERP | A. Platform | public | 2015-04-01 11:19 | 2015-10-13 10:16 |
|
| Reporter | egoitz | |
| Assigned To | egoitz | |
| Priority | normal | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | unable to reproduce | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | alostale |
| OBNetwork customer | OBPS |
| Web browser | |
| Modules | Core |
| Support ticket | 35388 |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0029490: The quartz scheduler is interrupted and the background process stop working |
| Description | On some environment the background process stop working.
That is solved restarting tomcat so seems related with the quartz process no working. |
| Steps To Reproduce | *unable to reproduce |
| Proposed Solution | there should be a mechanism that indicates if the quartz is working or not at least to know if it is needed to restart tomcat. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | design defect | 0035329 | | acknowledged | Triage Platform Base | scheduled processes are not executed in some cases (ie. after some OOM) |
|
| Attached Files | jstack1.txt (26,904) 2015-07-29 11:52 https://issues.openbravo.com/file_download.php?file_id=8313&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2015-04-01 11:19 | egoitz | New Issue | |
| 2015-04-01 11:19 | egoitz | Assigned To | => platform |
| 2015-04-01 11:19 | egoitz | OBNetwork customer | => Yes |
| 2015-04-01 11:19 | egoitz | Modules | => Core |
| 2015-04-01 11:19 | egoitz | Triggers an Emergency Pack | => No |
| 2015-04-01 11:21 | egoitz | Support ticket | => 35388 |
| 2015-04-01 11:24 | egoitz | Resolution time | => 1430344800 |
| 2015-04-07 09:37 | alostale | Note Added: 0076350 | |
| 2015-04-07 09:37 | alostale | Status | new => feedback |
| 2015-04-07 09:38 | alostale | Assigned To | platform => egoitz |
| 2015-04-07 10:06 | egoitz | Note Added: 0076354 | |
| 2015-04-07 10:06 | egoitz | Assigned To | egoitz => alostale |
| 2015-04-07 10:06 | egoitz | Status | feedback => new |
| 2015-04-27 13:17 | jonalegriaesarte | Assigned To | alostale => jonalegriaesarte |
| 2015-04-27 13:17 | jonalegriaesarte | Status | new => feedback |
| 2015-07-29 11:51 | egoitz | Resolution time | 1430344800 => 1439589600 |
| 2015-07-29 11:51 | egoitz | Assigned To | jonalegriaesarte => alostale |
| 2015-07-29 11:52 | egoitz | Status | feedback => new |
| 2015-07-29 11:52 | egoitz | File Added: jstack1.txt | |
| 2015-07-30 10:00 | alostale | Note Added: 0079120 | |
| 2015-07-30 10:00 | alostale | Status | new => feedback |
| 2015-07-30 10:00 | alostale | Assigned To | alostale => egoitz |
| 2015-10-13 10:16 | dmitry_mezentsev | Review Assigned To | => alostale |
| 2015-10-13 10:16 | dmitry_mezentsev | Note Added: 0080944 | |
| 2015-10-13 10:16 | dmitry_mezentsev | Status | feedback => closed |
| 2015-10-13 10:16 | dmitry_mezentsev | Resolution | open => unable to reproduce |
| 2017-02-21 17:01 | alostale | Relationship added | related to 0035329 |
|
Notes |
|
|
|
More information is required to be able to work on this issue:
* How does quartz stop working?
* Even not knowing the cause, which are the symptoms?
* Are there any message in the logs?
* ... |
|
|
|
(0076354)
|
|
egoitz
|
|
2015-04-07 10:06
|
|
The symptoms is that the background processes stop working. rescheduling the process does not solve the problem.
If you configure a process to be executed immediately it does not work.
The problem is solved after restart tomcat.
We don't know how to reproduce it so we can not get the logs. |
|
|
|
|
|
The stack trace provided looks fine: there are 10 Quartz Worker threads awaiting to run background processes, which is the normal situation when there is no running processes. |
|
|
|
|
|
No feedback for too long. |
|