Back to bug 1017673
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| John Skeoch | 2013-10-23 23:05:18 UTC | Assignee | jpai | dimitris |
| Dimitris Andreadis | 2013-10-24 18:28:05 UTC | Assignee | dimitris | david.lloyd |
| Jan Martiska | 2013-10-30 13:18:15 UTC | Status | NEW | ASSIGNED |
| Assignee | david.lloyd | jmartisk | ||
| Dana Mison | 2013-11-28 06:45:18 UTC | CC | dmison, jmartisk | |
| Flags | needinfo?(jmartisk) | |||
| Jan Martiska | 2013-11-28 07:51:09 UTC | Target Release | --- | EAP 6.3.0 |
| Flags | needinfo?(jmartisk) | |||
| Dana Mison | 2013-11-29 04:03:27 UTC | Doc Text | If a bean attempts to create a new timer at the same time as another thread is calling the `getTimers()` method, an exception of ConcurrentModificationException is thrown. This occurs because the `getTimers()` method does not call `synchronized()` on the timers. This will be fixed in the next release. | |
| Doc Type | Bug Fix | Known Issue | ||
| Jan Martiska | 2014-01-02 08:53:24 UTC | Status | ASSIGNED | POST |
| David M. Lloyd | 2014-01-02 15:08:56 UTC | CC | david.lloyd | |
| Kabir Khan | 2014-01-09 22:28:59 UTC | Status | POST | MODIFIED |
| CC | kkhan | |||
| Target Milestone | --- | DR0 | ||
| Dana Mison | 2014-01-09 23:34:18 UTC | CC | dmison | |
| Paul Gier | 2014-02-11 23:54:03 UTC | Status | MODIFIED | ON_QA |
| Jan Martiska | 2014-02-12 10:23:40 UTC | Status | ON_QA | VERIFIED |
| Lucas Costi | 2014-05-13 05:32:19 UTC | CC | lcosti | |
| Doc Text | If a bean attempts to create a new timer at the same time as another thread is calling the `getTimers()` method, an exception of ConcurrentModificationException is thrown. This occurs because the `getTimers()` method does not call `synchronized()` on the timers. This will be fixed in the next release. | If a bean attempted to create a new timer at the same time as another thread was calling the `getTimers()` method, a `ConcurrentModificationException` was thrown. This occurred because the `getTimers()` method did not call `synchronized()` on the timers. This issue is fixed in this release, and the timer service implementation's `getTimers()` method now properly calls `synchronized()` on the timers. | ||
| Doc Type | Known Issue | Bug Fix | ||
| mark yarborough | 2014-06-28 15:44:52 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:44:52 UTC |
Back to bug 1017673