1 2 Previous Next 17 Replies Latest reply on Sep 23, 2010 4:47 PM by mrbeagle Go to original post
      • 15. Re: Version 2.1.1 and Remote JMX
        timfox
        timfox Sep 15, 2010 3:00 AM (in response to timfox)

        Also, if you have a machine which needs to be accessible from other boxes, why would you set the JNDI server to only be listening on localhost? This won't be accessible from other machines.

         

        If you don't want JNDI just remove it from the beans.xml as mentioned in the user manual.

          • Actions
        • 16. Re: Version 2.1.1 and Remote JMX
          hughbragg
          hughbragg Sep 17, 2010 2:05 AM (in response to timfox)

          Yes I did use those parameters Tim. Did you try to repeat it?

          If you like, this isn't my problem. I just tried to reproduce their problem and I found this.

          I want to know why there is an inconsistency for this. It looks like a bug and it looks like the owner of this discussion was not answered correctly.

          You're correct. I probably wouldn't want jndi on localhost and to run jmx remotely, but this has caused some unnecessary confusion amongst users. Anyway, someone might think of a reason to want this.

            • Actions
          • 17. Re: Version 2.1.1 and Remote JMX
            mrbeagle
            mrbeagle Sep 23, 2010 4:47 PM (in response to peterox)

            that worked for me as well, commenting out the jndi section of the beans file

              • Actions
            1 2 Previous Next