Product: OpenFusion JacORB
Version: 2.1.3.2 & 2.1.3.3
Description:
JacORB 2.1.3.3 fixed Defect id: 01DP
When a transient consumer is shut down and a new consumer started on the same port, when an event is sent, the event is received twice by the new consumer.
Previous to this bug fix a transient consumer could restart with the same identity as an old one which was clearly incorrect.
In JacORB 2.1.3.3 this can no longer happen.
Resolution:
In JacORB an object is uniquely identified by its object key. If you are using a persistent object you need to configure the implname property to a unique name which will ensure that it stays persistent. For a transient object the whole object key is now randomly generated. The problem occurred because a transient server was being used. Clients would connect to the server using a corbaloc string which includes the object key as part of the string.
When the transient server was restarted with JacORB 2.1.3.3 this object key changed due to the bug fix.
The workaround was to use the proprietary JacORB method addObjectKey method to map the object key generated by JacORB to a name. This meant that when the server restarts, although the object key is regenerated, it is mapped to a name which will never change. This name can be used in the corbaloc string to contact the server.
#jacorbconsumer
#KnowledgeDocs
#OpenFusion
