qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Barto <jason.p.ba...@gmail.com>
Subject Re: Single threaded Client
Date Fri, 03 May 2013 13:07:58 GMT
Lance what language and client library are you using to connect? You'll
need to get a reference to the socket being used by the client library and
modify it's timeout limit.

Sincerely,
Jason
On May 3, 2013 1:15 PM, "Lance D." <lanced@gmail.com> wrote:

> Hello,
>
> I've got a question about Socket timeouts. I've got a program that must be
> single threaded.  I know that's got its own share of problems, but the
> biggest one that I have right now is the case of trying to connect to a
> broker on a host that doesn't exist.
>
> I'll start with my configuration.  I have a client running with the 0.14
> API on a Redhat Linux OS.  My program uses a lookup service to find brokers
> and exchanges that are providing data.  The client connects to each
> exchange, pulls the data and disconnects.  I don't need to do this
> extremely quickly, but it really shouldn't take more than 1-2 seconds per
> connection because they are all on a small network.
>
> My problems begin when the lookup service gives me a broker address for a
> host that is powered off.  When I call open on the connection, the SYN
> packet is sent and I'm stuck waiting for the kernel socket timeout to
> expire before qpid throws that exception.  That means that I'm stalled for
> 20 seconds for each down host.
>
> So, my question to this wonderful group of users is this: what is the best
> way (other than going multi-threaded), to reduce my wait from 20 seconds
> down to 2 seconds?
>
> Thanks all for the help!
> -Lance
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message