Problem with JMS queues after upgrading to jboss 5.1.0 GA

[daphna deutsch]

Hi,

I upgrade my application from jboss 4.0.5 to 5.1.0, and i'm having problems with the jsm queues.

I’m trying to send a message to queueA from MDB and got the exception javax.naming.NameNotFoundException.

The same queue is working correctly when using from stateless bean.

I have another queue, queueB, that does work from the same MDB.

These are the configuration that I’m using:
In ejb-jar.xml:

   
<message-driven>
	<description>Message Driven Bean</description>
	<display-name>MDB_A</display-name>
	<ejb-name>MDB_A</ejb-name>
	<ejb-class>path...</ejb-class>
	<transaction-type>Container</transaction-type>
	<message-destination-type>javax.jms.Queue</message-destination-type>

	<activation-config>
		<activation-config-property>
			<activation-config-property-name>DestinationType</activation-config-property-name>
			<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
		</activation-config-property>
		<activation-config-property>
			<activation-config-property-name>acknowledgeMode</activation-config-property-name>
			<activation-config-property-value>Auto-acknowledge</activation-config-property-value>
		</activation-config-property>
	</activation-config>

	<resource-ref>
		<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
		<res-type>javax.jms.ConnectionFactory</res-type>
	<res-auth>Container</res-auth>
	</resource-ref>
	<resource-ref>
		<res-ref-name>jms/queue_A</res-ref-name>    
		<res-type>javax.jms.Queue</res-type>
		<res-auth>Container</res-auth>
	</resource-ref>
	<resource-ref>
		<res-ref-name>jms/queue_B</res-ref-name>    
		<res-type>javax.jms.Queue</res-type>
		<res-auth>Container</res-auth>
	</resource-ref>
	

</message-driven>
 

And in jboss.xml:

    
<message-driven>
		<ejb-name>MDB_A</ejb-name>
		<destination-jndi-name>queue/queue_B</destination-jndi-name>
	<resource-ref>
		<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
		<resource-name>jmsConnectionFactory</resource-name>
	</resource-ref>
	<resource-ref>
		<res-ref-name>jms/queue_A</res-ref-name>
		<resource-name>queue_A</resource-name>
	</resource-ref>     
	<resource-ref>
		<res-ref-name>jms/queue_B</res-ref-name>
		<resource-name>queue_B</resource-name>
	</resource-ref>

</message-driven>


<message-driven>
	<ejb-name>queue_A</ejb-name>
	<destination-jndi-name>queue/queue_A</destination-jndi-name>
	<resource-ref>
		<res-ref-name>jms/jmsConnectionFactory</res-ref-name>
		<resource-name>jmsConnectionFactory</resource-name>
	</resource-ref>
</message-driven>

queue_B is the one that is working, and queue_A is failed.
There was no change in these configuration from jboss 4.0.5.


thanks for the help