Problem: Product Name: VisiBroker Product Version: 4.x, 5.x Platform: ALL Component: Naming Service This problem is reported on VBE 5.1 in Solaris, but also reproduced in Windows using VBE 5.2. The cause of the problem is that the stale references in LDAP are not been cleaned. This is similar to an issue reported for F25697: VB 4.x: Executing unbind from nsutil / naming service does not unbind the reference using LDAP. Failure 25697 is fixed in VBE 5.1.p3. However, using this patch results in CORBA::NO_IMPLEMENT exceptions when the Server tries binding to the Name Service. The full server error/exception: # vbj -DSVCnameroot=NameService Server org.omg.CORBA.NO_IMPLEMENT: minor code: 0 completed: No at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:232) at com.inprise.vbroker.orb.SE.read(SE.java:28) at com.inprise.vbroker.orb.DelegateImpl.handleReply(DelegateImpl.java:793) at com.inprise.vbroker.orb.DelegateImpl.invoke(DelegateImpl.java:679) at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:454) at com.inprise.vbroker.orb.RequestImpl._invoke(RequestImpl.java:208) at com.inprise.vbroker.orb.RequestImpl.invoke(RequestImpl.java:134) at org.omg.CosNaming._NamingContextStub.bind(_NamingContextStub.java:41) at Server.main(Server.java:36) Problem can be reproduced by using the "basic/bank_naming" example with the following VisiNaming properties: vbroker.naming.propBindOn=1 vbroker.naming.enableClusterFailOver=true vbroker.naming.smrr.pruneStaleRef=1 vbroker.naming.backingStoreType=JNDI vbroker.naming.loginName=uid=admin,ou=Administrators, ou=TopologyManagement,o=NetscapeRoot vbroker.naming.loginPwd=admin vbroker.naming.jndiInitialFactory=com.netscape.jndi.ldap.LdapContextFactory vbroker.naming.jndiProviderURL=ldap://ABAGMAR.sm.inprise.com.:389/o=NetscapeRoot vbroker.naming.jndiAuthentication=simple vbroker.naming.cacheOn=1 vbroker.naming.cacheSize=5 The problem can also be reproduced using the "ins/implicit_clustering" example. Resolution: The problem is seen only when Implicit Clustering is used (i.e. vbroker.naming.propBindOn=1 ). When using Explicit Clustering, there is no bind problem and also no stale entries in the LDAP. Failure 37775 is fixed in VBE 5.1.p13 and later versions of VisiBroker.
↧