[
https://issues.apache.org/jira/browse/DIRMINA-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025779#comment-13025779
]
Francesco Vivoli commented on DIRMINA-831:
------------------------------------------
Just to clarify: The bug report states that these pipes weren't managed
properly and is reported to having been fixed. Nevertheless, as of Java
1.6.0_17 the WindowsSelectorImpl implementation that uses sockets is still
there... Not a Mina issue though.
> NioSocketConnector create unused Connections, even when #connect(..) is not
> called.
> -----------------------------------------------------------------------------------
>
> Key: DIRMINA-831
> URL: https://issues.apache.org/jira/browse/DIRMINA-831
> Project: MINA
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.2
> Environment: win32, x86, winXP
> Reporter: Christian Schwarz
> Attachments: DIRMINA-831.avi, DIRMINA-831.jpg
>
>
> Hello,
> we are using Mina to access different types of network devices (Webcams,
> Digital-IO-Boxes, Access Control Systems,...). For every type of device we
> use a dedicated IoConnector because of the different protocols. Under some
> circumstances we get an "java.net.SocketException: No buffer space available
> (maximum connections reached?): connect". We figured out that for every
> created NioSocketConnector 8 connections will be created from localhost to
> localhost with different ports, even if we do no connect at all. So if we use
> many NioSocketConnector's we quickly run out of available ports, i guess.
> Is it possible to tune the NioSocketConnector so it only opens a port when
> we call #connect(..) ?
> Thanks in advance
> Chris
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
