Raymond Augé created ARIES-1963:
-----------------------------------
Summary: ConcurrentModificationException when calling
JaxrsServiceRuntime.getRuntimeDTO repeatedly
Key: ARIES-1963
URL: https://issues.apache.org/jira/browse/ARIES-1963
Project: Aries
Issue Type: Bug
Components: jax-rs-whiteboard
Reporter: Raymond Augé
Fix For: jax-rs-whiteboard-1.1.0
In a test case I'm quickly checking for DTO state of some application
resources. And often I get this concurrent modification exception.
{code}
java.util.ConcurrentModificationException
at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1561)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:546)
at
java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:260)
at
java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:505)
at
org.apache.aries.jax.rs.whiteboard.internal.AriesJaxrsServiceRuntime.buildApplicationDTO(AriesJaxrsServiceRuntime.java:969)
at
org.apache.aries.jax.rs.whiteboard.internal.AriesJaxrsServiceRuntime.getRuntimeDTO(AriesJaxrsServiceRuntime.java:367)
at
org.apache.aries.cdi.test.cases.mpjwt.MpJwtAuthTests.setUp(MpJwtAuthTests.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.osgi.test.junit4.service.ServiceUseRule$1.evaluate(ServiceUseRule.java:158)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:38)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at aQute.junit.Activator.test(Activator.java:356)
at aQute.junit.Activator.automatic(Activator.java:266)
at aQute.junit.Activator.run(Activator.java:187)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at aQute.launcher.Launcher.launch(Launcher.java:412)
at aQute.launcher.Launcher.run(Launcher.java:170)
at aQute.launcher.Launcher.main(Launcher.java:148)
at
aQute.launcher.pre.EmbeddedLauncher.executeWithRunPath(EmbeddedLauncher.java:154)
at
aQute.launcher.pre.EmbeddedLauncher.findAndExecute(EmbeddedLauncher.java:119)
at aQute.launcher.pre.EmbeddedLauncher.main(EmbeddedLauncher.java:48)
{code}
There should be some kind of protection around this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
