Vert.x 2.1.6 has been released

[Tim Fox]

I'm pleased to announce the release of Vert.x 2.1.6.

This is a maintenance release on the 2.x branch that fixes a few bugs and is designed for our current Vert.x 2 production users who cannot upgrade to 3.0 immediately.

For the latest production version for new projects please see Vert.x 3.0.

Fixes in this release include:

* runZip - fix bugs in unpacking zips

* HttpClient - make sure writeHead is set to true before connect

* Upgrade to Hazelcast 3.5 to fix bug in Multimap state.

* Workaround for Hazelcast bug which could result in inconsistent cluster state if multiple nodes shutdown concurrently

* Clustering fixes related to clearing up state in case of event bus connections closing and on close of event bus.

* Fix message replies to nodes other than the node the SockJS bridge is deployed on

The artifacts are in Maven, and you can get the distribution on Bintray: https://bintray.com/vertx/downloads/distribution/2.1.6/view

Thanks

[Morten Jensen]

Yay, great news! Thanks Tim! I'll get it into test and production in short order given the issues we've previously faced with the cluster state problem.

Again, thanks.
Morten

[Jon Arne Hegge]

Hi!

Thanks! Highly appreciated this one. 

Been struggling with the Hazelcast bugs and corrupted clusters for awhile now.

regards,

Jon Arne  

[Morten Jensen]

Anyone using AWS for vert.x deployments may wish to hold off deploying vert.x 2.1.6 for now due to: https://github.com/hazelcast/hazelcast/issues/5653 (com.hazelcast.cluster.impl.TcpIpJoinerOverAWS Server returned HTTP response code: 401 for URL: https://ec2.amazonaws.com/?Action=DescribeInstances)

Tim, separately I notice in 2.1.6 that default conf/cluster.xml has the following defined schema location:
<hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.2.xsd">

I don't think there's a problem with this but Hazelcast does appear to flag it as a warning in the logs:

2015-07-03 09:44:16.132000 WARNING com.hazelcast.config.AbstractXmlConfigHelper Name of the hazelcast schema location incorrect using default


Thanks.

Morten


On Tuesday, 30 June 2015 09:30:49 UTC+1, Tim Fox wrote:

[Morten Jensen]

Hi Tim,

It looks like the Hazelcast AWS issue (https://github.com/hazelcast/hazelcast/issues/5653) is being back ported to 3.5.2: https://github.com/hazelcast/hazelcast/issues?q=is%3Aopen+milestone%3A3.5.2+is%3Aissue with PR https://github.com/hazelcast/hazelcast/pull/5778. I've been away on holidays in the last 2 1/2 weeks so only just followed up on this today.

When this is released would it be possible to get a new vert.x 2.1.x build with this version please?

Thanks.
Morten