2 Replies Latest reply on Apr 5, 2006 2:30 AM by igald

    Embedded JMX and JAR usage

    igald

      Hi, Two questions:
      1. I have noticed that the transporter server requires the JMX jar in order to load properly. Problem is that the server runs in a JMX environment, and the Jboss JMX could conflict with the other JMX jar. Is there a way avoid loading the Jboss JMX? Why does it need it?

      2. The documentation does not state the mandatory jars required for loading transporter client and server. Which are the ones? I don't want to load them all..

      Thanks in advance,

      Daniel

        • 1. Re: Embedded JMX and JAR usage

          The TransporterServer automatically tries to load a remoting detector (to allow for autodiscovery for transporter clients). JMX is used to tie detectors and remoting servers together. There is not dependancy on JBoss JMX, so any JMX implementation jar on the classpath should work.

          This tie between detectors and servers being reliant on jmx will be removed in the future.

          As for jars that are required, we don't have formal documentation for this yet (http://jira.jboss.com/jira/browse/JBREM-311). The transport implementations are lazy loaded, so won't need transport specific jars unless using that transport (e.g. only need tomcat jars if using http invoker).

          • 2. Re: Embedded JMX and JAR usage
            igald

            Thanks, great news to me.

            Daniel