* In EC2 connection time out is around 1 minute. A few messages
were sent after quarantining and these caused endless restarts,
and connect attempts with 1 minute interval.
* This change makes sure that the endpoint is stopped after the first
failed connection attempt.
* Changed default settings for netty connection-timeout, and matching
retry window to allow for 3 restarts
* Deprecate all actorFor methods
* resolveActorRef in provider
* Identify auto receive message
* Support ActorPath in actorSelection
* Support remote actor selections
* Additional tests of actor selection
* Update tests (keep most actorFor tests)
* Update samples to use actorSelection
* Updates to documentation
* Migration guide, including motivation
- Moved system messages to their own package.
- All queueing operations are now hidden behind a SystemMessageList value class
- Introduced dual SystemMessageList types to encode the ordering in the type.
- Protects against accidentally missed reverse calls or accidentally reversed lists
- Makes ordering expectations by fields/parameters explicit
- Fixed serialization tests
- Fixes to logging in HierarchyStressSpec
* Changed TransportAdapterProvider to support java impl
* Verified java impl of AbstractTransportAdapter and
ActorTransportAdapter
* Privatized things that should not be public api
* Consistent usage of INTERNAL API marker in scaladoc
* Added some missing doc in conf
* Added missing SerialVersionUID
- New DeadLetter class for handling remoting specific envelopes
- Fixed error handling of name lookups
- Name lookup is now handled via futures (future refactor opportunity)
- Promise was completed twice erroneously
- Purged the trait Status from Transport, using failed futures instead
- using intercept instead of try ... catch in tests
- added termination hook for UntrustedSpec to shut down second system
- Fixed threading issues in ThrottlerTransportAdapter
- Removed nulls from exception constructors
- replaced Promise.successful(...).future with Future.successful
- Removed HasTransport trait from NettyHelpers
- Fixed unsafe initialization of boss and worker executors in netty driver when using an akka dispatcher
- Transports no longer uses raw ActorRefs as listeners but proper interfaces.
- Added managementCommand support to Transports
- Added support for dynamically loadable transport adapters
- Added throttler/failure injector transport adapter
- added actor based adapter support
- Changed configuration method of multiple transports - Fixed tests to work with the new remoting
- correct registration of endpoints
- passive endpoints now registered to detect parallel incoming connections
- special care to avoid multiple existing endpoints for the same remote addresses (concurrent inbound or outbound communication leads to out-of-order delivery)
- Asynchronous lockless remoting
- Pluggable transport drivers
- Multiple transport support
- Simplified lifecycle events
- Support for netty based TCP, SSL+TCP and UDP support
- Updated Akka protocol with soft-state connections and failure detection
- Refactored failure detectors (currently duplicated from cluster)
