I am using JBoss 2.2.2 and Tomcat 3.2.2. We have an application that sends a message to a queue that is handled by a stateless session bean (a separate piece of code monitors the queue and routes the message to the appropriate bean). The code is able to send a message to the queue, the bean picks it up and send a response to the response queue. What I have noticed is that the JMS code is not actually removing anything from the queue. It is reading the first message placed in the queue over and over. What am I doing wrong? We are following a standard process of getting context, establishing a session, creating a receiver, starting the connection and then doing a receive with a timeout limitation? What could be causing this behavior?
Joe Noonan
NeuVis
