It’s not possible to for a single instance of ServerSocket to listen to multiple ports. You can of course have multiple ServerSockets. However, as you already know, ServerSocket.accept blocks. What you can use instead is a ServerSocketChannel. They’re used in a similar way, but do not block. If there are no pending connections when ServerSocketChannel.accept … Read more
Basic answer is to use SmbFileInputStream to get InputStream You probably use this. Now the tricky part is how to offer InputStream to other apps. One possible approach, how many apps provide streaming of any InputStream to other apps on device, is to use http: URL scheme, and tunel your stream over http. Then apps … Read more
Usually, I use N+1 threads for this : one for the ServerSocket, to avoid blocking the whole application waiting for a client to connect; and N threads to process the client’s requests, N being the size of the thread pool (I recommend using a thread pool over creating a new thread per client). Here is … Read more
Does it work if you tell Java to use the IPv4 stack? Use the following command line option when starting the server and client. -Djava.net.preferIPv4Stack=true See also here
The correct way to use an AutoCloseable instance is with a try-with-resources block, so the resource is reliably closed even if an exception is thrown. Like this: try (OutputStream stream = new …) { … // use the resource } catch (IOException e) { … // exception handling code } You can also control multiple … Read more
The problem you have is related to TCP streaming nature. The fact that you sent 100 Bytes (for example) from the server doesn’t mean you will read 100 Bytes in the client the first time you read. Maybe the bytes sent from the server arrive in several TCP segments to the client. You need to … Read more
If you know what port the process is running you can type: lsof -i:<port>. For instance, lsof -i:8080, to list the process (pid) running on port 8080. Then kill the process with kill <pid>