I deploy a simple MDB. The destination that specified by the annotation does not exist:

@ActivationConfigProperty(propertyName="destination", propertyValue="queue/suchQueueWasNeverCreatedAndItWill NeverBe")

I overrride the destination name in the jboss-specific deployment descriptor. This destination exists.

<jboss>
<enterprise-beans>
<message-driven>
<ejb-name>MDB</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
</enterprise-beans>
</jboss>

At deployment, the EJB3 deployer tries to (wrongly) create "queue/MDB" instead of realizing that queue/testQueue exists.

10:23:35,988 WARN [MDB] destination not found: queue/MDB reason: javax.naming.NameNotFoundException: MDB not bound
10:23:35,988 WARN [MDB] creating a new temporary destination: queue/MDB