Uploaded image for project: 'MINA'
  1. MINA
  2. DIRMINA-976

ScheduledWriteBytes Increases after Exception on Writing

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.7
    • Fix Version/s: 2.0.14
    • Component/s: None
    • Labels:
      None

      Description

      If an exception occurs during sending of a message with another message in the queue already, there's a chance that the fields scheduledWriteBytes and scheduledWriteMessages in the IoAcceptor never return to 0.

      1. Mina2MinaServer.java
        4 kB
        Henning Rohlfs
      2. Mina2MinaClient.java
        2 kB
        Henning Rohlfs

        Activity

        Hide
        elecharny Emmanuel Lecharny added a comment -

        I would say this issue has been fixed with the fix for DIRMINA-1021 : we now close the sessions immediately, so nothing can be flushed anymore, when we have an exception.

        Show
        elecharny Emmanuel Lecharny added a comment - I would say this issue has been fixed with the fix for DIRMINA-1021 : we now close the sessions immediately, so nothing can be flushed anymore, when we have an exception.
        Hide
        elecharny Emmanuel Lecharny added a comment -

        The counters were badly protected against concurrent access. This has been fixed recently, but it would be valuable to check that those counters are correctly handled even if we have an exception.

        The scheduledWriteBytes counter is updated in two places :

        • in the session
        • in the service

        Now, I suspect the scheduledWriteBytes counter is updated in two different places, leading to inconsistancies. To be double checked.

        Show
        elecharny Emmanuel Lecharny added a comment - The counters were badly protected against concurrent access. This has been fixed recently, but it would be valuable to check that those counters are correctly handled even if we have an exception. The scheduledWriteBytes counter is updated in two places : in the session in the service Now, I suspect the scheduledWriteBytes counter is updated in two different places, leading to inconsistancies. To be double checked.
        Hide
        xehonk Henning Rohlfs added a comment -

        Attached a simple client/server testcase which reproduces this behaviour.

        Show
        xehonk Henning Rohlfs added a comment - Attached a simple client/server testcase which reproduces this behaviour.

          People

          • Assignee:
            Unassigned
            Reporter:
            xehonk Henning Rohlfs
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development