[ 
https://issues.apache.org/jira/browse/DIRMINA-1146?focusedWorklogId=1040616&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1040616
 ]

ASF GitHub Bot logged work on DIRMINA-1146:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Sep/26 21:56
            Start Date: 09/Sep/26 21:56
    Worklog Time Spent: 10m 
      Work Description: elecharny commented on PR #61:
URL: https://github.com/apache/mina/pull/61#issuecomment-5609285023

   ok, I think the issue is on the client side.
   
   On the server, the connection get closed by the client  thus it can't return 
anything to the client.
   
   I still have no idea why the client closes the connection, I keep digging.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1040616)
    Time Spent: 50m  (was: 40m)

> TLS enabled session got disconnected when outbound messages add up to the 
> value of maxscheduledwriterequests
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRMINA-1146
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1146
>             Project: MINA
>          Issue Type: Bug
>            Reporter: Chily
>            Assignee: Jonathan Valliere
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: ConnectionEndPointIoHandler.java, 
> EmDsectProtocolIoHandlare.java
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Slow Consumer Protection Feature does not work on TLS enabled session
> -> ioSession.getScheduledWriteMessages() never decreases in 
> IoSessionResponder#send method
> internal.engine.session.maxscheduledwriterequests=10000
> Our TLS enabled session got disconneced when the outbound messages added up 
> to 10000.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to