| Summary | How to close the client connection to the Orbix 3 daemon |
|---|---|
| Article Number | 16929 |
| Environment | HP-UX 11.0 Orbix 3.x |
| Question/Problem Description | How to close the client connection to the Orbix 3 daemon How to configure Orbix 3 in order to have the client connection to the Orbix daemon closed automatically? How to close the Orbix 3 client connection to the daemon programmatically? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | Orbix 3 clients do not automatically close the connection to the Orbix daemon. These connections need to be closed explicitly. Orbix 3 Java provides the IT_KEEP_ALIVE_FORWARDER_CONNECTION configuration variable which can be set to false in order to close the connection to the Orbix daemon. This variable can be used in the following ways:
Orbix 3 C does not provide a configuration variable, so the only way to close the connection to the daemon is by explicitly closing the connection in the client code.To close the client-daemon connection, you must specifically bind to the daemon first, then close that proxy's channel. The following is some sample code that will illustrate how to close the client-daemon connection with the CORBA::Orbix.closeChannel() API. #define WANT_ORBIX_FDS // require for _fd() int main () { // Client's proxy to the server object |
| Workaround | |
| Notes | Alternatively, the client connections to the daemon can be closed by using an Orbix smart proxy implementation which explicitly closes the connection through IT_daemon::_closeChannel() after each call to the Orbix daemon. |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#Orbix
#KnowledgeDocs




