[
https://issues.apache.org/jira/browse/CAMEL-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201872#comment-14201872
]
Babak Vahdat commented on CAMEL-8004:
-------------------------------------
This is the side effect of the fix for CAMEL-7836. If you would remove the
[synchronized
modifier|https://github.com/apache/camel/commit/882857fa9cc058c880db3e55061e2409cf8370b3]
there, then this test would not hang anymore.
IMHO CAMEL-7836 asks for a thread-safty which (as far as I know) has been never
been claimed to be given by different {{org.apache.camel.CamelContext}} Impls,
but maybe I'm wrong. Another option is probably to make use of a thread-safe
{{java.util.Set}} Impl for the {{routes}} field without using the
{{synchronized}} modifier, e.g. {{java.util.concurrent.CopyOnWriteArraySet}}.
> camel-quartz2 - A test may hang
> -------------------------------
>
> Key: CAMEL-8004
> URL: https://issues.apache.org/jira/browse/CAMEL-8004
> Project: Camel
> Issue Type: Test
> Components: tests
> Reporter: Claus Ibsen
> Priority: Minor
> Attachments: Screen Shot 2014-11-07 at 10.31.58.png, Screen Shot
> 2014-11-07 at 10.32.27.png
>
>
> This test seems to hang. I killed the job
> Running org.apache.camel.component.quartz2.QuartzNameCollisionTest
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
