Sorry for the noise - I just end up following my nose trying to find a way
round the problem.
The easiest way to reproduce the problem is simply to pump a bunch of
messages through a standard camel route defined in activemq.xml. I see the
problem with the standard distro of amq and camel (As built from svn) by
just adding a single route (with activemq: as the component) and exercising
it.
-Dominic
James.Strachan wrote:
>
> I'm getting a bit confused by all these permuations :)
>
> Whats the easiest way to reproduce the problem you're seeing. Just
> take the default activemq.xml and sending a ton of messages to one of
> the camel routes in the activemq.xml?
>
>
> On 20/03/2008, DominicTulley <[EMAIL PROTECTED]> wrote:
>>
>> I missed this message yesterday.
>>
>> The primary route builder has this code in it:
>>
>>
>>
>> from("activemq:IN_QUEUE?disableReplyTo=true&cacheLevelName=CACHE_CONSUMER")
>> .setHeader(RoutingStatics.HEADER_HASHANDLER,
>> hasHandlerExpression)
>> .setHeader(RoutingStatics.HEADER_ISDOCBASED,
>> isDocBasedExpression)
>>
>> .to("activemq:OUT_QUEUE?disableReplyTo=true&cacheLevelName=CACHE_CONSUMER");
>>
>>
>> However, if I get rid of all my camel configuration and instead just use
>> a
>> simple route like that below, it still has the problem.
>>
>> <route>
>> <from uri="activemq:TOOL.DEFAULT"/>
>> <to uri="activemq:TOOL.DEFAULT.ROUTED"/>
>> </route>
>>
>> -Dominic
>>
>>
>> James.Strachan wrote:
>> >
>> > On 18/03/2008, DominicTulley <[EMAIL PROTECTED]> wrote:
>> >>
>> >> If I run with the AMQ broker on one machine and the
>> producer&consumer on
>> >> a
>> >> second machine then all the TIME_WAIT sockets are on the AMQ machine
>> >> (from
>> >> localhost, to localhost). So, I'm pretty convinced the cause is
>> there.
>> >> Also, if I remove all camel logic and just produce and consume on
>> the
>> >> same
>> >> queue, there are no TIME_WAIT sockets (or very few).
>> >>
>> >> The number of sockets is certainly increasing - I'm pushing through
>> >> around
>> >> 100 msg/s and seeing around 100 TIME_WAIT sockets appearing per
>> second.
>> >> Interestingly the number continues to rise for "a while" after I
>> kill
>> >> the
>> >> producer - my assumption is that it is because camel hasn't got
>> through
>> >> them
>> >> all yet. The number of TIME_WAIT sockets stops rising a few seconds
>> >> after I
>> >> kill off the producer.
>> >>
>> >> Here's my http://www.nabble.com/file/p16131500/activemq.xml
>> >> activemq.xml .
>> >> My camel config is all right at the end.
>> >> Other than that, the only bit I've deliberately changed is to trim
>> down
>> >> the
>> >> network connectors section.
>> >
>> > What does the Java code look like for the
>> org.dominic.PrimaryRouteBuilder?
>> >
>> >
>> > --
>> > James
>> > -------
>> > http://macstrac.blogspot.com/
>> >
>> > Open Source Integration
>> > http://open.iona.com
>> >
>> >
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Getting-lots-of-TIME_WAIT-sockets-tp16119896s22882p16176219.html
>>
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
>
--
View this message in context:
http://www.nabble.com/Getting-lots-of-TIME_WAIT-sockets-tp16119896s22882p16177002.html
Sent from the Camel - Users mailing list archive at Nabble.com.
