[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-java-list
Subject:    [fedora-java] javax.management woes, again
From:       Andrew Haley <aph () redhat ! com>
Date:       2007-05-02 16:11:07
Message-ID: 200705021611.l42GB7c8013420 () littlepinkcloud ! COM
[Download RAW message or body]

To cut to the chase: I've been debugging 236541 for a week now, and
I've finally found the cause:
gnu.javax.management.Server.registerMBean() is broken in Classpath.

The problem is that it should send MBeanServerNotifications to its
delegate whenever called, but it doesn't.  The result of this is that
the Tomcat embedded web server is broken, because its server contexts
never get registered.

As far as I am aware, every application that uses an embedded Tomcat
is likely to be affected in the same way, and possibly standalone
Tomcat as well.

For the sake of comparison, MX4JMBeanServer.register() does this:

  delegate.sendNotification(new MBeanServerNotification
			    (MBeanServerNotification.REGISTRATION_NOTIFICATION, 
			     delegateName, sequenceNumber, objectName));

So, what to do for Fedora 7?  I'm sure there's no time to fix
gnu.javax.management.

So, I'm proposing this

    ln -sf /usr/share/java/mx4j/mx4j.jar  /usr/share/java/gcj-endorsed

There is one problem that I can see: mx4j is rather old, or at least
the version in Fedora 7 is.  Maybe some of the interfaces in Classpath
are more recent, so perhaps we shouldn't do this globally for all uses
of gcj.  I'd appreciate comments.

Andrew.


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236541

--
fedora-devel-java-list mailing list
fedora-devel-java-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-java-list
[prev in list] [next in list] [prev in thread] [next in thread]