[ 
https://issues.apache.org/jira/browse/DIRMINA-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025719#comment-13025719
 ] 

Emmanuel Lecharny commented on DIRMINA-831:
-------------------------------------------

I think this is just a M$ implementation problem.

The Selector.open() method,which is part of the JDK, seems to open a socket. 
There is nothing we can do regarding this issue. 

Note that the number of created Selector will depend on the number of 
processors you have, and it will default to NbCPU +1, thus the 3 sockets in 
TIME_WAIT (in Niklas example, he probably has  a dual core machine) and the 6 
opened sockets might be used for the outgoing data and in going data (thus the 
6 opened TVP connection).

At least, this is what I can deduce from the existing MINA code and the data 
you provided.

We can check in the Java source to see how it's implemented in the M$ land...

> 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

Reply via email to