[
https://issues.apache.org/jira/browse/DIRMINA-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022689#comment-13022689
]
Christian Schwarz commented on DIRMINA-831:
-------------------------------------------
You can simply reproduce it with the following code and a tool like "Active
Ports" to investigate open TCP-connections:
download link for "Active Port"-Tool ->
http://download.cnet.com/%7Bvalue=http://www.download.com/active-ports/3000-2651_4-29653.html
import org.apache.mina.transport.socket.nio.NioSocketConnector;
public class TestPorts {
public static void main(String[] args) throws Exception {
new NioSocketConnector();
Thread.sleep(9999999);
}
}
> 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
>
> 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
