Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 11 Sep 2016 14:22:20 +0000 (UTC)
From: "Fabrizio Spataro (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13004075.1473517287000.541949.1473603740579@Atlassian.JIRA>
In-Reply-To: <JIRA.13004075.1473517287000@Atlassian.JIRA>
References: <JIRA.13004075.1473517287000@Atlassian.JIRA> <JIRA.13004075.1473517287391@arcas>
Subject: [jira] [Commented] (CAMEL-10306) Upgrade from 3.6.5 to 3.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 11 Sep 2016 14:22:22 -0000


    [ https://issues.apache.org/jira/browse/CAMEL-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481828#comment-15481828 ] 

Fabrizio Spataro commented on CAMEL-10306:
------------------------------------------

I am studing failure tests, i supposed that hazelcast change lock and idempotence features! 

*Call reference IDs are included in the Lock operations issued from member to member, to prevent double locking when lock operation is retried. But, Lock at clients does not have these. [8359]* ( from http://docs.hazelcast.org/docs/release-notes/ )

> 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)