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

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

                Author: ASF GitHub Bot
            Created on: 09/Oct/26 17:47
            Start Date: 09/Oct/26 17:47
    Worklog Time Spent: 10m 
      Work Description: the-thing opened a new pull request, #78:
URL: https://github.com/apache/mina/pull/78

   We fixed it in https://github.com/apache/mina/pull/75 but it still fails 
from time to time e.g 
https://github.com/apache/mina/actions/runs/37960280693/job/113921075126
   
   The problem is that the test assertion relies on exception capture via 
`org.apache.mina.util.ExceptionMonitor` which is static and accessed from many 
classes.
   
   **Changes**
   
   I added filtering to only count failures when exceptions are throw from 
`org.apache.mina.transport.socket.nio.NioDatagramAcceptor` directly which was 
the original issue.
   
   **Alternative**
   
   One of the alternative fixes is to provide an instance exception monitor 
field to `NioDatagramAcceptor` that is only visible to the test.




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

    Worklog Id:     (was: 1046635)
    Time Spent: 50m  (was: 40m)

> Concurrent Bug while having 2 DatagramAcceptors
> -----------------------------------------------
>
>                 Key: DIRMINA-1140
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1140
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.21
>            Reporter: Alexander B
>            Assignee: Jonathan Valliere
>            Priority: Major
>              Labels: bug
>             Fix For: 2.2.10
>
>         Attachments: CmdException.JPG, MinaDatagramException.zip, 
> Send-UdpDatagram.ps1, exception.PNG, minaException.png
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Hello,
> We have created 2 DatagramAcceptors running completely independently. 
> It seems, that just one at a time is working. We receive 
> java.concurrent-Exceptions sometimes.
> These exceptions are thrown from a running thread, which do not have any 
> calling classes from our code. Attached you will find the complete exception 
> stack.
> Do you have any ideas about this?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to