OSSEVA FOR APACHE IGNITE
Ignite 3 is a different product wearing the same name.
Apache Ignite 3 was rebuilt from the ground up — new storage engine, new client API, new SQL engine, new configuration model. It is not an upgrade from 2.x, it is a migration. Meanwhile the 2.x clusters holding production caches and compute grids keep accruing advisories.
Why now
Ignite 3 is a rewrite, not a successor release
Ignite 3 replaced the storage engine, the SQL engine, the client protocol and the configuration model. Applications written against the 2.x cache and compute APIs do not port by changing a version number. That gap is why 2.x clusters are still carrying production load years into the 3.x line's existence.
Attention follows the new line, and 2.x is where the installed base is
Project energy has moved to 3.x. The 2.x series remains in extremely wide production use — in-memory caches fronting relational databases, compute grids running distributed closures, and persistent data regions holding primary copies. Widely deployed and quietly maintained is the exact combination extended support exists for.
Ignite executes arbitrary code by design
The compute grid ships user closures to nodes and runs them. Peer class loading distributes classes across the cluster automatically. These are features, not flaws — but they mean any weakness in node authentication or the discovery protocol converts directly into cluster-wide code execution, and they make an unpatched Ignite cluster a different risk profile from an unpatched cache.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 2.8.x(OSSeva patched) | EOL | Clean |
| 2.9.x(OSSeva patched) | EOL | Clean |
| 2.13.x(OSSeva patched) | EOL | Clean |
| 2.16.x(OSSeva patched) | Extended | Clean |
| 3.x(Rewritten line — upstream maintained) | Current | Clean |
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
CVE patches for Ignite 2.x with the API and storage format unchanged.
- Security backports across the 2.x line
- Discovery, communication SPI and REST advisory coverage
- Peer class loading and deserialization hardening guidance
- Maven / Docker / tarball delivery
- Signed artifacts (GPG)
- Ignite 3 migration assessment
- 24/7 managed operations
OSSeva Assure
Patch plus cluster audit and a costed assessment of the 3.x move.
- Everything in Patch
- Baseline topology and data region configuration review
- Discovery port exposure and authentication audit
- Cache and compute API usage inventory
- SOC 2 / HIPAA attestation package
- Ignite 3 migration assessment with effort estimate
- 24/7 managed operations
OSSeva Operate
Full MSP: 24/7 cluster monitoring, 15-min SLA, named Ignite engineers.
- Everything in Assure
- 24/7 heap, off-heap and baseline topology monitoring
- 15-minute P1 incident response SLA
- Named senior Apache Ignite engineer
- Checkpointing, WAL and rebalance tuning
- Migration execution to Ignite 3 or an alternative grid
- Quarterly capacity planning reviews
All tiers priced per cluster/application — not per core. Contact for pricing →
How it installs
OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.
# Version and topology via the REST connector
curl -s 'http://ignite:8080/ignite?cmd=version'
curl -s 'http://ignite:8080/ignite?cmd=top&attr=true' | jq '.response | length'
# Discovery and communication ports. A node that can join the ring
# can run compute closures — these must not be broadly reachable.
nmap -p 47100,47500,10800,8080 ignite-node.internal<dependency>
<groupId>io.osseva.ignite</groupId>
<artifactId>ignite-core</artifactId>
<version>2.16.1-osseva-1</version>
</dependency>
<dependency>
<groupId>io.osseva.ignite</groupId>
<artifactId>ignite-indexing</artifactId>
<version>2.16.1-osseva-1</version>
</dependency>Migrate from Unsupported Apache Ignite 2.x clusters
OSSeva patches the 2.x line in place, so the cache API, persistence format and client protocol your applications were built against do not change. Where a move is warranted, the assessment costs Ignite 3 against the alternatives honestly — because a rewrite on the vendor's schedule is not automatically the right answer for your estate.
Pricing model
OSSeva for Apache Ignite is priced per cluster — not per node, cache or GB held in memory.
Frequently asked questions
Which versions of RabbitMQ are past community end-of-life?
RabbitMQ 3.8.x, 3.9.x, 3.10.x, 3.11.x, and 3.12.x have all reached community EOL — meaning no further security patches or CVE fixes are released by the RabbitMQ maintainers for those versions. RabbitMQ 3.13.x reached EOL in late 2024. OSSeva delivers backported CVE patches for 3.11 through 3.13.
Which PostgreSQL versions are no longer receiving community security patches?
PostgreSQL 9.6 through 13 have all reached community EOL. PostgreSQL 11 reached EOL November 2023, PostgreSQL 12 reached EOL November 2024, and PostgreSQL 13 reaches EOL November 2025. OSSeva provides extended security patching for PostgreSQL 11, 12, and 13 for teams that cannot immediately migrate to PG 14 or later.
Is Spring Framework 5.3.x still supported?
Spring Framework 5.3.x reached its community OSS EOL on December 31, 2024. Broadcom's commercial support for Spring 5.3.x is also no longer available under standard terms. OSSeva delivers backported CVE patches for Spring Framework 5.3.x and Spring Boot 2.7.x under our extended lifecycle support program.
Which versions of Apache Kafka are EOL?
Apache Kafka versions 2.x and 3.0 through 3.4 are past their community supported window, meaning no further patch releases. Kafka 3.5 and 3.6 have reached or are approaching EOL. OSSeva supports Kafka 2.8 through 3.5 with backported security patches and compliance documentation.
What happened to Redis licensing? Can I still use Redis for free?
In March 2024, Redis Ltd. changed the Redis license from BSD-3-Clause to the Business Source License (BSL 1.1), which restricts use in competing database products. The Valkey project (a Linux Foundation fork) continues under BSD-3-Clause. OSSeva maintains BSD-licensed, CVE-patched builds of Redis 6.2 and 7.0 for enterprises that need verifiable open-source licensing alongside security coverage.
Is Node.js 18 still receiving security patches?
Node.js 18 (LTS 'Hydrogen') reached its end-of-life date in April 2025 and no longer receives security releases from the Node.js project. OSSeva delivers CVE patches for Node.js 18 for enterprise teams that have not yet migrated to Node.js 20 or 22.
Is Apache Tomcat 8.5 still supported?
Apache Tomcat 8.5 reached its community EOL in March 2024. OSSeva provides extended security patching for Tomcat 8.5.x for teams running Java EE 7 workloads that cannot immediately migrate to Tomcat 9.0 or 10.1.
What .NET versions does OSSeva support?
.NET 6 reached Microsoft end-of-support in November 2024. .NET 7 reached EOL in May 2024. OSSeva delivers CVE patches for .NET 6 and .NET 7 for teams that have not yet migrated to .NET 8 (LTS, supported through November 2026).
Ready to get Apache Ignite patched and supported?
Start with a 45-minute discovery call. We confirm your version coverage, scope the engagement, and have you onboarded within your first quarter.