metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cestella <>
Subject [GitHub] incubator-metron issue #149: METRON-217: Found a grabbag of bugs
Date Sat, 11 Jun 2016 00:45:58 GMT
Github user cestella commented on the issue:
    Just for those poor souls who are debugging this on the internet, this is the sister exception
(from the other thread):
    > 2016-06-10 13:34:44.687 b.s.util [ERROR] Async loop died!
    java.lang.RuntimeException: java.util.ConcurrentModificationException
            at backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(
            at backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(
            at backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
            at backtype.storm.daemon.executor$fn__5492$fn__5505$fn__5556.invoke(executor.clj:813)
            at backtype.storm.util$async_loop$fn__644.invoke(util.clj:479) [storm-core-]
            at [clojure-1.6.0.jar:?]
            at [?:1.8.0_51]
    Caused by: java.util.ConcurrentModificationException
            at java.util.HashMap$HashIterator.nextNode( ~[?:1.8.0_51]
            at java.util.HashMap$ ~[?:1.8.0_51]
            at java.util.HashMap$ ~[?:1.8.0_51]
            at java.util.HashMap.putMapEntries( ~[?:1.8.0_51]
            at java.util.HashMap.clone( ~[?:1.8.0_51]
            at org.apache.metron.enrichment.bolt.BulkMessageWriterBolt.execute(
            at backtype.storm.daemon.executor$fn__5492$tuple_action_fn__5494.invoke(executor.clj:684)
            at backtype.storm.daemon.executor$mk_task_receiver$fn__5415.invoke(executor.clj:431)
            at backtype.storm.disruptor$clojure_handler$reify__4991.onEvent(disruptor.clj:58)
            at backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(
            ... 6 more

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message