Apache ServiceComb
Microservice framework with service registry and governance
ServiceComb Java-Chassis is in pure maintenance: two branches, mostly Netty and Vert.x bumps.
◆Recent moves
- 1mo ago
2.9.5 fixes an OOM on large SSE responses
Fixes an out-of-memory condition when a large response arrives over a server-sent-events interface, plus the recurring Netty and Vert.x upgrade. The OOM fix is the only user-visible correctness change in this release and came from a first-time contributor.
View source ↗ - 3mo ago
2.9.4 updates the JDK version and fixes producer selection
A JDK version update, project management housekeeping for the Archaius component, and a fix for the wrong ProduceProcessor being chosen when produces is null. Small enough that the null-produces fix is the only thing an application would notice.
View source ↗ - 4mo ago
2.8.31 bumps Netty and Vert.x and moves SSL config reads
Two changes: the recurring Netty and Vert.x upgrade, and SSLOption and KeyPairUtils switching to the Environment abstraction for configuration reads. Maintenance-branch housekeeping with no behavioural change intended.
View source ↗ - 6mo ago
2.9.3 fixes delayed instance pulls after registry changes
Fixes a case where service instances were not pulled immediately after a watched registry-center change — a real availability problem, since it means clients keep routing to a stale instance list. Bundled with a Spring Boot dependency bump and another Netty and Vert.x upgrade.
View source ↗ - 6mo ago
2.8.30 backports the registry pull fix to the older branch
The 2.8.x cut of the same two changes released as 2.9.3 a minute earlier: the Netty and Vert.x upgrade and the delayed instance pull fix. A backport rather than independent work.
View source ↗ - 8mo ago
2.8.29 fixes RBAC registration in dual-engine failover setups
Fixes microservices failing to register when RBAC authentication is enabled in a dual-engine disaster recovery scenario, alongside a Tomcat embed upgrade. The specificity of that scenario is evidence the framework is still carrying real production deployments.
View source ↗