Solace

Solace Workload Balancer

Technical status and test controls for ordered event-family routing across three brokers.
How to read this page

Rates are recent messages/second. Target is requested generation; accepted and delivered are observed.

Accepted means the publisher wrote a durable local outbox receipt. It is not a broker ACK.

Backlog is current queue message depth from SEMP meta.count, never the cumulative lifetime spool counter.

Latency is the recent dashboard-observed submit-to-delivery interval. It is not a full distributed trace or SLA.

Order / duplicate checks use a bounded in-memory observation window per run, group, and entity. They do not prove exactly-once delivery.

Assignments are cumulative publisher choices since this dashboard process started; queue rates show current broker activity.

Membership is authoritative control state. ACTIVE serves traffic; epoch identifies the routing generation.

SDKPerf is optional test-only SMF/JCSMP source and sink tooling bridged through the native Go AMQP shims.

Routing topology

Current process observations
Ingress

Publisher shim

One stable ordering key per family · customer hash and rendezvous selection
Egress

Subscriber shim

Family-local sequence is observed before application ACK

Event-family routing

All five use scaling group events-a. The real rendezvous contract maps the selected keys 2–2–1 across Brokers 1/2/3. Equal 20/s family rates produce a measured 40/40/20 split.

Process health

Current supervised Go processes and process-lifetime restart counts.

Membership

Controller-authoritative phase, epoch, and active broker IDs.

SDKPerf test environment

Optional test tooling only. Managed tests use SDKPerf as the SMF source and sink, with the existing Go publisher/subscriber shims carrying the workload across all active brokers.

Unlock controls to edit and run SDKPerf tests.
Direct SDKPerf CLI examples

Prerequisites: Java, the official SDKPerf Java package, and private values exported as SDKPERF_CMD, SMF_URL, SDKPERF_USERNAME, VPN, and SDKPERF_PASSWORD. Start the subscriber first.

Direct broker smoke test — bypasses the shims. It uses a dedicated topic and does not test Broker 0 discovery or rendezvous placement.

"$SDKPERF_CMD" "-cip=$SMF_URL" "-cu=$SDKPERF_USERNAME@$VPN" "-cp=$SDKPERF_PASSWORD" -mt=persistent -stl=swlb-sdkperf/direct-smoke -md
"$SDKPERF_CMD" "-cip=$SMF_URL" "-cu=$SDKPERF_USERNAME@$VPN" "-cp=$SDKPERF_PASSWORD" -mt=persistent -ptl=swlb-sdkperf/direct-smoke -mn=100 -mr=25 -msa=256 -ped=2

Recent generic events

A bounded, sanitized display window—not an audit log. Event IDs are replaced before publication.

TimeGroupEvent IDEntityDuplicate