>I agree - updating a db on processing of each message doesn't sound a very >>scaleable solution. OK, good.
>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? Well, I'm not sure about that. The consumer will be handling messages from various jobs, and messages from different jobs may be posted simultaneously. Are you suggesting that the consumer hold state and keep a map along the lines of ["job id", count] and then when count reaches a certain size, then do a counter update? If so, how would the listener know when all the messages for a particular job were done? ie. the listener (with a threshold of 1000) got to a count of 812 (for example) and then there were no more messages... >Another solution would be to send a special "progress" message to >another >queue when the listener has processed 1000 or 10000 messages >(or whatever). Yes, this would be fine and is similiar to a db update. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938165#3938165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938165 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
