[omniORB] Assertion failure in giopImpl12 (omniORB4)

[Chris Newbold]

On Thu, 2002-12-19 at 05:53, Duncan Grisby wrote:
> On Friday 6 December, Chris Newbold wrote:
> 
> > The client uses N to connect to M and fails; then N + 1, N + 2 and so
> > on. Eventually N == M and the client connects his socket back on itself!
> > In the tracing you can see the client connect and send a 96-byte request
> > which he promptly receives back again :-)
> 
> I've finally had a chance to check in a fix for this. I hope it works
> in your situation. It just responds to an unexpected request message
> with a message error, rather than trying to detect your particular
> situation.

I suspect that this is how omniORB 3 managed to avoid the same problem.

> I wonder if it's really meant to be OK to connect a socket to itself.
> I can't imagine that's a particularly useful thing to be able to do.

Neither can I. That's why I wondered if omniORB should explicitly avoid
this problem...

-- 
====( Chris Newbold  <cnewbold@laurelnetworks.com> )==========================
      Laurel Networks, Inc. voice: +1 412 809 4200 fax: +1 412 809 4201
"If you fool around with a thing for very long you will screw it up." --Murphy
------------------------------------------------------------------------------