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

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

                Author: ASF GitHub Bot
            Created on: 23/Oct/26 12:23
            Start Date: 23/Oct/26 12:23
    Worklog Time Spent: 10m 
      Work Description: the-thing commented on PR #84:
URL: https://github.com/apache/mina/pull/84#issuecomment-6364782001

   Sure. This is more complex problem and I will not merge it without a proper 
review.
   
   Have a look especially at the test + the attachments 
https://issues.apache.org/jira/projects/DIRMINA/issues/DIRMINA-1205 - the flow 
will be easier to understand.




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

    Worklog Id:     (was: 1049662)
    Time Spent: 1h  (was: 50m)

> 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: 1h
>  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]

Reply via email to