omniORB 3.0.0 Bug List

  interface I{
    typedef sequence<I> t_I;
  };
  

The ORB uses a select() after the connect() call. Win32 differs from other platforms in that it reports a connect() failure to the select() via the exception fd_set. This was not tested by the ORB.

The connect code in 3.0.0 now turns the socket to non-blocking and set a limit on the time it prepares to wait. Once connected, the socket is turned back to blocking. Unfortunately, the ioctlsocket call is passed the wrong argument which leaves the socket in non-blocking state. The end result is that for CORBA calls with large arguments, the call may fail mysteriously (because windows says the send call would block and the ORB thinks it is wrong because it thinks the socket is blocking).

    interface I;
    typedef I J;
    interface I {};
    interface K : J {};
  

In the case that omniORB receives an object reference claiming to be type "A", and it requires type "B", but it has static knowledge that "A" is not derived from "B", it rejects the object reference. This is incorrect, since the object may actually have type "C", which is derived from both "A" and "B".

A special case of this is an object reference claiming to be a base type of the target type (such as CORBA::Object). Attempts to narrow such a reference would always fail.

Tracing of mutexes and condition variables was accidentally left turned on in include/omniORB3/tracedthread.h. Turning it off gives a significant performance improvement, especially for local calls.

All omniORB libraries need to be rebuilt to make this change; the make rules should do this automatically. The libraries remain compatible with user code, so it does not need to be recompiled. If you have omniORBpy installed, you must also recompile that. Unfortunately, its make rules do not realise that a recompile is necessary (I don't know why), so you must explicitly "make clean" before "make export".

This adds some missing makefiles for a directory that contains tools for building shareable images on the VAX platform. Also, some minor problems with the build of omniORBpy were fixed.

Note: This update is only available through CVS or the FTP snapshots, not via the patch file.