| Bug No. | Description |
|---|---|
| RTJ1043 | Fix behaviour of locate forward with multiple redirects. |
| Bug No. | Description |
|---|---|
| RTJ1040 |
Fix for locating child poas in find_POA> method.
|
| RTJ1031 | Use the RTOrb IOR Decoder in preference to the OpenFusion one when available, to ensure that all IOR profiles are displayed. |
| RTJ1029 | Fix marshalling with redirected object references. |
| Bug No. | Description |
|---|---|
| RTJ1025 | Fix ForwardRequest issue which causes an OBJECT_NOT_EXIST exception. |
| Bug No. | Description |
|---|---|
| RTJ1021 |
When a client makes a call to an object and the call is redirected,
and the client then calls object_to_string () for the
object reference, then the returned stringified IOR refers to the
original object, not the object to which the call was redirected.
|
| RTJ1004 |
Fix for LynxOS compilation issue by supplying a dummy java.applet.Applet class.
|
| RTJ858 | Timeout policies now take account of reinvocations and are no longer reapplied from the start. Note that this change is only effective under Enterprise and Soft Real-time modes. |
| Bug No. | Description |
|---|---|
| RTJ999 | Fix JacORB IDL compiler issue with constant long long generation. |
| Bug No. | Description |
|---|---|
| RTJ994 | Fix buffer allocation increment to avoid OutOfMemory. |
| RTJ988 |
Fix timeout policies issue with validate_connection ().
|
| RTJ987 | Fix to avoid resource starvation in POA. |
| RTJ976 | Fixes to unmarshal data correctly when swapping. |
| Bug No. | Description |
|---|---|
| RTJ960 |
Previously, if a server closed a connection or crashed before a client sent a request,
the client could not determine whether or not the connection was usable, and it sent
the request regardless. This caused an automatic retry of the request and an
incorrect completion status.
The client now correctly detects the state of the connection before sending, and avoids spurious retries. |
| Bug No. | Description |
|---|---|
| RTJ970 | Fix calculation of incorrect context sizes under GIOP 1.0. |
| RTJ940 / 941 | Fix nested value types issue which caused a CORBA.MARSHAL exception when attempting to use the OutputStream class to deserialise a value. |
| RTJ933 | Fix to handle empty sequences when reading and writing arrays. |
| RTJ932 |
Remove unnecessary logging of RemarshalExceptions.
|
| RTJ927 |
Catch a java.nio.channels.NotYetConnectedException and propogate a COMM_FAILURE to a client when the server crashes just before the client invokes it.
|
| Bug No. | Description |
|---|---|
| RTJ917 | Fix so that socket creation is not synchronised if the ORB is running in soft real-time or enterprise mode and not in scoped memory. |
| RTJ912 | Fix fatal error when freeing InvocationContexts. |
| RTJ910 | Improve handling of valuetypes to overcome CDR Stream performance issue. |
| RTJ906 | Fix issue where the RTCorbaPriority service context was being read with the wrong byte order. |
| Bug No. | Description |
|---|---|
| RTJ897 | Fix issue so that the byte order of streams is no longer ignored when skipping over service contexts. |
| Bug No. | Description |
|---|---|
| RTJ925 | Fix issue where an invocation on a new servant with the same object ID as a deactivated servant is incorrectly processed by the deactivated servant. |
| RTJ887 | Fixes for Any to work with the latest version of the IDL compiler (V080711) and corrections for input stream creation. |
| RTJ882 | Fixes to improve reliability of POA destruction. |
| Bug No. | Description |
|---|---|
| RTJ861 | Fix minor code on COMM_FAILURE exception. |
| RTJ848 | Fix issue where a CDR InputStream using the custom endian function fails to unmarshal a long long data type correctly. |
| RTJ811 |
Fix so POA listener threads will accept requests when POAManager transitions to the active state rather than when ORB.run is called. This complies with CORBA Specification version 3.1, 08-01-04, sections 8.2.5.3 and 15.3.2.1.
|
| RTJ805 | Fix issue where RTOrb returns an OBJECT_NOT_EXIST exception when invoking a local object which was activated with USER_ID in a child POA. |
| Bug No. | Description |
|---|---|
| RTJ787 | Fix an interoperability issue where out, inout and return values are garbled when passing long long data from an RTOrb client to a TAO server. |
| RTJ784 | Fix an issue where corbaloc fails when a corbaloc GIOP 1.2 version is explicitly specified and correct alignment issues with longlong bytes and corbaloc. |
| Bug No. | Description |
|---|---|
| RTJ777 | Fix issue where the skeleton for the first servant activated is the only skeleton that the POA can see, when the USER_ID policy is set on that POA. |
| RTJ754 |
Fix issue where an application fails to exit properly and appears to hang intermittently in the POA_Destroyer thread.
|
| RTJ184 | Fix to remove the hardcoded child POA limit of 31. |
| Bug No. | Description |
|---|---|
| RTJ743 |
Fix to warm up a connection and reduce the initial latency of a _validate_connection () call.
|
| RTJ728 |
The RTOrb examples do not call _validate_connection () correctly.
|
| Bug No. | Description |
|---|---|
| RTJ677 | A JacORB client connects to an RTOrb server with a transient POA. The RTOrb server crashes and restarts on the same port with a different POA name. The JacORB client reconnects to the old IOR and receives a CORBA.MARSHAL exception when an OBJECT_NOT_EXIST exception is expected. |
| RTJ497 | The following message is seen in log files: A high number of class com.prismtech.ofj.orb.OutputStream objects reached, probable memory leak. |
| Bug No. | Description |
|---|---|
| RTJ659 | When an RTOrb client invokes a method, which takes an object and a value type, on a JacORB server, the RTOrb client receives a CORBA.MARSHAL exception. This only occurs when the JacORB server has an IOR interceptor registered. |
| RTJ658 |
A NullPointerException occurs when an attempt is made to obtain the effective component from the ClientRequestInfo object inside the ClientRequestInterceptor.send_request () method.
|
| Bug No. | Description |
|---|---|
| RTJ634 | When a ForwardRequest exception is thrown in the ClientRequestInterceptor, the RTORB did not handle the ForwardRequest exception and continues to route the remote invocation to the old CORBA servant. |
| Bug No. | Description |
|---|---|
| RTJ618/619 | When an IOR Interceptor is registered on a CORBA server and a ClientRequestInterceptor is registered on a CORBA client, an ArrayIndexOutOfBoundsException occurs on the server side, which causes an INV_OBJREF on the client side when an object is activated and deactivated several times. |
| RTJ611 | When the POAManager is set to the inactive state, an AdapterInactive exception is not raised as expected when a subsequent attempt is made to change the state of the POAManager. |
| RTJ610 | When the IdUniquenessPolicy is used and a CORBA server starts with two different object ids pointing to the same servant, an RTOrb client receives an OBJ_ADAPTER exception when it attempts to invoke a method on the server. |
| RTJ608 | When an RTOrb client sets the messaging policy to SYNC_NONE on an object that contains a oneway method, a CORBA server does not receive an invocation from the client. |
| Bug No. | Description |
|---|---|
| RTJ602 | When a JacORB client connects to an RTOrb server with a relative roundtrip timeout policy, a java.lang.ArrayIndexOutOfBoundsException occurs in the RTOrb server when the client uses corbaloc to connect to the server, but does not occur when the client uses a stringified IOR. |
| RTJ596 | A CORBA.INTERNAL: Channel is null exception is displayed when a client invokes a method on a server, the server sleeps for 5 seconds and the client is killed during the sleep. |
| RTJ595 |
An ArrayIndexOutOfBoundsException occurs in the get_effective_component logic when an RTOrb client attempts to invoke a method on the object reference of a locator in a TAO server.
|
| RTJ590 | When a ServantLocator throws a ForwardRequest exception to a client with a null IOR, the client hangs indefinitely. A TRANSIENT exception should be thrown. |
| RTJ541 | When an RTOrb client invokes a method on a TAO locator server and the TAO locator throws a ForwardRequest exception containing an IOR hosted by an RTOrb server, the relative roundtrip timeout policy of the RTOrb client fails. |
| Bug No. | Description |
|---|---|
| RTJ564 | When an RTOrb server registers a ServerRequestInterceptor, activates a CORBA servant and invokes a method on that CORBA servant, a NullPointerException occurs. |
| RTJ563 |
A NullPointerException occurs when an attempt is made to extract the effective
component from the ClientRequestInfo object inside the
ClientRequestInterceptor.send_request () method.
|
| RTJ562 | The Trading Service does not run on the port specified in the TradingService CORBA tab in the OpenFusion AdminManager GUI because RTOrb does not set the etf port properties. |
| Bug No. | Description |
|---|---|
| RTJ548 | When a persistent RTOrb server activates a servant and writes an IOR to a file, the server successfully receives a method invocation with no parameters but the client receives a CORBA.INV_OBJREF when a method with an Object as a parameter is called on the server. |
| RTJ541 | An RTOrb client does not receive a CORBA timeout exception when using the relative round-trip policy and the specificed time has expired. |
| RTJ538 | An RTOrb client invokes an operation on an object in a ForwardRequest server. The ForwardRequest server throws a ForwardRequest exception to the client and the client reinvokes the operation on the actual object. When the server which contains the actual object is terminated, a subsequent client operation invocation fails with a COMM_FAILURE exception. The expected behaviour is for the client orb to reinvoke the operation on the object in the ForwardRequest server. |
| Bug No. | Description |
|---|---|
| RTJ539 | If PortableServer.idl is included in an idl file, a syntax error occurs when parsing the idl. |
| Bug No. | Description |
|---|---|
| RTJ512 | When a TAO server throws a ForwardRequest exception to transparently redirect an RTOrb client to another server, a "BAD_PARAM: IOR shorter than expected" exception is raised by the RTOrb client. |
| RTJ510 | When an RTOrb server throws a ForwardRequest exception to a client application, a "POA is marshalling unknown" message is seen in the server and a CORBA.UNKNOWN exception is caught by the client, when the client invokes the RTOrb server that threw the ForwardRequest exception. |
| RTJ507 | When a client resolves to a server with a persistent object reference, using a corbaloc formatted string after the server has been killed and then restarted, an unexpected end-of-file exception occurs. |
| RTJ505 |
The RTOrb server hangs and never exits after orb.destroy () is called, in both enterprise and soft real-time mode.
|
| RTJ489 | An RTOrb server throws an OBJECT_NOT_EXIST exception to a JacORB client when the client uses a corbaloc to connect to the server. |
| Bug No. | Description |
|---|---|
| RTJ501 |
When and object reference obtained from a servant is cast to org.omg.CORBA.portable.ObjectImpl on the server side, org.omg.CORBA.portable.ObjectImpl._ids()[0] returns an empty string or null, when an interface repository ID is expected.
|
| RTJ500 | An RTOrb client receives a CORBA::Unknown exception during first time invocation when a Client Interceptor is registered in the client application. The client does not receive an exception on subsequent invocations. |
| RTJ497 | A "probable memory leak" warning is received when a high number of OutputStream objects are used. |
| RTJ496 |
RTOrb receives an org.omg.CORBA.portable.RemarshalException warning message when an RTOrb client invokes a method on an object in a persistent TAO server which was narrowed using the unchecked_narrow method
|
| Bug No. | Description |
|---|---|
| RTJ490 | An interoperability problem occurs between a TAO client and an RTOrb server when the client uses a corbaloc to connect to the server. |
| RTJ489 | An interoperability problem occurs between an RTOrb Server and a JacORB Client when the client uses a corbaloc to connect with the server. |
| RTJ481 | A CORBA MARSHAL exception is raised when an object reference, which was returned from a TAO server, is passed to a remote method. |
| RTJ480 |
rootPOA.the_parent () raises a NullPointerException when the method is expected to return NULL.
|
| RTJ479 | An interoperability problem occurs between an RTOrb client and a TAO server when the client uses a corbaloc that uses localhost as the hostname to connect to the server. |
| RTJ477 | When a client registers a client interceptor, an infinite loop occurs when the client tries to invoke a oneway call on a server. |
| RTJ473 |
After a client invokes a remote invocation on a server one or more times, when deactivate_object() and activate_object_with_id() using the same object id are called on the server, an ObjectAlreadyActive exception is incorrectly received.
|
| Bug No. | Description |
|---|---|
| RTJ464 |
narrow () fails when using "localhost" in a client side corbaloc.
|
| RTJ459 |
After POA.deactivate_object () is called to deactivate a CORBA servant, the server incorrectly continues to receive requests from the client.
|
| RTJ448 | Unexpected exceptions occur during first time invocation in a client process when the server is not running. |
| RTJ440 | ClassNotFoundException occurs when attempting to register an ORBInitializer. |
| RTJ433 | The distribution contains a pre-JDK1.5 version of jndi.jar which does not include the latest version of javax.naming.NameClassPair. This file should be removed from the distribution. |
| RTJ422 | An IllegalAssignmentError occurs when testing Object Key Mapping in hard real-time mode. |
| Bug No. | Description |
|---|---|
| RTJ431 | org.omg.CORBA.BAD_PARAM exception when narrowing an object derived from a corbaloc. This is resolved with the Object Kep Mapping functionality added. |
| RTJ430 |
CORBA specification and the Java Mapping are inconsistent with respect to the spelling of
_set_policy_overrides versus _set_policy_override method. Both are supported.
|
| RTJ415 |
list_initial_services() produces a org.omg.CORBA.NO_IMPLEMENT
exception. This is now implemented.
|
| Bug No. | Description |
|---|---|
| RTJ417 |
With JacORB, org.omg.CORBA_2_5.ORB.id () returns a string containing the JacORB version whereas with RTOrb, an empty string is returned.
|
| RTJ416 |
An InvalidName exception is raised when resolve_initial_references () is called on an orb after a corbaloc is supplied as an argument to -ORBInitRef.
|
