Long Reference Processing Time

[Simone Bordet]

Hi,

On Thu, May 21, 2015 at 12:35 AM, Yu Zhang <yu.zhang at oracle.com> wrote:
> can you dump the heap and examine it with eclipse mat or some similar tools?

In our case this was not helpful, but your case may be different.

> On 5/20/2015 3:12 PM, Joy Xiong wrote:
> Also is there a way to get more info on weak references, such as the
> reference name? Our application does not use weak references, so it's likely
> that the weak references come from the underneath library, and I'd like to
> know which library is using lots of weak references.

We ended up with this "dirty" trick:
https://github.com/jetty-project/weakref-allocation

Basically, we modified WeakReference to keep track of allocations and
expose them via JMX.

Turned out that for our case, ThreadLocal and RMI usage were the most
important allocators of WeakReferences.

Hope it helps.

-- 
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz