Rainer Jung wrote:
I find it hard to decide between your case (we know the nodes are not
available and we don't need a reminder every minute, instead we want to
see the "real" errors), and the most common case (we didn't see the
single initial message a few days ago and so we didn't realize our n
Hi Jess,
On 11.05.2009 18:43, Jess Holle wrote:
> I have noticed that mod_jk logging about a dead server is overtly
> verbose in some circumstances.
>
> If you use it to load balance over a number of servers and one is dead
> you'll get several lines of error logging every time it retries the
> s
I have noticed that mod_jk logging about a dead server is overtly
verbose in some circumstances.
If you use it to load balance over a number of servers and one is dead
you'll get several lines of error logging every time it retries the
server (to see if it's alive yet). This can get rather ob
https://issues.apache.org/bugzilla/show_bug.cgi?id=47061
--- Comment #5 from Steve Pugh 2009-05-11 02:57:37 PST
---
The patch does indeed move the remove() method. This is because in the original
code, the call to remove() is inside the block of code in save(), which gets
the connection. B
https://issues.apache.org/bugzilla/show_bug.cgi?id=47061
Steve Pugh changed:
What|Removed |Added
Attachment #23521|0 |1
is obsolete|
https://issues.apache.org/bugzilla/show_bug.cgi?id=47061
--- Comment #3 from Steve Pugh 2009-05-11 02:46:00 PST
---
Created an attachment (id=23639)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=23639)
JDBCStore.java patch 1
--
Configure bugmail: https://issues.apache.org/bug
