3 Replies Latest reply on Nov 12, 2004 6:36 AM by wagemono

    MBean always uses local bean despite a lookup on a remote ma

    wagemono Newbie

      I have two identical MBeans on two servers. Each server has access to a different file system, so I need to be able to use each mbean on each machine. It seems to always use the local MBean, despite explicitly looking it up on the other machines JNDI space.

      Is this the same as EJB's defaulting to the local interfaces, despite looking it up remotely? Is it an optimisation method. Is there anyway to stop this?