1 Reply Latest reply on May 26, 2004 3:51 AM by Juha Lindfors

    Architecture of JMX and MBeans

    enterprisejavabones Newbie

      Hi,

      I'm fairly new to JMX so forgive me if my question is naive.

      I'm currently writing an application that is required to maintain multiple open socket connections (at all times).

      Data received in from the socket connections will be persisted to DB via EJB's.

      I'm currently trying to implement the Socket Communication portion as an MBean, where my deployed MBean will open the sockets and wait for incoming data. As data arrives, the MBean looks up my EJB's using JNDI and persists the data.

      My question, is the MBean life cycle similar to that of EJB's? In that will the MBeans get passivated (or something similar)? Also is there concurrency with MBeans, in that are there multiple instances running at any point in time (like EJB's)? What happens in the case of a cluster?

      My concern is that in the case of passivation any open connections created by the MBean will be closed. This would prove disastorous for us.

      TIA for your help.

        • 1. Re: Architecture of JMX and MBeans
          Juha Lindfors Master

           

          "EnterpriseJavaBones" wrote:

          My question, is the MBean life cycle similar to that of EJB's?


          No.


          In that will the MBeans get passivated (or something similar)?


          No.


          Also is there concurrency with MBeans, in that are there multiple instances running at any point in time (like EJB's)?


          No, single instance per object name.


          What happens in the case of a cluster?


          Default behavior is non-clustered. Single instance in a single node.