Hi,

I use my own client and server sinks with TCP channels and binary
formatters. My sinks are between formatters and transport sinks. They
exchange messages through request and response headers. They also replace
response and request streams.

I test this with a very small demo program - a SAO SingleCall object is
called on the server. It returns a short string back to the client. I use
port 8099 on my machine

Everything seems to work fine. However, one strange thing happens, for which
I don't have good explanation.

Every time the server object is called a new socket pair is generated. Here
is what happens after 5 calls (info displayed by netstat -a):
TCP    orlin-lpt:8099         orlin-lpt:0               LISTENING
TCP    orlin-lpt:3517         orlin-lpt:8099         ESTABLISHED
TCP    orlin-lpt:3518         orlin-lpt:8099         ESTABLISHED
TCP    orlin-lpt:3519         orlin-lpt:8099         ESTABLISHED
TCP    orlin-lpt:3520         orlin-lpt:8099         ESTABLISHED
TCP    orlin-lpt:3521         orlin-lpt:8099         ESTABLISHED
TCP    orlin-lpt:8099         orlin-lpt:3517         ESTABLISHED
TCP    orlin-lpt:8099         orlin-lpt:3518         ESTABLISHED
TCP    orlin-lpt:8099         orlin-lpt:3519         ESTABLISHED
TCP    orlin-lpt:8099         orlin-lpt:3520         ESTABLISHED
TCP    orlin-lpt:8099         orlin-lpt:3521         ESTABLISHED

Of course after several thousand calls system starts to behave erratically -
refuse calls and return errors. After a couple of minutes those sockets are
gone and the program can work again.

If I don't use my sinks - only a pair of established sockets is created.

I will very much appreciate any hints about what is triggering such behavior
in the Remoting.

Thanks a lot,

Orlin