Uploaded image for project: 'Errai'
  1. Errai
  2. ERRAI-866

Catch "bad payload" exception ... subsequently a Chrome bug (Websocket)

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.1.0.CR1, 3.1.0.Final, 3.1.1.Final, 3.1.2.Final
    • Fix Version/s: 3.2.0.Final
    • Component/s: ErraiBus
    • Labels:
      None

      Description

      The Chrome browser sends a second (unexpected) message (which is valid but empty) when a message was > ~145KB. This results in a RTE "bad payload" because no Errai message can be produced. A further problem is now, because this RTE is not catched and results in a closed socket channel after this error case.

      Most robust solution is to catch any Errai specific exceptions in the endpoint.

      https://code.google.com/p/chromium/issues/detail?id=510016&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mbarkley Max Barkley
                Reporter:
                werrenmi Michel Werren
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: