[
https://issues.apache.org/jira/browse/DIRMINA-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301106#comment-17301106
]
Alexander B commented on DIRMINA-1137:
--------------------------------------
Dear Jonathan,
Sorry for my delay. But your links dont help me.
They dont show, how to solve the problem with Mina specific approaches and
furthermore, even if i use "localhost" or "any other IP within the same
network" oder use InetAddress.getByName(host), in case of the first returned
ICMP the session closes. There must be something I am doing wrong - and I dont
see.
Bests
Alex
> PortUnreachable not check while writing to socket
> -------------------------------------------------
>
> Key: DIRMINA-1137
> URL: https://issues.apache.org/jira/browse/DIRMINA-1137
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1.4
> Environment: Java 1.8, Unix/Windows
> Reporter: Alexander B
> Priority: Critical
> Attachments: exceptionstack.png, minatest2.7z
>
>
> Hi guys,
> My intention is to send udp package to a specific ip and port (even if there
> is not receiver). Me - as the sender - do not have any knowledge about
> (existing) receivers. After receiving a "unreachable port" package back to
> myself (because no receiver exists), the session was closed automatically.
> In your class AbstractPollingIoProcessor from lines 1108ff. in such a case a
> UnreachablePortException was thrown, catched and therefore in line 1112 the
> session was closed.
> In contrast to this, while reading from a socket (lines 560ff.), you are
> distinguishing cases with and without the flag CloseOnPortUnreachable from
> the sessionConfig. [I am not quite sure about my statement here]
> Can you explain, why this was not done at the "writing"-process? Or was there
> anything I missunderstood?
> Thanks
> Alex
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
