Skip to main content

Problem

  • Product Name: Borland Enterprise Server
  • Product Version: 5.2.1
  • Product Component: EJB, Naming, Osagent
  • Platform/OS Version: All
  • JDK/Compiler Version: JDK 1.4.1

BES521 EJB Bean instance failover requires OSAGENT when using implicit clustering

Resolution

When using implicit clustering ( vbroker.naming.propBind=1 ) to cluster EJB intances the OSAGENT is required if failover is desired at the bean instance method invocation level. This is becuase EJBHomes and the home-created Beans are registered in the OSAGENT. Only EJBHomes are registered in JNDI.

If disabling usage of the OSAGENT (e.g. setting vbroker.orb.enableLocator=false and using java.naming.providerURL or corbaloc to bootstrap beans into JNDI/NameService) since the EJB"s home interfaces are registered with the JNDI a client must use logic to obtain a new EJBHome interface, re-create a bean and call the remote methods again.


#Security
#BES
#EJB
#failiover
#AppServer
#VisiBroker
#osagent