tyrus
  1. tyrus
  2. TYRUS-163

maxMessageSize is not honored after an incorrect message size is sent once

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0-rc1
    • Component/s: None
    • Labels:
      None

      Description

      Using GlassFish b82 with the following definition:

      @OnMessage(maxMessageSize=6)
      public String echoText(String data)

      { return data; }

      For a freshly deployed app:

      Send a message size <= 6 bytes, works fine.
      Send a message size > 6 bytes, message is not received by the endpoint.
      Send a message size <= 6 bytes, message is not received by the endpoint.

        Activity

        Hide
        jitu added a comment -

        For <=6 case, you mentioned two conflicting results. I suppose
        < 6 works fine
        > 6 doesn't work. Client should receive a specific close code for this, OnError method needs to be invoked.
        = 6 bug ?

        Show
        jitu added a comment - For <=6 case, you mentioned two conflicting results. I suppose < 6 works fine > 6 doesn't work. Client should receive a specific close code for this, OnError method needs to be invoked. = 6 bug ?
        Hide
        Pavel Bucek added a comment -

        fixed in the trunk.

        OnError method is now called on the receiving side (with already closed session).

        feel free to comment/reopen.

        Show
        Pavel Bucek added a comment - fixed in the trunk. OnError method is now called on the receiving side (with already closed session). feel free to comment/reopen.

          People

          • Assignee:
            Pavel Bucek
            Reporter:
            arungupta
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: