Socket.getInputStream hangs

Question

I have a simple client/server app, and the client hangs when I try to get the input stream coming out of the server. I have the following code on the server:
ObjectOutputStream oos = null;
ObjectInputStream ois = null;
port = 49152;
server = new ServerSocket(port, 0, InetAddress.getLocalHost());
sock = server.accept();
oos = new ObjectOutputStream(sock.getOutputStream());
ois = new ObjectInputStream(sock.getInputStream());
String inMsg = (String) ois.readObject();
oos.writeObject(outMsg);
oos.close();
ois.close();
sock.close();And I try to invoke it with this code on the client:
ObjectOutputStream oos = null;
ObjectInputStream ois = null;
String inMsg = "";
int port = 49152;
try {
     Socket sock = new Socket(InetAddress.getLocalHost(), port);
     oos = new ObjectOutputStream(sock.getOutputStream());
     ois = new ObjectInputStream(sock.getInputStream());//the code hangs here
     oos.writeObject(outMsg);
     inMsg = (String) ois.readObject();
        oos.close();
     ois.close();
     sock.close();
} catch (Exception e) {
     return "";
return inMsg;
     The code hangs where indicated in the comments. Can someone tell me what I'm doing wrong?
Edited by: MidnightJava on Apr 10, 2008 4:55 AM

Answer 1

Can you please explain the rationale for your suggestion? What sort of problem is it addressingThe constructor for ObjectOutputStream writes a header to the stream. The constructor for ObjectInputStream reads it. Try constructing them in the opposite order at both ends and you will see a lovely deadlock. The flush() is required if there is a BufferedOutputStream under the ObjectOutputStream.
is it a good idea to do it always when creating streams from a socket?It's essential when dealing with object streams. Other streams, no.