Massive increase of TCP/IP connections when opening JMS conn

[christof_kal]

Hi,

I have an interesting problem with UIL2 in JBoss 4.0.2 (Windows). When I open a JMS-connection using UIL2 and close it immediately afterwards and repeat this over and over again, the amount of open TCP/IP connections increases massively (although I close the connections). This problem is relevant if you have clients that hold their JMS-connection only for sending/receiving a message and close it immediately afterwards.

When I call netstat -a I get a long long list of open TCP/IP connections.

Is there a way to get around this? E.g. set some kind of timeout parameter? Any help is appreciated.

You can reproduce this problem with following code:

for (int i = 0; i < 10000; i++) {
InitialContext initCtx = new InitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory)initCtx.lookup
("ConnectionFactory");
TopicConnection connection = tcf.createTopicConnection();
Topic topic = (Topic) initCtx.lookup("topic/jmsTestTopic");
TopicSession session = connection.createTopicSession(false,
QueueSession.AUTO_ACKNOWLEDGE);
connection.start();

connection.stop();
session.close();
connection.close();
}

Thanks

Christof

[schrouf]

This is a TCP/IP operation system issue, not a JBoss issue. Google around for "TCP" and "TIME_WAIT" and read some stuff TIME_WAIT socket state und system tuning e.g http://www.octetstring.com/support/issues/Tuning-TIMEWAIT.php

Regards
Ulf

[oglueck]

No, this guy is creating InitialContexts in a loop. Man, creating an InitialContext is a expensive operation! How did you think RMI works? When in a bean, use the lookup methods of the EjbContext. On a client, create an InitialContext once. And don't forget to close it in a finally clause.

[adrian.brock]

:-)

You mean do what is says in the spec?
And don't do what is says not to do in the spec?