Tag: release

Morphium 6.3.7 and 6.3.8: Bugs We All Had

Last time it was about bugs nobody ever hit. Morphium 6.3.7 and 6.3.8 are the opposite: bugs we all had, for months, some for years. Found because we put PoppyDB onto a real message bus and looked properly - heap histograms, connection counters, logs. One Double per event that never goes away. 937,000 TCP connections in 61 hours for a client with nothing to do. A watchdog with 2,229 false alarms in a week. And a full-cluster restart that shows why a rolling restart is worthless as a test for restore paths.

Morphium 6.3.1 — and the Transparent Message Bus

We just released Morphium 6.3.1 - officially a bugfix release, in reality the harvest of 6.3.0's first two production weeks: server-side topic filters in the change stream, detection of mixed messaging implementations, and an in-memory driver that now behaves like mongod down to event ordering. And the occasion for the bigger story: why a message bus made of documents is transparent - with a peeker that reads along without consuming, and Morpheus as the cockpit for the running bus. Try that with Kafka 😉

Using a wire proxy to do failover tests

Failover testing with `kill -9` is manual labor and never runs in CI — yet from a driver's perspective, failover bugs are pure wire phenomena. So we moved the faults onto the wire: one TCP proxy per replica set node that can freeze, reset, or cleanly close connections, plus `hello` rewriting so the driver never sees the real addresses. The harness promptly found real bugs — including a read that spent 26 seconds hammering a dead primary.

Morphium 6.2.6: The Timeout That Multiplied Itself by 100

Morphium 6.2.6 is out — and it repairs something that should never have been broken in the first place: replicaset failover. A chain of bugs (chief among them a timeout that silently multiplied itself by 100) meant the driver practically never recovered after the primary died: writes hung, messaging stayed dead. After the fixes: full write throughput ~25 seconds after a kill -9, no lost messages. Also on board: a fix for `findOneAndUpdate` deleting documents instead of updating them on read-cache hits, a self-deadlock in the SingleMongoConnectDriver, and `$setOnInsert`/upsert support in the InMemoryDriver.

Morphium 6.2.5: The One-Document Batch That Cost 20 Seconds

Morphium 6.2.5 is out. A quiet patch release with one loud story: a hardcoded change stream `batchSize=1` that turned into 20-second latency spikes over a high-latency link — plus Atlas TXT seedlist support, Quarkus native-image pre-registration, and a batch of InMemoryDriver and aggregation fixes.

Morphium 6.2.4 — When Messaging Dies Quietly

Morphium 6.2.4 is out. The reason behind it was a bug that took longer to find than to fix. In production, messaging suddenly stopped. The backlog grew. The log said nothing. Only the 10-second fallback poll kept the application half-alive. This is what we learned about producer/consumer architecture, silent `Error`s, and the hard 16 MB BSON limit, and the five layers of protection that came out of it.

Morphium 6.2.2 — Bugfix Release with PoppyDB Hardening and Performance

Morphium 6.2.2 is here — a focused bugfix release that makes PoppyDB significantly more stable. Wire protocol corruption, thread leaks with 20,000 threads per node, and Raft election flapping are fixed. Plus: 4.7x faster startup via ClassGraph caching and PoppyDB is now 3x faster than MongoDB for individual operations.

Morphium 6.2.1 — A Bugfix Release That Packs a Punch

Morphium 6.2.1 is out — and while it's officially a bugfix release, there's considerably more inside than the version number suggests. ByteBuddy replaces spring-cglib, PoppyDB gets a stability overhaul, and the wire protocol is now much more robust against connection chaos.