When the super class of an EJB3 MDB implements the same business interface a second time an "unable to determine messagingType interface for MDB" exception is thrown --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1185 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1185 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Roland Räz The class org.jboss.ejb3.mdb.MDB.getMessagingType() throws a RuntimeException("unable to determine messagingType interface for MDB") when a s super class of an MDB implements the business interface. To fix this bug the org.jboss.ejb3.ProxyFactoryHelper.getBusinessInterfaces(clazz) method could use internally a Set instead of a list, this would be preferred and least surprising semantic in my opinion. Caused by: java.lang.RuntimeException: unable to determine messagingType interface for MDB at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:88) at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.getBusinessInterfaces(EJB3InterceptorsFactory.java:167) at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.isBusinessMethod(EJB3InterceptorsFactory.java:122) at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:98) ... 154 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira