Pipe read error

Question

i'm trying to make a ServerSocket that listen for clients and then uses one thread to read from a file and for each client starts another thread, and then as the file is being readed to send data to the other threads and from there to the clients but i've got a little stock
i don't know if i have used how it should the pipe connection; can somebody take a look at it? i would be grateful
thanks
import java.io.*;
import java.net.*;
public class sample_server {
  public static void main(String[] args) {
    try{
      ServerSocket listener = new ServerSocket(Config.port);
      Socket server;
       Reader cititor=new Reader();
       cititor.start();
      while((Config.openConexions++ < Config.maxConnections) || (Config.maxConnections == 0)){
         server = listener.accept();
        Handler conn= new Handler(server,cititor);
        conn.start();
    } catch (IOException ioe) {}
class Config {
static int port=4444, maxConnections=0,openConexions=0;
class Reader extends Thread{
RandomAccessFile file;
public PipedWriter  pipeOut;
char ch;
public Reader(){
try {
file = new RandomAccessFile("c:/student.txt","r");
pipeOut = new PipedWriter();
     catch (IOException e){}
public void run()
     try {
          while (true)
               ch=file.readChar();
               System.out.println(ch);
               pipeOut.write(ch);
          catch(IOException e){}
class Handler extends Thread {
    private Socket server;
    private String line;
     private Reader cititor;
     private PipedReader cit;
     private char ch;
    Handler(Socket server,Reader citeste) {
      this.server=server;
       this.cititor=citeste;
       try {
       this.cit=new PipedReader(cititor.pipeOut);
            catch(IOException e){};
    public void run () {
      try {
        // Get input from the clien
        DataOutputStream out = new DataOutputStream(new BufferedOutputStream(server.getOutputStream()));
        while(true)
               ch=(char)cit.read();
            System.out.println(ch);
      } catch (IOException ioe) {}
}

Answer 1

The basic flaws are that you're not checking for EOS when reading from the file or the pipe, and swallowing exceptions instead of logging them and handling them sensibly, and that you're never closing anything, but the entire scheme doesn't make any sense. If you're trying to serve the contents of 'student.txt' to every client, there is no reason to have the file reading thread at all: just read the file in every client-handling thread. If you want every client to get an arbitrary portion of the file, stick with your current architecture. In reality, the first client to connect will most probably read the entire contents of the file from the pipe, after which the file reader thread can't do anything except exit, so all the other clients will get nothing.