Back to Main PageBack

OpenFusion TAO Fixed Bugs

Fixed since 1.5.1.1

Bug No. Description
TAO780 Duplicate of TAO753.
TAO774 Fix XMI generation for module reopening.
TAO768 Fix DAnCE issue with NodeApplication destructor which can cause a process to crash.
TAO753 Increased ACE_DEFAULT_MAX_SOCKET_BUFSIZ to 262144 to allow socket memory buffers sufficient size for application use. Prevents deadlocking of SPCR144 - Fault detector detects a supervision failure despite that it is still alive.
TAO745 Fix issue where upon completion of a server request, the thread current is copied to the request current as expected but is then not cleared.
TAO739 Fix generation of association for sequences and arrays.
TAO739 Fix xmi.id generation so they are unique within a single XML document and contain only characters allowed in XML.
TAO739 Add XMI generation for native types.
TAO739 Fix XMI generation for forward declared interfaces / structs / unions / exceptions / valuetypes / components / eventtypes.
TAO726 Fixed an issue where a NodeApplication did not properly clean up homes created during plan deployment.
TAO720 Fix so that the idl compiler detects bounds violations for the string type.
TAO718 Fix for incorrect handling of artifact location for valuetype factories.
TAO717 Changed the behaviour of the Relative Roundtrip Timeout policy such that the timeout will bound the entire user invocation including any transparent re-invocations following LOCATION_FORWARD or other retryable exception conditions.
TAO701 Fixed improper use of ACE_Vector in the dance DomainApplicationManager_Impl.
TAO688 Fix issue where NodeApplication_Impl object is deleted before all incoming requests on that object have completed.
TAO684 Fix to only mark the client connection handler as registered with the reactor if the registration has succeeded when using the RW strategy in conjunction with the option to clean up closed connections. This prevents potential errors during ORB shutdown.
TAO675 Change use of the OMG defined IOP namespace in code to be scoped as ::IOP to avoid conflicts with potential user modules called IOP.
TAO669 Fixed compilation failure when an idl3 file includes idl2 files that use CORBA TypeCode.
TAO661 Fixed an error with the idl3_to_xmi tool when a sequence is declared in an included IDL file.
TAO655 Fixed an INTERNAL exception when CSD is used and the send_request server request interceptor point is invoked.
TAO654 Fixed the idl3_to_xmi tool to generate UML:Association values for IDL sequence bounds.
TAO642 Add support for access to the CORBA standard defined methods of PortableServer::Current within servant invocations dispatched by the Custom Servant Dispatch framework Thread Pool Strategy reference implementation.
TAO638 Fix the idl3_to_xmi tool to generate UML:Association values for IDL array dimension sizes.
TAO581 Fix for a "Type not supported" error when DAnCE attempts to parse a plan containing an <alias> element.
TAO577 Fix for mpc files which need to inherit from tao_output.mpb in order to install a symbolic link to built libraries in the ACE_ROOT/lib directory.
TAO576 Add missing files to the tao151/TAO/CIAO/tools/Config_Handlers/DynAny_Handler directory.
TAO572 DAnCE NodeManager and ExecutionManager now use rebind instead of bind when registering its reference in the NameService at start-up.
TAO570 An Error Unknown element 'alias' message occurs when parsing DeploymentPlan with the <alias> element.
TAO536 TAO does not correctly duplicate the second and subsequent indirect typecodes.
TAO532 The TAO IFR returns the incorrect length of an array of a typedef.
TAO527 Repeated typecodes cannot be processed by TAO when TAO interoperates with JacORB, which generates indirect typecodes.
TAO522 The tao_idl compiler can cause an infinite loop during the lookup of certain identifiers within local modules, and searching in parent scope for identifiers that were not found in local modules is done in a non-CORBA compliant way.
TAO505 The tao_idl compiler generates incomplete code for a const long defined in an idl interface.
TAO498 When a ServantLocator throws a ForwardRequest exception to a client with a null IOR, the client hangs indefinitely. A TRANSIENT exception should be thrown.
TAO497 When the Request_Interceptor_Flow example is modified to register interceptor B, the test sends an exception to the client, when the expected behaviour is to enter an infinite loop.
TAO495 A memory fault occurs when an OBJ_ADAPTER exception is thrown by a ForwardRequest TAO server to a TAO client to indicate that no working server is available.
TAO483 When SSL is activated in TAO, a TAO server can make invocations over SSLIOP to a client but cannot make invocations to a client over plain IIOP. This is because once SSL is activated in TAO, the TAO application attempts to use SSL connections only. A CORBA::NO_PERMISSION exception is thrown if SSL is not in use and the SSLNoProtection flag is not specified. A CORBA::INV_POLICY exception is thrown if there is no SSL port and the SSLNoProtection flag is not specified.
TAO418 When a struct that is used within a valuetype is typedef'd, the IDL compiler fails to generate Arg_Traits template specialisation code for the typedef'd type, causing compilation to fail.
TAO416 When a typecode from an enumeration is included in a struct, the IDL compiler fails to generate Arg_Traits template specialisation code for the typedef'd type, causing compilation to fail.
TAO414 GIOP request message format for no-arg method invocation should not be alignment-packed; this causes interoperability problems with Orbix.
TAO413 In the TAO_Marshal_Object::perform_skip () method, the handling for a valuetype is not implemented; a valuebox should be handled in the same way as a regular valuetype.
CCM56 The dance --gen-obj-key argument command returned a full corbaloc rather than an object key.
CCM57 The dance --gen-obj-key argument was not accepted by dance. The tao_idl3_to_idl2, cdmw_idl3_to_idl2, and idl3_to_xmi tools were not included in the distribution.
CCM68 DAnCE was using an different definition of the exception Components::InvalidConfiguration to Cardamom. These have been brought into sync. Exception handling on CCM_Object::configuration_complete calls has been corrected.
CCM60 Corrected handling of initial reference value ProcessDestinationNC in ServerActivator_Impl::create_component_server. The value of this reference is now interpreted as the NamingContext that ComponentServer references are bound directly into.
CCM61 Corrected the format of deployment plan component name bindings in the nominated name service.
CCM62 NodeManager level plan NamingContexts are now created (and rebound) in nominated target name services at the time of the manager creation rather than on first preparePlan invocation.
CCM29 Pluggable log mesage backend support is corrected to match requirements.
CCM66 dance command line options have been corrected to match the format documented in the wiki requirements. N.B. - The short option to nominate a CDR encoded deployment plan file to the planlauncher tool has been changed from '-c' to '-d'. See updated Wiki for details.
CCM72 Enable dance to load deployment plan files specified by a path relative to the current working directory. Previously this was not possible.
CCM73 Fixed the bug that meant that using the comman dance --gen-object-key wasn't producing any output.
CCM74 Move the operation Plan_Launcher_Base_Impl::read_cdr_plan_file out of protected scope so that it can be used programatically.
CCM76 Fixed a bug where use of the dance -n command could encounter a segmentation fault as a result of use of an unitialised ORB pointer.
CCM69 Fixed handling of GNU format options in the plan launcher. Fixed handling of the -d plan launcher option. Fixed errors when the --stop-plan option is used. Fixed exception encountered when ExecutionManager -r is used. Fixed the problem where the --process-ns [ior_file] option did not save the name service IOR to the nominated file. Fixed a problem where the ExecutionManager -e option didn't save the service IOR to the nominated file.
CCM79 Fixed an exception during POA initialisation when the options dance -e -p are used.
CCM80 Provide the log priority in dance logging output.
CCM45 Handle the exception identifying an incorrect path to an artifact library correctly in dance.
CCM71 Improved error reporting in dance when plan data is incorrect.
CCM75 Utilise an unchecked narrow when connecting a publisher port to a consumer port in dance. This prevents an execption in the event that the consumer does not yet exist.
CCM77 Change dance to pass all values of cdmw.config configuration values on all calls to CDM.
CCM77 Method Plan_Launcher_Impl::load_xml_plan made public static to enable loading of an XML plan file.
CCM83 Fix ACE_ASSERT during NodeApplication_impl::createComponent in dance.
CCM82 Fixed a bug where the dance ExceutionManager instance was not being bound into the name context specified by the initial reference DoaminNC.
CCM85 Introduced a check on the value of the intial reference ProcessDestinationNC at dance start-up. If this initial reference is not set then dance will exit with an error.
CCM86 Fix a bug in option parsing by dance.
CCM88 Fixed a bug where starting dance with the --rebind-plan-ns(-r) option and without the --create-plan-ns(-c) did not produce the expected error message.
CCM90 Enable dance to load and start more than one plan on start-up.
CCM91 Fixed a problem where no appropriate error message is produced when the dance plan launcher is supplied with an incorrect file name value for the --read-plan comand line option.
CCM93 Fixed a problem where no appropriate error message is produced when the dance plan launcher is supplied with an incorrect IOR value for the --em-ior comand line option.
CCM94 Fixed a problem where the dance option --log-level did not suppress trace level messages during argument parsing.
CCM96 Fixed a general problem with dance such that supply command line options that required argument values without values was not reported as an error.
CCM97 Fixed a problem within dance where a StopError was raised on calling DomainApplicationManager::destroyApplication().

Fixed in 1.5.1.1

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.

Fixed in 1.5.1.0

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.

PrismTech TOP
Top