Home / FleetMan / Architecture / Pool failover
Architecture

Pool failover

Four Tomcat nodes (app0, app1, iot0, iot1) behind an Nginx proxy with automatic WAR dispatcher. If one server fails, the others take over.

Nginx upstream WAR dispatcher Single MariaDB
Enterprise architecture

What Pool failover does

Nodes

4 Tomcat nodes

app0 + app1 (web/admin) and iot0 + iot1 (tracker gateways).

LB

Nginx load balancer

Round-robin with health checks and sticky WebSocket sessions.

Deploy

Automatic WAR dispatcher

1 upload on malambi.net → copy + reload on all 4 nodes.

Sync

Inter-server sync

ChatPoolHandler propagates messages, presence and reactions.

DB

Single MariaDB DB

All nodes point to gprmc1.malambi.net (dedicated MariaDB).

Admin

Telnet admin port 20000

Real-time console for debug, broadcast, no-downtime reload.

Architecture

How it integrates

The production dispatcher receives the WAR only on malambi.net and distributes it:

scp malambi-fleetman-7.0.1.war root@malambi.net:/home/rootx
# dispatcher.sh → copy to app0/app1/iot0/iot1 → reload Tomcat
Technical specs
ProxyNginx
App nodesapp0, app1
IoT nodesiot0, iot1
DBgprmc1.malambi.net (MariaDB)
Heartbeat60 s inter-server
Failovertransparent to client

Try Pool failover on FleetMan

Bundled with FleetMan — activation is instant. Contact your account manager or start a free trial.

30-day free trial Back to FleetMan