fix: Propagates close() to the underlying DatagramSocket implementation
fixing a leak of fd's while the the objects waiting to be finalized.
This commit is contained in:
parent
72d1b1441c
commit
7c63d5202c
@ -202,9 +202,13 @@ public class ComponentSocket
|
||||
super.close();
|
||||
}
|
||||
finally
|
||||
{
|
||||
Component component = this.component;
|
||||
if (component != null)
|
||||
{
|
||||
component.getParentStream().removePairStateChangeListener(this);
|
||||
component = null;
|
||||
this.component = null;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -136,6 +136,13 @@ public class MergingDatagramSocket
|
||||
@Override
|
||||
public void close()
|
||||
{
|
||||
try
|
||||
{
|
||||
super.close();
|
||||
}
|
||||
finally
|
||||
{
|
||||
|
||||
if (isClosed())
|
||||
{
|
||||
return;
|
||||
@ -144,8 +151,8 @@ public class MergingDatagramSocket
|
||||
logger.info("Closing.");
|
||||
|
||||
// XXX do we want to risk obtaining the lock here, or should we just
|
||||
// let any thread in receive() find out about the close after it's next
|
||||
// timeout?
|
||||
// let any thread in receive() find out about the close after it's
|
||||
// next timeout?
|
||||
synchronized (receiveLock)
|
||||
{
|
||||
receiveLock.notifyAll();
|
||||
@ -161,6 +168,7 @@ public class MergingDatagramSocket
|
||||
socketContainers = new SocketContainer[0];
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* {@inheritDoc}
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user