-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b107
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8156228 | 8u111 | Mark Sheppard | P3 | Resolved | Fixed | b01 |
JDK-8146763 | 8u102 | Sean Coffey | P3 | Resolved | Fixed | b01 |
JDK-8161998 | emb-8u111 | Mark Sheppard | P3 | Resolved | Fixed | b01 |
JDK-8146764 | 7u111 | Sean Coffey | P3 | Resolved | Fixed | b01 |
Customer application opens and closes corba connections to different servers.
These servers may be offline for an undefined time. In this situation the
application tries to reconnect periodically.
The problem is that ORB.destroy() obviously does not dispose fds. Not even
when forcing System.gc() / System.runFinalization()
The provided test program opens a corba connection to a non existent server
and closes it immediately over and over in a loop. Watch e.g.
with pfiles the unlimited growth of fds
- backported by
-
JDK-8146763 ORB destroy() leaks filedescriptors after unsuccessful connection
- Resolved
-
JDK-8146764 ORB destroy() leaks filedescriptors after unsuccessful connection
- Resolved
-
JDK-8156228 ORB destroy() leaks filedescriptors after unsuccessful connection
- Resolved
-
JDK-8161998 ORB destroy() leaks filedescriptors after unsuccessful connection
- Resolved
- duplicates
-
JDK-8144175 ORB destroy() leaks filedescriptors after unsuccessfull connection
- Closed
-
JDK-8144176 ORB destroy() leaks filedescriptors after unsuccessfull connection
- Closed
(1 duplicates)