[
https://issues.apache.org/jira/browse/DIRMINA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711353#action_12711353
]
Emmanuel Lecharny commented on DIRMINA-708:
-------------------------------------------
Hi,
I have looked at the traces, but as you can imagine, it's far from being easy
to analyze what's going on. Since you attached it, a major bug has been fixed,
which took me 3 full days (DIRMINA-712).
I understand that it's a major issue for you, but you may also consider that as
volunteers, we have a limited amount of time to work on the project.
As a side effect, yes, sure, if you want to dig into the code, and find a fix,
that would be greatly appreciated ! Anyone can help, this is basically how it
works...
> Unbound thread growth on discovery attempts
> -------------------------------------------
>
> Key: DIRMINA-708
> URL: https://issues.apache.org/jira/browse/DIRMINA-708
> Project: MINA
> Issue Type: Bug
> Reporter: boB Gage
> Attachments: profile-mina.txt.gz
>
>
> Using several different possible protocol handlers (handler, codecs, et al)
> on several potential ports (serial and/or network), our code attempts to
> discover devices on the far end and attach the proper decoders on the proper
> ports.
> Generally, this process is working, however, every failed discovery attempt
> has launched roughly 6 threads, but only destroyed roughly 4 of them. The
> 2 delta threads sit in WAIT states forever.
> More details are available in the "Unbound thread growth" thread of the
> listserv.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
