[
https://issues.apache.org/jira/browse/DIRMINA-1146?focusedWorklogId=1040652&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1040652
]
ASF GitHub Bot logged work on DIRMINA-1146:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 10/Sep/26 06:14
Start Date: 10/Sep/26 06:14
Worklog Time Spent: 10m
Work Description: elecharny commented on PR #61:
URL: https://github.com/apache/mina/pull/61#issuecomment-5614046859
Ok, I was totally wrong. The server do close the connection, and more
specifically the `messageReceive()` method does it when it has received 2
messages.
The key here is that the `IoHandler` receives Handshake massages, which is
totally wrong. So it all has to do with the change done. We have to find a way
to *not* send HS messages to the `IoHandler`.
Here are the logs:
```
------------------------------------Message sent: HeapBuffer@5ab35b18[pos=0
lim=1427 cap=33418: 16 03 03 00 7A 02 00 00 76 03 03 1B 0E 3F 5E D7]
...
and then later on:
```
------------------------------------Message sent: HeapBuffer@63d87619[pos=0
lim=1210 cap=33418: 17 03 03 04 B5 27 B5 4E 9A 80 91 A9 A5 22 55 A1]
```
I have changd the `messageSent` method to print that logs:
```
@Override
public void messageSent(IoSession session, Object message) throws
Exception {
System.out.println( "------------------------------------Message
sent: " + message );
sentMessages.add(message.toString());
if (sentMessages.size() >= 2) {
session.closeNow();
}
}
```
and we can clearly see that we are dealing with TLS messages: 16 is for a HS
TLS message, 17 is the wrapped message, crypted.
Issue Time Tracking
-------------------
Worklog Id: (was: 1040652)
Time Spent: 1h 20m (was: 1h 10m)
> 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: 1h 20m
> 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]
