2.8.0 - Added support for lame duck mode notification

• Added lame-duck mode support 334

When a server goes into lame-duck mode. The client will send out a connection event.

Example code registering for lame-duck mode.

            Options options = new Options.Builder().server(ts.getURI()).connectionListener(new ConnectionListener() {
                @Override
                public void connectionEvent(Connection conn, Events type) {
                    if (type.equals(Events.LAME_DUCK)) connectLDM.complete(type);
                }
            }).build();

            Connection nc = Nats.connect(options);

Lame-duck mode is for servers in a cluster to tell clients that they will no longer be serving requests.
Clients can get notified of this and gracefully perform some actions.

2.7.0

Miscellaneous Updates

• [ADDED] #323 Nats.connect v2 credentials (@olicuzo)
• [CHANGED] #320 Update MAINTAINERS.md (@gcolliso)

Bug Fixes

• [FIXED] #318 Printing trace when NUID initialization takes long (@matthiashanel)
• [FIXED] #327 Subject Remapping Fix (@brimworks)
• [FIXED] #331 Close connection when flush fails during drain (@matthiashanel)
• [FIXED] #330 Reconnect wait was not being honored (@ColinSullivan1)

2.6.8 - reconnect improvements

2.6.8 - reconnect improvements.

Changed the reconnect logic so it does not try to connect to a server that it just lost the connection to.

With the randomization algorithm, there's a chance the client will immediately try the server it just lost connection with. Move the last connected server to the end of the list when reconnecting.

• [FIXED] - #309 - Removed some debug printf statements
• [CHANGED] - Allow disable reconnect buffer by using size of zero
• [CHANGED] - Added option to set the max unsent size at the writer and fail or discard messages
• [CHANGED] - Updated build.gradle to not fail if TRAVIS_BRANCH isn't set

Reconnect cleanup

• Reconnect cleanup #300
• [FIXED] Make jwtFile optional in Nats.credentials
• [FIXED] Javadoc of Message.getSID()
• Minor readme and documentation fixes

2.6.6

[FIXED] - #274 - Added a check to prevent double event notification
[CHANGED] - #276 - Updated TLS certs to match go client
[FIXED] - #275 - Updated connect to randomize with the same code as reconnect

2.6.5

2.6.5 is a test release to check automated maven releases. No code changes effect the running library.

2.6.4

2.6.4 is a test release with no code changes but major build changes to support automated release.

2.6.3

Bumped version to test automated deploy.

2.6.2

Bumped version to replace maven packages built with JDK 11 with ones built with JDK 8

2.6.1

• [FIXED] - #263 - Added server URLs to connect exception (not to auth exception)
• [FIXED] - #262 - Added @deprecated as needed
• [FIXED] - #261 - Added a static credentials implementation that uses char arrays
• [FIXED] - #260 - Moved to nats-server from gnatsd for testing
• [FIXED/CHANGED] - #259 - Double authentication errors from a server during reconnect attempts will result in the connection being closed.
• [FIXED] - #257 - Added connection method to messages that come from subscriptions, dispatchers and requests
• [FIXED] - #243 - Added check for whitespace in subjects and queue names
• [FIXED] - Improved a couple flaky tests