Correlation is not causation. The warning is not slowing down your code.
This harmless warning is generated during the static initialization of some
protobuffer code. That static initialization is happening, because your
application is being loaded in a new JVM by a loading
Tony,
thank you for the tips. I'll test them as soon as possible.
I've a question. You said the warning is not slowing down your code.
But it increases the response time of the page. So the user waits for
a longer time before receiving the page. Do you confirm? Have I
correctly understood?
Vince,
ok, it's harmless, but the response is very slow. 5000ms or more
instead of 200ms.
In my case it's a problem.
Any idea/solution?
fabrizio
On Dec 5, 7:07 pm, Vince Bonfanti vbonfa...@gmail.com wrote:
The exception is harmless. Add this to your logging.properties file to hide
it:
Are you sure the slowness is caused by whatever is generating this exception?
fhtino wrote:
Vince,
ok, it's harmless, but the response is very slow. 5000ms or more
instead of 200ms.
In my case it's a problem.
Any idea/solution?
fabrizio
On Dec 5, 7:07 pm, Vince Bonfanti
Yes. I'm quite sure. A couple of examples.
A tipical request with normal execution time and without
FinalizableReferenceQueue
12-10 10:40PM 32.484 /url 200 83ms 160cpu_ms 85api_cpu_ms
A request with FinalizableReferenceQueue:
12-10 10:36PM 22.306 /url 200 4888ms 7280cpu_ms 85api_cpu_ms
