Akka 2.2.1 Released
Dear hAkkers,
We—the Akka committers—are pleased to be able to announce the availability of Akka 2.2.1. This is the first maintenance release of the 2.2 branch, containing documentation improvements and fixing several issues including:
- Convenience method for looking up ActorRef via ActorSelection
- Configurable dispatcher for internal remoting actors
- Java support of ask pattern using ActorSelection as target
- Less noisy and more configurable logging of remoting events
… and several smaller fixes.
Akka 2.2.0 Released
Dear hAkkers,
we—the Akka committers—proudly announce the FINAL RELEASE of Akka 2.2.0 “Coltrane”. Half a year has passed since the release of Akka 2.1.0 “Mingus” and much has happened in our code base. User-visible API changes have been kept to a minimum, though, as most work happened under the hood; more on that later. First let us take a look at what Coltrane brings you:
- Cluster support (with a big thank-you for the feedback throughout the development cycle); we have continued to improve on the preview offered with Mingus, e.g. adding node roles or distributed pub-sub or the cluster client.
- Fully actor-based remoting implementation with support for multiple transports and high-level failure detection.
- An extremely scalable actor-based network IO layer with SSL support and a protocol pipeline infrastructure.
- Reliable supervision and deathwatch for remote actors.
- An experimental preview of Typed Channels.
This is just a very high-level overview of the biggest pieces, there have also been improvements in other areas like test coverage of our OSGi bundles, or how actor failures are logged, or in the semantics of ActorContext.unwatch(), or a more performant rewrite of Agents, or how dispatchers and mailboxes can be configured outside of your code.
Akka 2.2-M3 Released
Dear hAkkers,
we—the Akka committers—are pleased to announce the THIRD PRE-RELEASE MILESTONE of Akka 2.2 “Coltrane”. As discussed earlier this is to be the final and feature-complete milestone, so please take a good look and give feedback. We will gladly fix all rough edges you report while we will thoroughly test and benchmark and if necessary improve the current state of the toolkit. We do this so that we can then confidently proclaim the first release candidate in a few weeks.
Akka 2.1.2 Released
Dear hAkkers,
We—the Akka committers—are pleased to be able to announce the availability of Akka 2.1.2. This is the second maintenance release of the 2.1 branch, where the main changes are that it was built and tested against Scala 2.10.1 and that it comes with true Javadoc generated by the GenJavaDoc plugin.
This release is backwards binary compatible with version 2.1.0, and 2.1.1, which means that the new JARs are a drop-in replacement for the old ones (but not the other way around). Always make sure to use at least the latest version required by any of your project’s dependencies.
Known Issues
Due to the restriction imposed by binary compatibility—which is kept for the patch releases within a minor release such as 2.1.x—not all known issues can be fixed. The currently known issues in the 2.1.x series are:
- ActorSystem.shutdown() does not terminate all threads if akka.remote.netty.use-dispatcher-for-io is set to true
Migrating from Older Releases
When migrating an existing project from Akka 2.0.x please have a look at our migration guide
When migrating from the Akka 1.3.x series please follow first the migration guide towards version 2.0.5
About the Cluster Support
The “akka-cluster” module is published under the name “akka-cluster-experimental” to emphasize that its status is not yet final. This denomination is not due to sub-par standard of the module; the cluster support has been tested thoroughly and it works as documented. The reason for the “experimental” tag is that this rather important module is now presented to the general public for the first time, and although we have received valuable feedback from early adopters we anticipate possible API changes in order to meet all of your requirements. Work is continuing on Akka’s cluster support, and we will formally declare it officially supported and stable with the next major release—Akka 2.2 ‘Coltrane’. Please help us make it the best possible solution by continuing to give feedback on the mailing list and telling us what can be improved.
IMPORTANT NOTICE
The artifacts comprising this release candidate have been published to https://oss.sonatype.org/content/repositories/releases/ and also to Maven Central. In addition, we adopted the SBT standard of encoding the Scala binary version in the artifact name, i.e. the core actor package’s artifactId is “akka-actor_2.10”.
2.1.2 compared to 2.1.1:
* 5 tickets closed
* 49 files changed, 361 insertions(+), 287 deletions(-)
* … and a total of 3 committers!
Fixed Tickets: see the assembla milestone
Happy hAkking!
Akka 2.1.1 Released!
Dear hAkkers,
We—the Akka committers—are pleased to be able to announce the availability of Akka 2.1.1. This is the first maintenance release of the 2.1 branch, which besides documentation updates and the fixes mentioned below also contains a back-port of most of the cluster-related changes in the recently released 2.2-M1.
The issues fixed are:
- release thread pool used by Netty’s ExecutionHandler more timely
- passive remote connections now work when using secure cookies
- do not silently swallow exceptions in ForkJoinPool executor anymore
- fix a bug in HashedWheelTimer which would schedule events incorrectly if delay is multiple of one wheel rotation (thanks Matthew Neeley)
- fix reporting of error condition when IOManager binds to a port
- make sure to set Thread.interrupt() flag when catching InterruptedException during tell()
- Netty does not close the connection anymore upon encountering a non-serializable or too large message
- PinnedDispatcher does not allow its thread to time out anymore, keeping the actor on the same thread (as opposed to only on its own thread)
- actually disallow sending `null` messages (was always forbidden by documentation and only worked on some special ActorRefs)
- StdoutLogger restores stdout-loglevel during system shutdown
- do not leak the default dispatcher anymore
- do not set SO_REUSEADDR for remoting on Windows (which implements this in a buggy way)
- properly log exceptions without a message in JulEventLogger (thanks Sam Halliday)
The changes in the cluster module are:
- cluster metric-aware adaptive load balancing routers
- automatically load cluster extension when used, no need to declare in `akka.extensions` anymore
- fire DeathWatch only upon member DOWN, not already at UNREACHABLE
- allow configuration of minimum number of members before starting the cluster
- cluster singleton pattern
- detect failure even when no heartbeat was ever sent
In addition there have been a great number of documentation updates including a whole new section on terminology.
This release is backwards binary compatible with version 2.1.0, which means that the new JARs are a drop-in replacement for the old ones (but not the other way around). Always make sure to use at least the latest version required by any of your project’s dependencies.
Known Issues
Due to the restriction imposed by binary compatibility—which is kept for the patch releases within a minor release such as 2.1.x—not all known issues can be fixed. The currently known issues in the 2.1.x series are:
- ActorSystem.shutdown() does not terminate all threads if akka.remote.netty.use-dispatcher-for-io is set to true
Migrating from Older Releases
When migrating an existing project from Akka 2.0.x please have a look at our migration guide.
When migrating from the Akka 1.3.x series please follow first the migration guide towards version 2.0.5.
About the Cluster Support
The “akka-cluster” module is published under the name “akka-cluster-experimental” to emphasize that its status is not yet final. This denomination is not due to sub-par standard of the module; the cluster support has been tested thoroughly and it works as documented. The reason for the “experimental” tag is that this rather important module is now presented to the general public for the first time, and although we have received valuable feedback from early adopters we anticipate possible API changes in order to meet all of your requirements. Work is continuing on Akka’s cluster support, and we will formally declare it officially supported and stable with the next major release—Akka 2.2 ‘Coltrane’. Please help us make it the best possible solution by continuing to give feedback on the mailing list and telling us what can be improved.
IMPORTANT NOTICE
The artifacts comprising this release candidate have been published to https://oss.sonatype.org/content/repositories/releases/ and also to Maven Central. In addition, we adopted the SBT standard of encoding the Scala binary version in the artifact name, i.e. the core actor package’s artifactId is “akka-actor_2.10”.
2.1.1compared to 2.1.0:
- 55 tickets closed
- 604 files changed, 8100 insertions(+), 2626 deletions(–)
- … and a total of 8 committers!
Fixed Tickets: see the assembla milestone
Happy hAkking!
Akka 2.2-M1 Released
- Metrics-based adaptive cluster-aware routers
- DeathWatch fires upon node DOWN (previously on UNREACHABLE)
- Configurable minimum number of nodes before cluster starts
- ClusterSingleton actor pattern
- Hardening of the code by adding stress tests
- various fixes, optimizations
- Smaller SPI for implementing other transport drivers
- Support for multiple transports within one ActorSystem
- No more blocking message sends due to broken connections or during connection establishment
- Currently still using Netty, but will switch to Akka IO soon
- Completely new IO layer written in collaboration with the spray.io team
- Actors all the way down—until you hit NIO
- No external dependencies
- Extreme scalability
- No compromises on the API (i.e. fully exposing the different capabilities of e.g. TCP and UDP)
- Type-safety for message sends which is on par with type checking of method invocations
- Based on Scala 2.10 macros; unfortunately not possible to do in Java
- Very early preview, expect API changes within the next weeks
commits added removed
62 6476 3442 Roland
58 8925 4476 Patrik Nordwall
57 10824 6041 Endre Sándor Varga
43 3040 4311 Viktor Klang
17 819 440 Björn Antonsson
11 1324 322 Johannes Rudolph
10 1109 527 Mathias
6 1108 289 Rich Dougherty
5 311 139 RickLatrine
2 83 20 Kaspar Fischer (hbf)
2 127 66 Christophe Pache
2 163 66 Raymond Roestenburg
1 10 3 Michael Pilquist
1 127 127 drewhk
1 548 77 Helena Edelson
1 38 24 Matthew Neeley
1 8 10 Peter Vlugter
1 3 3 Thomas Lockney
1 36 35 Derek Mahar
Happy hAkking!
Akka 2.1.0 Released
Dear hAkkers,
We—the Akka committers—are pleased to be able to announce the availability of Akka 2.1.0 ‘Mingus’. We are proud to include the work of 17 external committers, plus the work done by our great community in reporting and helping to diagnose bugs along the way.
This release refines and builds upon version 2.0, which was published a bit over nine months ago. The most prominent new features are
- cluster support (experimental, including cluster membership logic & death watch and cluster-aware routers, see more below)
- integration with Scala standard library (SIP-14 Futures, dataflow as add-on module, akka-actor.jar will be part of the Scala distribution)
- Akka Camel support (Raymond Roestenburg & Piotr Gabryanczyk)
- Encrypted Akka Remoting using SSL/TLS (Peter Badenhorst)
- OSGi meta-information for most bundles (excluding samples and tests, Gert Vanthienen)
- an ActorDSL for more concise actor declarations, e.g. in the REPL
- a module for multi-node testing (to support you in developing clustered applications, experimental in the same sense as cluster support)
- a Java API for the TestKit
In addition there have been a great number of small fixes and improvements, documentation updates (including a whole new section on message delivery guarantees), an area for contributions—akka-contrib—where community developments can mature and prove themselves and many more. A series of blog posts high-lighting the new features has been published over the past weeks on this blog, see this tag.
When migrating an existing project from Akka 2.0.x please have a look at our migration guide: migration-guide-2.0.x-2.1.x
When migrating from the Akka 1.3.x series please follow first the migration guide towards version 2.0.4: migration-guide-1.3.x-2.0.x