I agree - updating a db on processing of each message doesn't sound a very scaleable solution.
Having a consumer update the db after having processed 1000 messages/sec seems somewhat better but I still don't understand why you'd need a special "counter message" to do this - can the consumer not keep count itself? Another solution would be to send a special "progress" message to another queue when the listener has processed 1000 or 10000 messages (or whatever). You're application could then inspect the "progress" queue to see the current progress. The progress messages could perhaps be non-persistent (depending on your application requirements) so not requiring any db hits (unless you have a lot of them) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938160#3938160 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938160 ------------------------------------------------------- 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
