-
Bug
-
Resolution: Fixed
-
P3
-
6, 7, 8
-
b09
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8039078 | 9 | Shanliang Jiang | P3 | Resolved | Fixed | b08 |
JDK-8045616 | 8u25 | Shanliang Jiang | P3 | Resolved | Fixed | b01 |
JDK-8053843 | emb-8u26 | Shanliang Jiang | P3 | Resolved | Fixed | b17 |
LinearExecutor uses an instance variable "command" to enqueue a command to be executed. It starts a new thread to read this variable and perform the command. A subsequent call to the "execute()" method without the processor thread being fully started will lead to an IAE.
ILW = HLM
I = H: It will crash the application with IAE
L = L: One needs to call the "execute()" methods in very rapid succession
W = M: One can provide his own implementation of the ClientNotifForwarder executor (via the "jmx.remote.x.fetch.notifications.executor" key in the provided env map)
ILW = HLM
I = H: It will crash the application with IAE
L = L: One needs to call the "execute()" methods in very rapid succession
W = M: One can provide his own implementation of the ClientNotifForwarder executor (via the "jmx.remote.x.fetch.notifications.executor" key in the provided env map)
- backported by
-
JDK-8039078 c.s.j.r.i.ClientNotifForwarder$LinearExecutor prone to data races
- Resolved
-
JDK-8045616 c.s.j.r.i.ClientNotifForwarder$LinearExecutor prone to data races
- Resolved
-
JDK-8053843 c.s.j.r.i.ClientNotifForwarder$LinearExecutor prone to data races
- Resolved