+ Workaround for injecting ConnectionFactory instances - Inject JmsXA instead of ConnectionFactory @Resource(mappedName="java:/JmsXA", type=javax.jms.ConnectionFactory.class) private ConnectionFactory factory; + Workarounds for injecting Queue/Topic instances: 1.- Not to inject Queue and instead, assuming the queue name is "queue/A" use the following code to initialise it the first time you use the Queue instance variable: String bindAddress = System.getProperty("jboss.bind.address") == null ? "localhost" : System.getProperty("jboss.bind.address"); InitialContext ic = new InitialContext(); Queue queueA = (Queue)ic.lookup("jnp://" + bindAddress + ":1100/queue/A"); 2.- For this second option, let's assume the queue name is "queue/B". In this case, you can add META-INF/jboss.xml to your EJB jar deployment, which looks like this: <?xml version="1.0"?> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"> <jboss> <enterprise-beans> <session> <ejb-name>InhaltPruefungVerwaltungBean</ejb-name> <resource-ref> <res-ref-name>queue/ref/B</res-ref-name> <jndi-name>jnp://${jboss.bind.address:localhost}:1100/queue/B</jndi-name> </resource-ref> </session> </enterprise-beans> </jboss> And inject the Queue in your EJB this way: @Resource(mappedName="java:comp/env/queue/ref/B") private Queue queueB;