EJB3 Core 5.4.16.1
A JMS message-driven bean is associated with a JMS Destination (Queue or Topic) when the bean is
deployed in the container. It is the responsibility of the Deployer to associate the message-driven bean
with a Queue or Topic.

The short answer is implement the interface

javax.jms.MessageListener

@MessageDriven

@MessageDriven(activateConfig = {
 @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
 @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/MyMDBQueue")
})
// NOTE: the EJB3 JSR says this class must not be final
public class MyMDB implements MessageListener {

 private static final Logger l = Logger.getLogger(MyMDB.class);

 // NOTE: the EJB specification says we must have a public constructor with no arguments
 public MyMDB() {
 // to support spec
 }

 // NOTE: the EJB specification says this method must not be final
 public void onMessage(final Message message) {
 l.debug("*********** GOT MESSAGE: " + message);
 }
}

What is the property for setting the maxium MDB pool size?

I have tried both:

@ActivationConfigProperty(propertyName = "maximumSize", propertyValue = "20"),

@ActivationConfigProperty(propertyName = "maxPoolSize", propertyValue = "20"),

In the annotation Oracle wants destinationName and jboss wants destination.

Can I use something which both app server would be happy with.

@MessageDriven(activationConfig={
@ActivationConfigProperty(propertyName="destination", propertyValue="queue/ServiceInvocationQueue"),
@ActivationConfigProperty(propertyName="destinationName", propertyValue="queue/ServiceInvocationQueue"),
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue")
})

Jboss throws error when I have this.