[
https://issues.apache.org/jira/browse/DIRMINA-1205?focusedWorklogId=1049660&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1049660
]
ASF GitHub Bot logged work on DIRMINA-1205:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Oct/26 12:20
Start Date: 23/Oct/26 12:20
Worklog Time Spent: 10m
Work Description: jon-valliere commented on PR #84:
URL: https://github.com/apache/mina/pull/84#issuecomment-6364732207
> > This is the exact class of problem that was brought up two years ago
that led to the experimentation branch which introduced the buggy concurrency.
>
> Are you referring to `org.apache.mina.proxy.filter.ProxyFilter`? Are there
any JIRA's / PR's that you can remember related to that?
>
> Obviously the issue is there and needs to be addressed in one way or
another. Possibly causing some other, undiscovered issues in the meantime until
we get it right.
>
> My first attempt was to fix it inside G0 / G1 handlers, but I don't really
want to touch G0 especially.
I'm referring to my work in G1 and the removal of the synchronized blocks
which led to https://github.com/apache/mina/pull/77 you brought up. G0 would
never support the pattern of having an same-thread consumer blocking on the
write operation because it essentially holds both the read and write locks
simultaneously.
I'd appreciate a week or so for us to discuss and review the problem. I
have a little bit of a time availability problem the next few days.
Issue Time Tracking
-------------------
Worklog Id: (was: 1049660)
Time Spent: 50m (was: 40m)
> Deadlock when using SSL in combination with proxy filter
> --------------------------------------------------------
>
> Key: DIRMINA-1205
> URL: https://issues.apache.org/jira/browse/DIRMINA-1205
> Project: MINA
> Issue Type: Bug
> Components: Core, SSL
> Affects Versions: 2.2.10
> Environment: Windows, Linux, MacOS
> Reporter: Marcin Lamparski
> Priority: Critical
> Attachments: blocking-pipeline-deadlock.dot,
> blocking-pipeline-deadlock.svg, non-blocking-pipeline-deadlock.dot,
> non-blocking-pipeline-deadlock.svg
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> While updating MINA 2.2.10 in QuickFIXj we encountered a deadlock in
> end-to-end SOCKS proxy tests.
> It looks like this was introduced by DIRMINA-1199 fix however all
> combinations of tests fail with a deadlock, which also means that there is an
> existing problem with {{org.apache.mina.filter.ssl.SSLHandlerG0}}
> implementation in versions before 2.2.10.
> Currently I was only able to confirm SSL + SOCKS proxy combination failures,
> but some of the failures in mentioned QuickFIXj PRs look suspicious. It will
> be easier to investigate if we solve this problem first.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
