Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4976710

JSR160 - JMXMP connector throws EOFException when stopping

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P3
    • 1.0.1
    • 1.0
    • core-svc
    • None
    • 1.0.1
    • unknown
    • generic
    • Verified

    Description

      This behavior appears with b41. It was not there with previous build b40_a.
      It seems printed each time you stop the connector.
      As in previous build, it was not printed, do we really need it now ?
      When the customer does stop a connector, he is ok with the fact various streams will close, no need to warn him about it !
      It has a side effect on the TCK making several tests seen as failed by the harness even they passed.

      Typical stacks :

      Jan 12, 2004 1:25:51 AM GenericConenctor RequestHandler-connectionException
      WARNING: java.io.EOFException
      java.io.EOFException
      at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2435)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1245)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
      at com.sun.jmx.remote.socket.SocketConnection.readMessage(SocketConnection.java:211)
      at com.sun.jmx.remote.generic.SynchroMessageConnectionImpl$MessageReader.run(SynchroMessageConnectionImpl.java:440)
      at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)
      at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)

      or

      Jan 12, 2004 1:05:10 AM GenericConenctor RequestHandler-connectionException
      WARNING: java.io.EOFException
      java.io.EOFException
      at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2435)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1245)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
      at tests.api.share.utils.MessageConnectionForGeneric.readMessage(MessageConnectionForGeneric.java:185)
      at com.sun.jmx.remote.generic.SynchroMessageConnectionImpl$MessageReader.run(SynchroMessageConnectionImpl.java:440)
      at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)
      at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)

      Sometimes, the stack is printed after another message such as :

      Jan 11, 2004 11:33:49 PM ClientCommunicatorAdmin restart
      WARNING: Failed to restart: java.io.IOException: The connector is not at the connection state.

      Parenthesis : note the typo 'GenericConenctor' in messages.

      ----
      With b42:
      Jan 15, 2004 1:38:35 AM GenericConenctor RequestHandler-connectionException
      WARNING: java.io.EOFException
      java.io.EOFException
      at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2435)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1245)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
      at com.sun.jmx.remote.socket.SocketConnection.readMessage(SocketConnection.java:211)
      at com.sun.jmx.remote.generic.ClientSynchroMessageConnectionImpl$MessageReader.run(ClientSynchroMessageConnectionImpl.java:393)
      at com.sun.jmx.remote.opt.util.ThreadService$ThreadServiceJob.run(ThreadService.java:208)
      at com.sun.jmx.remote.opt.util.JobExecutor.run(JobExecutor.java:59)
      ###@###.### 2004-01-15

      Attachments

        Activity

          People

            sjiang Shanliang Jiang (Inactive)
            yjoan Yves Joan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: