Known Issues

Currently, RTOrb uses no-watchdog when execing PERC 5.3 pvm processes, for example, from scripts. The no-watchdog option might introduce a slight slowdown in native code. An alternative is to set the CPU affinity of pvm, as described in the PERC Ultra Manual section 1.6.
The Real-time CORBA Specification states that if the activate_object_with_id_and_priority () operation is invoked with a different priority to an earlier invocation of one of the create reference with priority operations for the same object, then the ORB shall raise a BAD_INV_ORDER system exception. To actually implement this semantic, the ORB would need to keep a table of created references. The ORB does not currently do this.
RTOrb must be initialised in immortal memory when running as a real-time ORB. The facility to initialise the ORB in scoped or heap memory will be available in a future release of RTOrb. There is a slight memory leak when multiple calls are made to ORB.init ().
When using the run script with the IBM J9 JVM, -Xrealtime must be added to the JVM arguments to avoid a NoClassDefFoundError. This is due to classloader and class resolution issues within the codebase. While this adds real-time classes to the JVM and switches it into RT mode, the ORB will still run in enterprise mode.
Occasionally socket creation on Linux architecture using JDK 1.5.0 or the IBM J9 JVM can take 3 minutes. This is due to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6483406