5 Replies Latest reply: Mar 29, 2013 5:46 AM by EJP RSS

    a RMI call is hanging at  java.net.SocketInputStream.socketRead0

    839715
      Hi,

      One of our RMI call is often hanging at java.net.SocketInputStream.socketRead0, the thread stack looks like,

      "RMI TCP Connection(8539)-10.179.38.14" daemon prio=3 tid=0x01d29c00 nid=0x22193 runnable [0xc486e000]
      java.lang.Thread.State: RUNNABLE
      at java.net.SocketInputStream.socketRead0(Native Method)
      at java.net.SocketInputStream.read(SocketInputStream.java:150)
      at java.net.SocketInputStream.read(SocketInputStream.java:121)
      at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
      - locked <0xd8253548> (a java.io.BufferedInputStream)
      at java.io.DataInputStream.readByte(DataInputStream.java:265)
      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:213)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:160)
      at com.nortel.cdma.service.security.SecurityService_Stub.validateLoginParameters(Unknown Source)
      at com.nortel.cdma.service.session.SessionService.createSession(SessionService.java:1388)
      - locked <0xd3d00d80> (a com.nortel.cdma.service.session.SessionService)
      at com.nortel.cdma.service.session.SessionService.createSession(SessionService.java:2849)
      - locked <0xd3d00d80> (a com.nortel.cdma.service.session.SessionService)
      at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:601)
      at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
      at sun.rmi.transport.Transport$1.run(Transport.java:177)
      at sun.rmi.transport.Transport$1.run(Transport.java:174)
      at java.security.AccessController.doPrivileged(Native Method)
      at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
      at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
      at java.lang.Thread.run(Thread.java:722)

      The issue is not 100% reproducible and I have ever googled the issue from Internet and found that somebody said that the heavy system or networking instability will result in the issue...

      I checked the system status when the issue was happending and we still had 3-4G memory left and the free CPU was about 50%.

      Could you please tell me why we will have the problem and how can I solve it?

      Thanks