#1 Not compliant MBean

v1.0_(example)
closed-fixed
None
5
2003-10-20
2003-09-27
No

While running,
javax.management.NotCompliantMBeanException is thrown.
It says MBean has no public constructor.

The problem is solved if org.mom4j.messaging.Console
class' contructor is made public.

Versions:
--------------
JDK 1.4.1
JMS 1.1
JMX 1.2.1

Discussion

  • Stefan Denninger

    • assigned_to: nobody --> the_real_grace
    • status: open --> open-accepted
     
  • Stefan Denninger

    Logged In: YES
    user_id=809090

    Java" Management Extensions Instrumentation and Agent
    Specification, v1.2 (page 34) :

    "The Java class of an MBean, whether standard or dynamic,
    *can* optionally be of a public class and have one or more
    public constructors. An MBean must be of a public concrete
    class with a public constructor if it is to be instantiated
    by a JMX agent on demand from a management application."

    In a mom4j server process, there is only one instance of
    class Console and this intance plays a very central and
    important role. It doesn't make sense to have more then one
    instances. Thats why it doesn't have a public constructor
    and that's why it is not ment to be instantiated by a JMX
    agent. This is absolutely conform to the spec (see above).
    Mom4j runs properly with JDK 1.4.1, JMS interfaces 1.1 and
    JMX 1.2.1 (reference implementation from SUN Microsystems).

     
  • Stefan Denninger

    • status: open-accepted --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks