I have the following scenario on Websphere 5:
a) Stateless session bean sending a JMS message to a queue
b) Message-driven bean consuming this message on the same server
Everything seem to be ok, but the message is not consumed at all. Has anybody some experience with such issue?
Are you using WebSphere's Embedded JMS implementation, or are you using WebSphere MQ? Typically you see behavior like this when using WebSphere MQ and you haven't set up a server connection channel appropriately to recieve client requests (this is of course assuming you are using the CLIENT method of transport versus BINDING). Also, I am assuming that you verified in your logs (either WAS's system out or your own logs) that the MDB is actually started. Also, did you set up a Listener Port for the Connection Factory and the Queue?