Thanks for answering my question.

No, the transaction will not be shared by different threads.  The transaction is committed after I convert the events to some data structure.

I would only have a Timer/Executor thread that fires off at specific intervals to send these converted data structures (from events) to customized storage/consumer for processing.

Do you see an issue with this approach ?


On Aug 24, 2014, at 9:59 PM, Hari Shreedharan <[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