[
https://issues.apache.org/jira/browse/DIRMINA-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Brown updated DIRMINA-782:
-------------------------------
Attachment: FileRegionWriteFilterTest.java
This file demonstrates the problem described in this bug. The expected
behavior would be to see the following messages on stdout.
messageReceived: HeapBuffer[pos=0 lim=6 cap=37: 61 64 73 66 0D 0A]
messageSent: HeapBuffer[pos=0 lim=11 cap=11: 74 65 73 74 20 73 74 72 69 6E 67]
messageSent: org.apache.mina.core.file.defaultfilereg...@1f950198
session closed (0x00000001: nio socket, server, /127.0.0.1:44888 =>
/60.127.0.0:46609)
However, the follow messages are actually seen with 2.0.0-RC1 code:
messageReceived: HeapBuffer[pos=0 lim=6 cap=37: 61 73 64 66 0D 0A]
messageSent: org.apache.mina.core.file.defaultfilereg...@203fa5ac
messageSent: HeapBuffer[pos=0 lim=3923 cap=3923: 2D 2D 2D 20 2F 68 6F 6D 65 2F
61 62 72 6F 77 6E...]
session closed (0x00000001: nio socket, server, /127.0.0.1:33608 =>
/3.127.0.0:30214)
> Combination of SslFilter & FileRegionWriteFilter causes messageSent events to
> be lost
> -------------------------------------------------------------------------------------
>
> Key: DIRMINA-782
> URL: https://issues.apache.org/jira/browse/DIRMINA-782
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0-RC1
> Reporter: Adam Brown
> Attachments: FileRegionWriteFilterTest.java
>
>
> When SslFilter & FileRegionWriteFilter are the last 2 filters on the outgoing
> end of a filter chain, you lose the messageSent notification for an IoBuffer
> if a write of the IoBuffer is immediately followed by a write of a FileRegion.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
