On Jun 11, 12:15 am, thengil staffan.martins...@gmail.com wrote:
Hi,
we have a problem in our production environment where we are getting
abnormal amounts of timeouts as outlined below:
net.spy.memcached.OperationTimeoutException: Timeout waiting for value
You'll get this error whenever
Yes, the timeout is 1000ms since we haven't touched that value. We
will set up wireshark to look at possible network problems... Could it
somehow be related to garbage collection on the appserver? The
timeouts seem to occur in clumps - nothing goes wrong for a minute or
so, then we get 3-8
On Jun 11, 1:05 am, thengil staffan.martins...@gmail.com wrote:
Yes, the timeout is 1000ms since we haven't touched that value. We
will set up wireshark to look at possible network problems... Could it
somehow be related to garbage collection on the appserver?
Oh yes, a GC pause could
I've turned on GC logging and unfortunately it seems that the problem
is not ONLY due to full GCs. We've observed a full GC that took 1.2
seconds and that led to timeouts, but we've also observed timeouts
that occurred when no full GC was ongoing. We will try to se what we
can find via tcpdump
This might be an obvious question, but have you verified that
memcached is not going in to swap?
thengil wrote:
I've turned on GC logging and unfortunately it seems that the problem
is not ONLY due to full GCs. We've observed a full GC that took 1.2
seconds and that led to timeouts, but we've
