java.util.HashMap$Ha: censored:erator.nextEntry(

Mirth Project | Mike Nowlin | 1 decade ago
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Exception occurred while processing several messages at the same time - only happened once out of 50+K messages over the last week or so. Error writing to the database java.util.ConcurrentModificationException at java.util.HashMap$Ha:censored:erator.nextEntry( at java.util.HashMap$ at java.util.HashMap$ at org.mule.providers.TemplateValueReplacer.loadContext( at org.mule.providers.TemplateValueReplacer.replaceValues( at org.mule.providers.jdbc.JdbcUtils.getParams( at org.mule.providers.jdbc.JdbcMessageDispatcher.doDispatch( at org.mule.providers.AbstractMessageDispatcher$ at at$Worker.runTask( at$ at Quote from Chris: Ah very appears that values are being modified in a hash-map while Mirth is trying to iterate through it. This points to an area where we need to synchronize the threads. Can you add this to the JIRA? I'll try to get a fix for this in 1.3.2 (coming withing a week). Additional info available if needed - I haven't deleted anything from the PGSQL DB. thanks - mike

    Mirth Project | 1 decade ago | Mike Nowlin
    java.util.HashMap$Ha: censored:erator.nextEntry(

    Root Cause Analysis

    1. java.util.HashMap$Ha


      at java.util.HashMap$
    2. Java RT
      1. java.util.HashMap$
      2. java.util.HashMap$
      2 frames
    3. org.mule.providers
      1. org.mule.providers.TemplateValueReplacer.loadContext(
      2. org.mule.providers.TemplateValueReplacer.replaceValues(
      3. org.mule.providers.jdbc.JdbcUtils.getParams(
      4. org.mule.providers.jdbc.JdbcMessageDispatcher.doDispatch(
      5. org.mule.providers.AbstractMessageDispatcher$
      5 frames
    4. org.mule.impl
      1 frame
    5. Backport of JSR 166
      2 frames
    6. Java RT
      1 frame