You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Christian Schwarz (JIRA)" <ji...@apache.org> on 2011/04/26 14:13:03 UTC

[jira] [Updated] (DIRMINA-831) NioSocketConnector create unused Connections, even when #connect(..) is not called.

     [ https://issues.apache.org/jira/browse/DIRMINA-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schwarz updated DIRMINA-831:
--------------------------------------

    Attachment: DIRMINA-831.jpg

> 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.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