|
Quick Lists
|
|
Bug ID:
|
6763340
|
|
Votes
|
0
|
|
Synopsis
|
memory leak in com.sun.corba.se.* classes
|
|
Category
|
idl:orb
|
|
Reported Against
|
b02
|
|
Release Fixed
|
5.0u21-rev(b03),
6u16-rev(b04) (Bug ID:2180407)
|
|
State
|
10-Fix Delivered,
Verified,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
6873605
|
|
Submit Date
|
23-OCT-2008
|
|
Description
|
Customer reports a memory leak with a WebLogic app with 1.5.0_16. Histograms shows several classes continuously growing over time. These classes include weblogic.corba.client.utils.EndPointInfo and several com.sun.cobra.se.impl.* classes. The heap dump shows EndPointInfo is held by reference by com.sun.corba.se.impl.legacy.connection.SocketFactoryContactInfoImpl
References to SocketFactoryContactInfoImpl were more com.sun.cobra.se.impl.* classes. Going further up the stack, I found these com.sun classes were referencing each other in a circular fashion.
I looked at one particular instance of com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl. There are over 8800 references to this instance. Here are some of the references.
xxxxx@xxxxx (85 bytes) : field connection
xxxxx@xxxxx (85 bytes) : field connection
xxxxx@xxxxx (37 bytes) : field corbaConnection
xxxxx@xxxxx (85 bytes) : field connection
Here a two relevant bugs, 6725987 and 6553303. Could they be the source of this problem?
CR 6725987 says ORB.destroy() does not cleanup correctly and ORB customer instances are not garbage collected.
The evaluation for CR 6553303 says one part of this problem is clear: if the ORB successfully opens a connection, but sometime later the connection is no longer usable, it gets stuck in the cache.
Posted Date : 2008-10-23 23:58:38.0
The customer reported that this issue only happens with JDK 1.5. There is no problem on JDK 1.4.2. They also report the issue happens with JDK 1.5 only when IOP is used. The webapp runs fine on JDK 1.5 with TCP.
Posted Date : 2008-10-24 18:38:51.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
While cyclic references themselves do NOT cause leaks, there were other
problems that did cause memory leaks, notably some issues with ThreadLocals,
and some transport resources that were not properly freed. This bug appears
to be simply another manifestation of the problems that we fixed in 6725987.
The fixes for that bug are/will be available in (according to 6725987) in
6u12 and 5.0u20. I suggest that you re-test for this problem with those
releases.
If there are any other issues (such as the WebLogic endpoint info in the
LegacySocketFactory, which was not part of the test for 6725987) please
update this bug or file a new bug.
Posted Date : 2008-10-29 17:21:49.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |