Bug No. |
Description |
TAO486 |
When a fault tolerance client performs a request on an IOGR in a server with a server request interceptor, a core dump occurs when the expiration time has passed. |
TAO484 |
Link errors occur when a CORBA application is built with Unicode
enabled but the idl definitions use non-unicode strings. |
TAO479 |
Calling orb->unregister_value_factory ()
leads to a call to TAO_Valuetype_Adapter_Impl::vf_map_unbind () . In this
method, CORBA::ValueFactory fac is declared and set to the old
ValueFactory. But fac->_remove_ref () is not called to remove the
reference to the old ValueFactory, so a memory leak occurs. |
TAO477 |
The _type attribute in the
Any_SystemException class which inherits from Any_impl is not released in the
free_value () method, which causes a memory leak. |
TAO470 |
The truncation of object key strings in shared memory IOP corbaloc URLs occurs, resulting in OBJECT_NOT_EXIST exceptions when they were used. |
TAO469 |
A BAD_INV_ORDER exception is raised when the get_slot () operation is called on PICurrent for a slot that has been allocated but has not yet been initialised. |
TAO464 |
The tao_idl compiler produces uncompilable code in the case of nested typedefs with the same dimensions. |
TAO449 |
IOGRs are treated as collocated if a non primary profile is process local. If FT is installed and an IOGR contains an FT tagged component it should be marked as collocated if (and only if) the primary is local. |
TAO439 |
A NULL pointer read can occur when using AMI. This is caused by incorrect repository IDs being generated for an AMI reply handler servant for an inherited interface, in the case where the parent interface is defined in another IDL file with a different pragma prefix directive value. |
TAO437 |
tao_idl compiler generates code that does not compile for an unbounded sequence of an array typedef from another module that is partially related to the sequence's module scope. |
TAO430 |
Missing & (amphersand) in ace/TSS_T.cpp. |
TAO423 |
The tao_idl compiler gives a "may not directly support interfaces" error when a derived component directly supports interfaces. |
TAO419 |
Uninitialised "out" parameter for sequence can cause server to core dump. |
TAO415 |
The tao_idl compiler produces uncompilable code when a typedef of another type is used as an attribute on a Valuetype and as an argument to a method on an interface. |
TAO411 |
UIPMC tags changed from TAO-specific to OMG-defined but the old tags are still in use. |
TAO409 |
A oneway operation with a timeout causes the client to crash due to server termination. |
TAO408 |
The ORB::destroy() method should throw BAD_INV_ORDER if called from a request processing thread, instead of performing ORB shutdown. |
TAO407 |
If an exception is thrown during the creation of a new POA and that POA requires its own POAManager, an access violation occurs. |
TAO406 |
A CORBA_MARSHALL exception occurs when processing two or more consecutive inout parameters with type sequence in the case where the size of the first sequence is decreased on the server side. |
TAO397 |
FT_ClientRequest_Interceptor adds the request service context even if the target is not an IOGR. |
TAO361 |
tao_idl compiler generates a header file which itself includes header files which do not exist, so a C++ compilation error occurs. This is as a result of an error with INCLUDE_PIDL. |
TAO355 |
tao_idl compiler generates code for typedefs of strings of the same length which causes a link error with the same TypeCode definition. |
TAO303 |
Location forwarding stores all forward references up to the point of memory exhaustion. |
Bug No. |
Description |
TAO251 |
In a FT application using AMI, two consecutive requests have the same retention_id and expiration_time when the first request is not answered before the invocation of the second request. |
TAO249 |
When a FT request causes a user or system exception, the retention_id and expiration_time are not updated for the next request. |
TAO238 |
Messages are fragmented when a TAO server receives a datastream containing more than one request in immediate sequence on one connection. |
TAO178 |
A single object reference is equivalent to a fault tolerant group reference with the single object set as primary - this contradicts the CORBA specification. |
TAO170 |
TAO has no support for LOCATION_FORWARD_PERMANENT exceptions and replies. |
TAO135 |
Optimisation collocations Thru POA does not work when using corbaloc URLs referring to collocated objects. |
TAO87 |
When a CORBA::Any which contains a valuetype is exchanged between TAO and JacORB, a CORBA::MARSHAL exception is raised because the ValueModifier in TAO type codes is 4 bytes rather than 2. |