On 04/07/2011 01:38 AM, David Zych wrote:
Hello David,
it's about the time I get back to this :)
> The problem is that even with SQLRetries 1 and (let's say) Timeout 3,
> *subsequent* SQL-bound requests will still stall Radiator for 3 seconds
> each, so instead of being able to process many requ
On 4/6/2011 4:26 PM, Heikki Vatiainen wrote:
> On 04/06/2011 10:22 PM, David Zych wrote:
>> I just ran into this same problem; my DB got into a state where
>> DBI->connect was working fine but actual INSERTs were timing out, and
>> the non-observance of FailureBackoffTime in this situation resulted
On 04/06/2011 10:22 PM, David Zych wrote:
David,
thanks for the suggestion and comments. Please see my comments below:
> I just ran into this same problem; my DB got into a state where
> DBI->connect was working fine but actual INSERTs were timing out, and
> the non-observance of FailureBackoffT
On 9/20/2010 12:00 PM, Michael wrote:
>> > I'm having a couple issues with. Maybe it would be
>> > considered a bug i'm not sure.
>> >
>> > 1. the Timeout handling.
>> >
>> >
>>> >> From my testing, it a
ok, thanks. Can I suggest an option to disable this behavior? In my
case, I would prefer radiator to only allow one timeout, when a timeout
occurs, respect the FailureBackoffTime. If it doesn't, radiator creates
a very undesirable situation when it continues to try for every packet,
the sql se
Hello Michael -
The behaviour you observe is in fact what the code does - the manual does not
correctly describe this behaviour.
The manual has been amended for the next release.
Thanks for letting us know.
regards
Hugh
On 16 Sep 2010, at 15:31, Hugh Irvine wrote:
>
> Hello Michael -
>
Hello Michael -
We'll investigate this a bit further.
BTW - some people put a unique index on the accounting table using something
like Acct-Session-Id + Timestamp to avoid duplicates.
Otherwise you can use a stored procedure in the database to do whatever you
need (or not).
regards
Hugh
Debian 4.0
Perl, v5.8.8 built for x86_64-linux-gnu-thread-multi
DBI v1.53
mysqld Ver 5.0.32-Debian_7etch12-log for pc-linux-gnu on x86_64 (Debian
etch distribution)
since my radiator config is quite lengthy, i'll just post what i think
is the relevant parts. if you would like to know more, let
Hello Michael -
We'll need to see a copy of the configuration file (no secrets), together with
a more complete trace 4 debug showing what is happening.
We will also need to know what hardware/software platform you are running on,
what version of Perl, what version of DBI/DBD, what SQL database
Hi,
I'm having a couple issues with . Maybe it would be
considered a bug i'm not sure.
1. the Timeout handling.
From my testing, it appears that radiator times out at this value, but
seems to retry the sql query a second time, creating in another timeout
count.
eg
10 matches
Mail list logo
