Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12514

ConcurrentModificationException during deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • 7.1.0.ER3
    • CDI / Weld

      During our automated testing, this issue occured:

      20:29:41,817 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./contextRoot.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./contextRoot.UndertowDeploymentInfoService: Failed to start service
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
      	at java.lang.Thread.run(Thread.java:785)
      Caused by: java.util.ConcurrentModificationException
      	at java.util.HashMap$HashIterator.nextNode(HashMap.java:1448)
      	at java.util.HashMap$KeyIterator.next(HashMap.java:1472)
      	at org.jboss.weld.util.collections.Iterators$TransformingIterator.next(Iterators.java:142)
      	at org.jboss.weld.util.collections.Iterators$TransformingIterator.next(Iterators.java:142)
      	at org.jboss.weld.util.collections.Iterators$CombinedIterator.hasNext(Iterators.java:95)
      	at org.jboss.weld.util.collections.Iterators$CombinedIterator.hasNext(Iterators.java:94)
      	at org.jboss.weld.resolution.AbstractTypeSafeBeanResolver$1.computeValue(AbstractTypeSafeBeanResolver.java:151)
      	at org.jboss.weld.resolution.AbstractTypeSafeBeanResolver$1.computeValue(AbstractTypeSafeBeanResolver.java:146)
      	at org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:49)
      	at org.jboss.weld.resolution.AbstractTypeSafeBeanResolver.getBeans(AbstractTypeSafeBeanResolver.java:238)
      	at org.jboss.weld.resolution.AbstractTypeSafeBeanResolver.getAllBeans(AbstractTypeSafeBeanResolver.java:217)
      	at org.jboss.weld.resolution.TypeSafeResolver.findMatching(TypeSafeResolver.java:102)
      	at org.jboss.weld.resolution.TypeSafeResolver.access$000(TypeSafeResolver.java:41)
      	at org.jboss.weld.resolution.TypeSafeResolver$ResolvableToBeanCollection.apply(TypeSafeResolver.java:52)
      	at org.jboss.weld.resolution.TypeSafeResolver$ResolvableToBeanCollection.apply(TypeSafeResolver.java:43)
      	at org.jboss.weld.util.cache.ReentrantMapBackedComputingCache$1.apply(ReentrantMapBackedComputingCache.java:55)
      	at org.jboss.weld.util.cache.ReentrantMapBackedComputingCache$1.apply(ReentrantMapBackedComputingCache.java:51)
      	at org.jboss.weld.util.cache.ReentrantMapBackedComputingCache.getValue(ReentrantMapBackedComputingCache.java:64)
      	at org.jboss.weld.resolution.TypeSafeResolver.resolve(TypeSafeResolver.java:88)
      	at org.jboss.weld.manager.BeanManagerImpl.getBeans(BeanManagerImpl.java:557)
      	at org.jboss.as.weld.deployment.WeldClassIntrospector.getInjectionTarget(WeldClassIntrospector.java:77)
      	at org.jboss.as.weld.deployment.WeldClassIntrospector.createFactory(WeldClassIntrospector.java:57)
      	at org.jboss.as.ee.component.ComponentRegistry.createInstanceFactory(ComponentRegistry.java:76)
      	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:726)
      	at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:273)
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
      	... 3 more
      

      I wasn't able to reproduce it again yet. The issue occured only once on RHEL6 x86_64 with IBM JDK 8 SR4 FP6.

      The scenario was to deploy EJB jar via Arquillian and do some testing. But deployment failed with above exception. Check full log and deployment jar in attachment.

            rhn-cservice-bbaranow Bartosz Baranowski
            jbliznak@redhat.com Jan Blizňák
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: