camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From DominicTulley <dominic.tul...@telelogic.com>
Subject Re: Getting lots of TIME_WAIT sockets
Date Tue, 18 Mar 2008 16:44:30 GMT


I have a total of three java processes running in my "test case":

One is a message producer connecting to the broker at
 tcp://localhost:61616?wireFormat.tcpNoDelayEnabled=true
and refering to the queue
IN_QUEUE?cacheLevelName=CACHE_CONSUMER

One is AMQ with camel embedded, and the previously shown routebuilder

One is a message consumer using the same broker url as the producer
and referring to the queue
OUT_QUEUE?cacheLevelName=CACHE_CONSUMER

I've annotated all the queue URIs with cacheLevelName=CACHE_CONSUMER to no
effect.
Both the producer and consumer processes are using activemq connection
factories to connect to the broker.
The producer and consumer classes are running as plain java Main methods -
no spring or anything like that involved.
An experiment with the producer and consumer on separate machines showed
that all the TIME_WAIT sockets are internal connections within AMQ (ie from
localhost and to localhost) - not to either the producer or consumer
processes.

-Dominic



-- 
View this message in context: http://www.nabble.com/Getting-lots-of-TIME_WAIT-sockets-tp16119896s22882p16125352.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Mime
View raw message