View RSS Feed

JNDI

JNDI Best Practices

Rate this Entry
by , 07-07-2012 at 05:29 PM (1926 Views)
Remote JNDI lookup are considered as quite expensive sort of remote method call. For performance of JNDI lookup, applications will be doing it once. Hence home handles caching will be improving the performance in this kind of situation. It is also an expensive task to make a connection with JNDI. Caching of these context references will be improving the performance of applications.

One class is used for abstraction of all usage of JNDI and also EJB home object lookup, initial context creation and EJB object re-creation complexities are hidden. Such objects could be resued by various clients so that the complexity of code could be reduced and single control point could be provided, and performance could be improved by giving out a caching facility.

Either java.rmi.Remote or java.io.Serializableor shall be implemented by the object present in JNDI tree. Both JBoss and WebLogic use the JNDI services that are non persistent. Such in-memory technique would be increasing the retrievals performance. Reliability of such services can be increased when vendors rely at replication across the nodes of cluster. Load balancing and fail over of naming services will be provided in this way.

Submit "JNDI Best Practices" to Facebook Submit "JNDI Best Practices" to Digg Submit "JNDI Best Practices" to del.icio.us Submit "JNDI Best Practices" to StumbleUpon Submit "JNDI Best Practices" to Google

Categories
Tutorial

Comments