Fork me on GitHub

Basic Usage

junixsocket supports the Java Socket API.

AFUNIXSocket and AFUNIXServerSocket work just like their AF_INET (TCP/IP) Socket counterparts — they extend and respectively. Also check out AFUNIXSocketFactory.

See here how to add junixsocket to your project.

Connecting to an existing AF_UNIX Socket

File socketFile = new File("/path/to/your/socket");
AFUNIXSocket sock = AFUNIXSocket.newInstance();
sock.connect(new AFUNIXSocketAddress(socketFile));

Creating a new AF_UNIX Server Socket

File socketFile = new File("/path/to/your/socket");
AFUNIXServerSocket server = AFUNIXServerSocket.newInstance();
server.bind(new AFUNIXSocketAddress(socketFile));

Complete Examples

junixsocket provides working demos for:

  • Sockets (package
  • RMI over Unix Sockets (packages and
  • MySQL over Unix Sockets (package, also see how to add junixsocket to your MySQL project

You can even run the demos from the command line without having to compile anything.

Adding junixsocket to your project

See here how to add junixsocket to your project, whether you use a dependency management system, or not.


Maximum path length

At the system-level, the maximum length of the pathname referring to a Unix domain socket is restricted and may vary from one OS to another. Currently, junixsocket limits the maximum pathname length to 103 bytes (this may mean fewer characters, depending on the encoding). If the maximum length is exceeded an Exception is thrown.

It is recommended to use short pathnames whenever possible.


Unix domain server sockets are created with read-write privileges for everybody on the system, just like TCP/IP sockets are accessible for local users.

If you want to restrict access to a particular user or group, simply create the socket in a directory that has proper access restrictions.


Whereas TCP/IP sockets point to ports at particular Internet addresses, AF_UNIX sockets point to special files on the local file system. The notion of “port” is not necessary in this case.

However, junixsocket supports the concept of “ports” in AFUNIXSocketAddress, in order to enable features like Java RMI.

Port support may also come handy in other situations, especially when an existing application expects a particular port on a Socket. Please be aware that specifying a particular port number has no effect for non-RMI connections.