I deployed a stateless session bean and an MDB in a configuration similar to yours.
I used the stateless session bean to send a message to requestQueue. The message has been immediately processed by the MDB and the response has been placed in responseQueue (no expiration for message). I then used the session bean to read from the responseQueue after more than 15 minutes, and everything worked fine. If something is wrong with the server, it's probably due to a race condition caused by the message expiration. Could you replicate the error consistently? Could you describe the sequence of steps so I can replicate it as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953149#3953149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953149 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
