[DIRMINA-1146] Pass message to next filter in SslFilter - #61
Conversation
|
Hi, thanks for the proposed patch. I'm not sure it's related, but I don't have this failure when I don't apply your proposed patch. I have tested with Java 17 and 25. If I run the exact same class test in eclipse, it passes green... Go fish... I'm trying to see what could be the cause of this issue (beside the fact the connection has been closed) |
|
Hello, I was getting slightly different error for Windows 11 / temurin / Java 17 I also consistently get an error on 2.2.x
Let me have a look as well. |
|
I also have the same issue with the NPE when the message is sent back to the IoHandler. Now to understand why the socket has been closed... |
|
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. |
Fixes DIRMINA-1146
It will also help fix quickfix-j/quickfixj#406
Changes
Currently none of the
EncryptedWriteRequestinstances have parent message provided which means that original message and request is always the same instance. We must pass all the messages down the chain.org.apache.mina.filter.ssl.SslFilternow also passes the encrypted message down the filter chain, eventually reachingorg.apache.mina.core.filterchain.DefaultIoFilterChain.TailFilterwhich will increase the written message count and also decrement scheduled message count.Obviously this change will have an impact filters configured between
org.apache.mina.filter.ssl.SslFilterandorg.apache.mina.core.filterchain.DefaultIoFilterChain.TailFilter, but I think users should make changes accordingly in this case.