I found the problem... After pouring through the logs and JBoss AS source code I found a place where you can select the jms provider JNDI.

Changing the annotations to:


| @MessageDriven(
|      activationConfig = {
|      @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "java:/TibJMSProvider"),
|      @ActivationConfigProperty(propertyName = "destination",
|           propertyValue = "ems/queue.sample"),
|      @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")}
| ))
|

Fixes the problem.
Here are the following valid AcitvationConfigProperties that JBoss understands:

destination
| destinationType
| providerAdapterJNDI
| maxSession

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054483#4054483

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054483
_______________________________________________
jboss-user mailing list
jboss-user@(protected)
https://lists.jboss.org/mailman/listinfo/jboss-user