[
https://issues.apache.org/jira/browse/DIRMINA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711645#action_12711645
]
Emmanuel Lecharny commented on DIRMINA-708:
-------------------------------------------
Seems that the app is not blocked in the PdrProtocolEngine.messageSent()
method, but more likely on the WriterMonitor wait then. Which makes sense ...
So I guess that this call to the remove() method is mandatory at some point, in
order to get the flush() method to be called. This part of the code is not one
I'm comfortable with, as I never used it. I guess that closing the session
should either call the remove() method before or do it inside the close()
handling at some point.
> 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.
