Java - Sockets, writing data and shutdownOutput

I too would like to see a log extract *and* the logging code that produces it

Thanks all for the replies.
Below are the logs:
2009-08-20 08:09:17,436 [SessionH] INFO: Closing output
2009-08-20 08:28:43,369 [SessionH] INFO: HttpConnection disconnected

Please note the time response. SessionH is a thread which will monitor all the sessions on our server. And will take some actions.

Please see attached code.
Any help from here, would be greatly appreciated.

public void disconnect()
    {
        if (socketClosed) return;
        try {
               	log.info("Shutting down input");
            	s.shutdownInput();
            	log.info("Shut down input");
	
              	log.debug("Closing output");
            	bout.flush();
            	s.shutdownOutput();
           	outputShutdown = true;
 
   		s.close();
            	socketClosed = true;
            	log.info("HttpConnection disconnected");
        } catch (IOException x) {
        }
    }

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:

Are you sure the closing message and disconnected message belong to the same session?

Yes CEHJ. Both belonging to same session.
The original message is as below:
2009-08-20 08:09:17,436 [SessionH] <6n8lpdyD4bnduj0aVfoBrV6> DEBUG: Closing output
2009-08-20 08:28:43,369 [SessionH] <6n8lpdyD4bnduj0aVfoBrV6> INFO: HttpConnection disconnected

6n8lpdyD4bnduj0aVfoBrV6 - is our Session ID

I can say, It could be blocking in one of below locations.

bout.flush()                                      or
s.shutdownOutput()                        or
s.close()

Any thoughts or comments?

I am sorry guys, bit late in delay to respond.

Thanks objects & CEHJ for helping me out. One last question.

1. I have below timeout settings configured.
        s.setSoTimeout(0);
        s.setSoLinger(true, 0);
        s.setTcpNoDelay(true);

2. My question is on setting SoLinger(true,0). setting linger to "true" and linger time out to "0" means - stop reading & sending the data immediately. Data in sent & receive buffer will be DISCARDED. And finally socket will be closed immediately.

My doubt is - If the client is already expecting some data from the server (please note that there is no time out set) and we have closed our send & receive buffer by discarding it.
Is there any chance to hang at socket.close() statement, because client is already called socket.read()....??? Since, there is no socket timeout set, calling socket.read() will never gets terminated....

Any ideas?

you haven't answered why you are trying to close the socket explicitly
what happens when you just close the stream?

> you haven't answered why you are trying to close the socket explicitly
what happens when you just close the stream?

TBF, I am not the designer of this code. Working to fix one issue. You are right, if we close the stream that should also be fine. I can keep this in my mind.

Please could you confirm my below doubt, does it make sense?

>>> My doubt is - If the client is already expecting some data from the server (please note that there is no time out set) and we have closed our send & receive buffer by discarding it.
Is there any chance to hang at socket.close() statement, because client is already called socket.read()....??? Since, there is no socket timeout set, calling socket.read() will never gets terminated....