Suppose I have the following interfaces:

public interface Parent1 {
    public int foo();
}
public interface Parent2 {
    public int foo();
}
public interface ChildMBean extends Parent1, Parent2 {
}
public class Child implements ChildMBean {
    public int foo() {return 0;}
}

If I register this MBean, its MBeanInfo will contain two MBeanOperationInfo defining two operations both called "foo".

The behaviour is the same if I define an MXBean instead of a Standard MBean.

This bug was already present in Tiger and is present in Mustang b77.