[ 
https://issues.apache.org/jira/browse/IVY-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Monroe Walker reopened IVY-1628:
--------------------------------

[~jaikiran] Thanks for such a quick response on this! Unfortunately I don't 
think the changes in that commit will prevent the problem. I expect the copy 
constructor still needs to iterate over the list so there's still the potential 
for modification by another thread while that's happening. I think the ideal 
here would be to put those lists into a threadlocal variable since that seems 
to better match the intent anyway. Otherwise, even if there isn't a concurrency 
exception, two threads may both print the same list of warning/error messages

> ConcurrentModificationException in MessageLoggerHelper.sumupProblems
> --------------------------------------------------------------------
>
>                 Key: IVY-1628
>                 URL: https://issues.apache.org/jira/browse/IVY-1628
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>         Environment: Groovy 2.4.12
>            Reporter: Monroe Walker
>            Assignee: Jaikiran Pai
>            Priority: Major
>             Fix For: master
>
>
> Our Jenkins build job occasionally fails with 
> {code:java}
> java.util.ConcurrentModificationExceptionjava.util.ConcurrentModificationException
>  at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:911) at 
> java.util.ArrayList$Itr.next(ArrayList.java:861) at 
> org.apache.ivy.util.MessageLoggerHelper.sumupProblems(MessageLoggerHelper.java:45)
>  at 
> org.apache.ivy.util.MessageLoggerEngine.sumupProblems(MessageLoggerEngine.java:136)
>  at org.apache.ivy.util.Message.sumupProblems(Message.java:143) at 
> org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:347) at 
> org.apache.ivy.Ivy.resolve(Ivy.java:523)
> {code}
> It seems this must be due to a warning / error being logged while 
> `sumupProblems` is printing the captured warning/errors.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to