Port 1979: UniSQL Java — A Database That Lost the Wars

What This Port Does

Port 1979 is officially assigned to UniSQL Java (unisql-java), the Java client connectivity service for the UniSQL database system. Its sibling, port 1978, carries the base UniSQL protocol. Together they formed the network interface for a database system that no longer exists in any meaningful commercial form.

If you see port 1979 open on a modern system, it is almost certainly not UniSQL. Something else is using it.

The UniSQL Story

In May 1990, Dr. Won Kim founded UniSQL with an audacious idea: unify the relational and object-oriented database models into a single system. At the time, this was genuinely controversial. Relational databases dominated the enterprise. Object-oriented programming was rising fast. The question of whether databases would follow was live and contested.

UniSQL/X shipped in March 1992. It was one of the first commercial object-relational database management systems (ORDBMS) — so early that Won Kim and Michael Stonebraker of Illustra disputed who had actually coined the term "ORDBMS." ¹

The system was real enough to earn a registration in the IANA port registry. Port 1978 for the core protocol. Port 1979 for Java connectivity, added as Java became the enterprise language of the late 1990s.

UniSQL did not survive the database consolidation of that era. Oracle, IBM, and Microsoft absorbed or outcompeted most of the innovative database startups of the 1990s. The ports stayed registered. The company did not stay relevant.

Security Note

Port 1979 has a documented association with ZSpyII 0.99b (also known as BackDoor-AGK and Backdoor.ZSpy), a keylogger and remote access trojan from the early 2000s. ² This is common for obscure registered ports: malware authors specifically target ports that legitimate administrators are unlikely to monitor or question.

If you see unexpected traffic on port 1979, treat it seriously. The odds of it being a live UniSQL installation are essentially zero.

How to Check What's Listening

On Linux/macOS:

# Show what process is listening on port 1979
ss -tlnp | grep 1979

# Alternative using lsof
sudo lsof -i :1979

On Windows:

# Show all listening ports with process IDs
netstat -ano | findstr :1979

# Then identify the process
tasklist | findstr <PID>

If you find something listening and you don't recognize it, that is worth investigating.

Why Unassigned-in-Practice Ports Matter

The registered port range (1024–49151) contains thousands of entries like this one — officially assigned, historically meaningful, currently dormant. They matter for two reasons.

First, they create ambiguity. A firewall rule that blocks "unknown" ports might pass port 1979 because it has a legitimate-sounding IANA name. Second, they represent the sediment of computing history. Every registration is a record of someone believing, at a specific moment, that their protocol was important enough to reserve a number forever.

UniSQL believed that in the 1990s. They were not wrong about the technology — object-relational databases did become the standard. They were just not the ones who got to build them at scale.