Help required regarding open TCP connections at server side

Hi,
I am using orbacus 3.3.1 and using the close_cb call back method of OCI. I am observing that the TCP connections are still open at my server side even after the client application is down. I am not sure why this is happening. It would be very helpful if you clarify below points for me.

1) I assume that orb server monitors for the inactive client sessions and closes those connections after the time-out period expires. When the connections closes then server does release those ports used by the inactive client connections. Is my assumption correct?

2) I also assume that when a client closes the connection either
abnormally or normally then the client side TCP connection gets closed and in a case where the closeconnection is not received by the server, then as per my assumption listed as (1) those TCP connections at the server side would be closed. Can I assume this is the default behaviour of the Orbacus?

3) But in my case I am observing the server side TCP connections are still in the ESTABLISHED (when used netstat) state even after the client applications got closed. And I see that these connections are very old may be dates back to several weeks. How can this happen? However I can not see the remote connections status at the client side.

4)Can this be happen in any way because of the OCI call back method close_cb?

5) when I add the client TCP connection
information using the add_closecb method call then does it not release these connections after the client got closed ? does that releases the server ports only after receiving the closeconnection from client?

6) Sometimes I observed that when the client application is killed, then the server is not receiving the client socket close indication. Does that mean that the application is getting killed but the client is not sending the closeconnection? When can this happen?

7) The clients are getting connected through the firewalls. Could these firewalls are blocking the socket close indications?

8) I suspect that the client applications (using jacorb) are not closing the client sockets when they are closing/killing the application. And still the server / client
channel is still up at the TCP level. Do you reckon this is what happening in my case?

9) Can you suggest me why the server side TCP connections are still in ESTABLISHED mode even after the application sessions got closed?

Thanks,

Shyam

_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html