JFR events SocketReadEvent/SocketWriteEvent should contain exception information

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: core-libs
    • None

      Currently the JFR events SocketReadEvent and SocketWriteEvent are generated with a zero length transfer size when an exception occurs. Although a separate exception event is generated, it can be inconvenient to associate with the read/write that generated it. The SocketReadEvent and SocketWriteEvent can have an extra field with the exception message or null if the operation was sucessful.

            Assignee:
            Tim Prinzing (Inactive)
            Reporter:
            Tim Prinzing (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: