Re: bidirectional omniORB, NAT and idle timeouts
Duncan Grisby via omniORB-list <[email protected]>
| Newsgroups | gmane.comp.corba.omniorb.user |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2026-08-13 at 15:42 +0200, Michael Teske via omniORB-list wrote: [...] > Our architecture heavily relies on callback object, and with > bidirectional we don't need to keep a listen port on the client open > - which often leads to security discussions these days. > > So we finally went live with this configuration, and all worked fine, > except: The connections from the client to the server processes goes > over NAT, and the NAT server they use disables idle connections after > about 45 minutes. [...] > Is there any solution for this available yet? I thought about > hacking TCP_KEEPIDLE on linux into the socket options, but before > doing that I thought I ask here first. I don't think you are likely to have much luck with doing that. It might make it somewhat less likely for the NAT server to drop your connection, but sooner or later something will cause the connection to drop. A more robust solution would be to periodically make an explicit CORBA call from the client to the server, re-sending the callback object reference. Normally that periodic call would reuse the existing connection, but if the connection is dropped for any reason, a new one will be opened. It is important to re-send the callback because bidirectional callbacks are only allowed on the same connection that was used to receive the object reference. Duncan. -- Duncan Grisby <[email protected]> _______________________________________________ omniORB-list mailing list [email protected] https://www.omniorb-support.com/mailman/listinfo/omniorb-list