When the consumption stops in GroupA, were there any error/exception in the
consumer logic?

One common cause for a consumer to stop is that the application code hits
an exception while consuming an event. In particular, if you are using java
thread pool and haven't attached an exception handler, those exceptions
will be eaten and you won't see them in the application log. The solution
is to add a try/catch clause in the application code to log all Throwables.


On Sun, Jan 20, 2013 at 6:22 PM, Bo Sun <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB