Orbix Comet always keep a connection between the bridge and Orbix daemon, and does not close it unless the Orbix process exits.

If multiple instances of Microsoft client are deployed, each one with its embedded Comet bridge, this might cause the Orbix daemon run out of file descriptors. One solution will be to configure Orbix daemon to use Active Connection Management (ACM), so that the least used connections are dropped, and reused. The Comet bridge will re-establish these connections to the daemon on first access, so this setup will be transparent to Microsoft clients using Comet.