[
https://issues.apache.org/jira/browse/CAMEL-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481862#comment-15481862
]
Fabrizio Spataro commented on CAMEL-10306:
------------------------------------------
Hello everybody, now all tests are ok
It isn't a wrong lock features but only newHazelcastInstance() that with new
version gone wrong.
I had change this code with newHazelcastInstance(new Config("A NAME")) and all
tests are ok!
Can you merge my PR? (https://github.com/apache/camel/pull/1166)
king regards
FabryProg
LOG OUTPUT
Results :
Flaked tests:
org.apache.camel.processor.aggregate.hazelcast.HazelcastAggregationRepositoryOperationsTest.checkOptimisticPersistentRemove(org.apache.camel.processor.aggregate.hazelcast.HazelcastAggregationRepositoryOperationsTest)
Run 1:
HazelcastAggregationRepositoryOperationsTest.checkOptimisticPersistentRemove:149
▒ OptimisticLocking
Run 2: PASS
Tests run: 186, Failures: 0, Errors: 0, Skipped: 0, Flakes: 1
[
> Upgrade from 3.6.5 to 3.7.1
> ---------------------------
>
> Key: CAMEL-10306
> URL: https://issues.apache.org/jira/browse/CAMEL-10306
> Project: Camel
> Issue Type: Task
> Components: camel-hazelcast
> Reporter: Fabrizio Spataro
> Priority: Minor
>
> Upgrade hazelcast version.
> The 3.7.x version is Cloud-Enabled and 30% Faster and Fully Modularized
> In-Memory Data Grid
> (http://insidebigdata.com/2016/09/02/hazelcast-releases-3-7-cloud-enabled-30-faster-and-the-first-fully-modularized-in-memory-data-grid)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
