| Summary | This article describes the problem which causes socket's leak. |
|---|---|
| Article Number | 33631 |
| Environment | Orbix V6.1.x,V6.2.x,V6.3.0,V6.3.1,V6.3.2,V6.3.3,V6.3.4,V6.3.5 All Supported Operating Systems |
| Question/Problem Description | Underlying socket is intermittently not closed after both ORB.shutdown and ORB.destroy is called. |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | Defect ORB-2113 |
| Cause | There is a race condition between client and the server during shutdown: The client ORB initiates orderly closure of existing TCP connections, but doesn't wait for the server to close its end of the connection. The end result is that by the time the server has closed its end of the connection, the client ORB has likely torn down enough of its internals not to be able to process the server's EOF. It is during processing of server's EOF that the client-side socket is closed. |
| Resolution | Fixed in the hotfix V6.3.5.05. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 30 July 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 30 July 2012 |
| First Published date: | 30 July 2012 |
#Orbix
#KnowledgeDocs
