[
https://issues.apache.org/jira/browse/DIRMINA-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711638#action_12711638
]
boB Gage commented on DIRMINA-708:
----------------------------------
I'm unsure as to how anything could get stuck inside
PdrProtocolEngine.messageSent(), the entire method is reproduced here:
public abstract class PdrProtocolEngine extends IoHandlerAdapter {
...
@Override
public final void messageSent(IoSession session, Object message) {
logger.debug("messageSent(session, " + message + ")");
}
...
}
Is there some step I've missed that I should be doing in the overridden
method?? This particular one was a placeholder we never went anywhere with;
I'll try simply removing it to see if the problem disappears.
----
I do recall one of the changes we had to do when updating to M4 (I think we
were at M2 before that?) -- we had been using IoSession.closeOnFlush() which
got removed so we had to drop back to a straight close() method.
Since then our code has called close methods, but there is no flush anywhere
that we use or that I am aware of.
Matter of fact, a search for flush through our project uncovers only my notes
from that upgrade and from chasing this bug -- we have zero specific flush
calls in our code.
Is this a problem?? I assumed Mina will flush the sessions it is closing --
or at least trigger whatever threads it may have launched to control that
session. Is there something more I should do beyond calling the
IoSesison.close() method to bring down a session that fails discovery??
----
Digging now... more later
> 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.
