As marked under this issue, the command callback will not be called if the connection between JGroups peers dies whilst a command is in transit. Credits go to "sgrimm-sg" for filing the issue and solving it.
If cluster connection message came in quickly after starting the connection, a
NullPointerException could be thrown. This issue was resolved for release 4.1 here.
The Mongo extension incorrectly used the content type instead of the tokens type upon storing a serialized token. The issue was marked and resolved under #1.
When using the Kubernetes implementation of Spring Cloud the
SpringCloudCommandRouter would throw
NullPointerExceptions. This occurs because Spring Cloud Kubernetes does not support the
ServiceInstance's meta data field, which the
SpringCloudCommandRouter relies on. This pull request introduced a null check to ensure the null pointer would not be thrown again.
SpringCloudCommandRouter failed to correctly connect to a Spring Cloud Discovery Service if the node did not contain any Command Handler methods. This undesired behaviour was marked by user "travikk" and made more lenient under this.
This release has seen a bunch of adjustments towards the Spring Cloud extension, which can be grouped into two categories. Firstly, the introduction of the
CapabilityDiscoveryMode and secondly the automatic process added to this project:
Introduced GitHub Actions to build, test and push snapshots of the Spring Cloud Extension, as has been marked in pull request #68.
Dependabot was introduced, ensuring all versions will be as up to date as possible.
JUnit4 has been removed entirely, in favor of JUnit 5.
CapabilityDiscoveryMode mode has been introduced through issue #23.
This approach allows for more flexibility when it comes to defining how command routing information should be retrieved and shared.
For a full list of all the changes, please check the release notes.