"DefaultJMSProvider not bound" warning with deploying an MDB in JBoss EAP

Issue

• When deploying a Message Driven Bean this WARN occurs:

  WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@43784378(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@4fa54fa5 destination=<destinationName> destinationType=null tx=true durable=false reconnect=10 provider=DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=10
     javax.naming.NameNotFoundException: DefaultJMSProvider not bound
          at org.jnp.server.NamingServer.getBinding(NamingServer.java:581)
          at org.jnp.server.NamingServer.getBinding(NamingServer.java:589)
          at org.jnp.server.NamingServer.getObject(NamingServer.java:595)
          at org.jnp.server.NamingServer.lookup(NamingServer.java:342)
          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
          at javax.naming.InitialContext.lookup(InitialContext.java:450)
          at org.jboss.util.naming.Util.lookup(Util.java:215)
          at org.jboss.util.naming.Util.lookup(Util.java:175)
          at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupJMSProviderAdapter(JmsActivation.java:365)
          at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:322)
          at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:671)
          at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)   
          at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
          at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
          at java.lang.Thread.run(Thread.java:735)