Very strange : android using the socket abnormal setsockopt failed: EBADF (Bad file number)

 finally {
  	        	Log.i("bai", " finally socket finally  isConnected : "+ socket.isConnected());
  	        	Log.i("bai", "socket info : "+ socket.toString() );
  	        	Log.i("bai", "socket isConnected : "+ socket.isConnected());
                	if (null != socket) {
                		try {
  //              			if(dis != null) {
  //              				dis.close();
  //              			}
                			Log.i("bai", "socket isConnected null != socket: "+ socket.isConnected());
                			Log.i("bai", "socket.isClosed(): "+ socket.isClosed());
                			socket.setSoTimeout(0);
                		} catch(SocketException se) {
                			Log.i("bai",se.getMessage());
                			throw new PushException(se, ErrorType.Err_Read);
                		} catch(IOException ie) {
                			throw new PushException(ie, ErrorType.Err_Read);
                		}
                 	}
  	        }

This finally is executed at the end of the read socket , but the strange thing is that people in the socket is not empty , is also connected to the case , I set the socket timeout never discovered setsockopt failed: EBADF ; (Bad file number) problems, leading to abnormal shutdown socket . Internet did not find detailed information , please help fellow facie , very thank you! ! !

08-22 08:34:11.452: I/bai(6466): [SocketRead_08:29:07-227] finally socket finally  isConnected : true(pushagent/SSLPushChannel.java:344)
  08-22 08:34:11.452: I/bai(6466): [SocketRead_08:29:07-227]socket info : Socket[address=/122.11.38.26,port=5223,localPort=60280](pushagent/SSLPushChannel.java:345)
  08-22 08:34:11.452: I/bai(6466): [SocketRead_08:29:07-227]socket isConnected : true(pushagent/SSLPushChannel.java:346)
  08-22 08:34:11.452: I/bai(6466): [SocketRead_08:29:07-227]socket isConnected null != socket: true(pushagent/SSLPushChannel.java:352)
  08-22 08:34:11.452: I/bai(6466): [SocketRead_08:29:07-227]socket.isClosed(): false(pushagent/SSLPushChannel.java:353)
  08-22 08:34:11.462: I/bai(6466): [SocketRead_08:29:07-227]setsockopt failed: EBADF (Bad file number)(pushagent/SSLPushChannel.java:356)
  08-22 08:34:11.462: I/bai(6466): [ 08-22 08:34:11.471  6466:0x19ad E/connect cause :com.huawei.android.pushagent.datatype.PushException: java.net.SocketExceptio[SocketRead_08:29:07-227]ssl_push_thread(pushagent/SSLPushChannel.java:254)
  

------ Solution ------------------------------------- -------
direct socket.close not? Why must add socket.setSoTimeout (0); do ?

If you want to terminate the socket input or output , you can add :

  if(null != socket && socket.isConnected)
  {
  socket.shutdownInput();
  socket.shutdownOutput();
  }
  

------ eference ------------------------------------- -
socket.setSoTimeout (0);
is never set socket timeout
------ eference ------------------------------ ---------
problem has been resolved ! ! !
The reason is because the java each GC , the garbage collector will reuse the ParcelFileDescriptor session parameters are recovered , leading to push connection SSLsocket become false connections , then socket.isConnected () = true. But in fact the socket connection has become unavailable or is broken , save the next reasonable parameters can be reused in the next .
------ eference --------------------------------------- < br> android using the socket abnormal setsockopt failed: EBADF (Bad file number)

I also encountered the same problem here , and now there is no information on the Internet to find , to say in detail what the next solution ?
------ eference --------------------------------------- < br> So, now how to deal with the landlord ?
------ eference --------------------------------------- < br> Will you solve the problem yet
------ eference -------------------------------- -------
landlord how to deal with that now ?  
landlord said about the treatment of it ! ! ! !
------ eference --------------------------------------- < br> the landlord said that under the specific methods , thank you