Releases: MindsIgnited/continuum-framework
Releases · MindsIgnited/continuum-framework
Release list
3.1.1 release
Features
- Vert.x runs on the native transport when the platform has one (#58).
continuum.prefer-native-transport(defaulttrue) setsVertxOptions.preferNativeTransportfor both clustered and single-node Vert.x.continuum-core-vertxshipsnetty-transport-native-epollforlinux-x86_64andlinux-aarch_64as runtime dependencies. Netty loads the one matching the CPU, and Vert.x falls back to NIO elsewhere (macOS). - At startup continuum logs which transport Vert.x is using, warning on Linux if it fell back to NIO.
Why
Vert.x applies TCP options like TCP_USER_TIMEOUT and keepalive tuning only on a native transport; NIO ignores them. Structures' Elasticsearch client sets them so a connection to a node that vanished without closing it is dropped within seconds.
Notes for consumers
ContinuumProperties.isPreferNativeTransport()is a default method returningtrue; existing implementations keep compiling.- On Linux, every Vert.x server and client now runs on epoll by default. Set
continuum.prefer-native-transport=falseto return to NIO while troubleshooting.
What's Changed
- feat: run Vert.x on the native transport when the platform has one by @NickPadilla in #58
- Release 3.1.1 by @NickPadilla in #59
Full Changelog: 3.1.0...3.1.1
3.1.0 release
What's Changed
- Resolves Gh-40 by @NavidMitchell in #42
- Reply to by @NavidMitchell in #46
- Optimize service RPC delivery by preferring local handlers by @NavidMitchell in #53
- fix: adjusting pipeline by @NickPadilla in #54
- Cicd work by @NickPadilla in #55
- fix: repair the clienttest/development profile yml; add a delayed reply to the clienttest service by @NickPadilla in #56
- Release 3.1.0 by @NickPadilla in #57
New Contributors
- @NavidMitchell made their first contribution in #42
Full Changelog: 2.5.2...3.1.0