-
Bug
-
Resolution: Fixed
-
P3
-
1.0
-
None
-
tiger
-
unknown
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2113226 | 1.0 | Jean-Francois Denise | P3 | Resolved | Fixed | team |
b11
When I do run the JSR 160 TCK, the remote side, which is either JMX Client or JMX Server, is the same JVM, alive during all the TCK run.
At the run end, I saw there is several threads named "JavaIDL Reader" that are never dying. I do not now internals of IIOP but it could look like a thread leak.
I attach a full thread dump where you can see 34 "JavaIDL Reader" threads as well as 2 "JavaIDL Listener" ones.
I only have 7 tests where RMI/IIOP is enabled.
When I do run the JSR 160 TCK, the remote side, which is either JMX Client or JMX Server, is the same JVM, alive during all the TCK run.
At the run end, I saw there is several threads named "JavaIDL Reader" that are never dying. I do not now internals of IIOP but it could look like a thread leak.
I attach a full thread dump where you can see 34 "JavaIDL Reader" threads as well as 2 "JavaIDL Listener" ones.
I only have 7 tests where RMI/IIOP is enabled.
- backported by
-
JDK-2113226 JSR 160 - possible thread leak with RMI/IIOP
-
- Resolved
-
- relates to
-
-
- Resolved
-