[
https://issues.apache.org/jira/browse/CAMEL-7321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944611#comment-13944611
]
ASF GitHub Bot commented on CAMEL-7321:
---------------------------------------
GitHub user gzurowski opened a pull request:
https://github.com/apache/camel/pull/116
CAMEL-7321: Fix inconsistent synchronization to prevent freezing of
JcrConsumer
Signed-off-by: Gregor Zurowski <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gzurowski/camel CAMEL-7321
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/116.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #116
----
commit adf86876f3f4fdc895a66d50361102093ee4f98a
Author: Gregor Zurowski <[email protected]>
Date: 2014-03-23T22:17:14Z
CAMEL-7321: Fix inconsistent synchronization to prevent freezing of
JcrConsumer
Signed-off-by: Gregor Zurowski <[email protected]>
----
> JcrConsumer freezes in some environments
> ----------------------------------------
>
> Key: CAMEL-7321
> URL: https://issues.apache.org/jira/browse/CAMEL-7321
> Project: Camel
> Issue Type: Bug
> Components: camel-jcr
> Affects Versions: 2.13.0
> Reporter: Gregor Zurowski
> Assignee: Gregor Zurowski
>
> In January [~njiang] reported that the JUnit test JcrConsumerTest fails in
> his environment. This could not be reproduced in other environments at that
> time. [~njiang] applied the following fix to the pom.xml in order make the
> test pass:
> {code:title=camel-jcr/pom.xml}
> [...]
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <forkMode>pertest</forkMode>
> </configuration>
> </plugin>
> </plugins>
> </build>
> [...]
> {code}
> This made all tests run in separate processes, but was also an indicator for
> potential multi-threading issues in JcrConsumer. I was recently able to
> reproduce the problem by running Maven within Eclipse. The problem is indeed
> a synchronization issue and should be addressed with this ticket.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
