I am looking for a way to keep running counts of all of the processed messages. The last part of the camel application is a route that posts the message to a web service, we need to keep counts of the various responses so that when the entire process is complete and the application is exiting it will log the number of successful submissions and the numbers of unsuccessful submissions by the error type. So for example we have something like this:
Success: 12345678 Error A: 2345 Error B: 3456 ... One idea was to send an empty message to a counter topic based on the respose. e.g. COUNTER.SUCCESS, COUNTER.ERRA, COUNTER.ERRB, etc. Then on exit I can use the enqueue count as the counter. I don't know if that's the best idea but it worked with one problem. The problem is that if the application is killed or has some sort of serious problems such as a full disk or we run out of memory, all of which have happened while testing, the counts are completely lost. I could do the same thing with queues instead of topics and use the queue size for the count but I would have to persist the messages. It would work but with additional overhead and I/O for persisting essentially nothing. I could just log the response results and count later but that does not seem much better than using persistent queues. Is there some way that people are using to keep a running count of various message processing results that can reliably survive an application restart?
