In our application we send the messages from session bean (in the transaction context, we are using BMT) to the Queue, using java:/JmsXA ConnectionFactory.
In the JBoss 2.4.4 the same application works fine, the messages successfully sent and received by listener (we are using MessageDrivenBean). As Persistence Manager we are using file - based manager, so we can see, that the message successfully delivered and removed from the storage. Bu under JBoss 3.0.0 there are problems.
The messages successfully sent, but after the transaction had been committed, we saw the record in the log about problem with connection to consumer. After investigation, we found, that the SpyMessage, that has been sent to Consumer was wrong - it looks like the default instance. But in the file I can see that the message is correct... Moreover, after inserting some additional debug messages I found that the org.jboss.mq.server.BasicQueue.queueMessageForSending receive correct MessageReference message. The problem occurred later, probably because some WeakReference semantics of this MessageReference.
Is it a bug? And is there a fix?