Re: non-trivial finalize() on AbstractJdbc2Statement

Yes, that's how I got my thread dump. But the that doesn't give me the
priority. This is not the openJDK, so that's probably the difference that's
making you see a priority and me not seeing one (I've seen discussions
around not being able to get thread priority from ThreadInfo in a plugin
for jonsole that shows the topthreads).

My heap dumps are over 7GB and they crash jvisualvm if I try to open them.
I've used YourKit to inspect these dumps and that's how I've looked the
Finalizer objecets where I saw the jdbc3Statement being referenced.

Cheers
-- Imran

2012/2/15 Віталій Тимчишин <tivv00(at)gmail(dot)com>

>
>
> 2012/2/15 Imran <imranbohoran(at)gmail(dot)com>
>
>> So I've tried to run jstack over five times and it kept in saying it
>> can't walk over the threads. We have a fair amount of background processes
>> running, not sure if that made jstack fail. I've read that its possible to
>> hit the error on jstack. My thread dumps from jvisualvm doesn't show the
>> priority of any threads.
>>
> I have visualvm 1.3. I can select application in the list -> popup menu
> with RMB -> thread dump. Another option is to click Thread Dump button in
> Threads tab of application open. This should open new tab with textual
> thread dump, pretty similar to jstack one.
>
>> Also the only thing the tread dumps have shown to me is that its waiting
>> on RefernceQueue.remove, which holds the Finalizer objects that gets
>> created due to finalize methods.
>>
> This means that ReferenceQueue is empty. If you wish to dig deeper you
> need to check same thing with unpatched driver.
> Another option is to load OOM heap dump with visual vm, then click "Show
> threads" in the Summary, then check for Finalizer thread. If it could not
> keep up, you should see exact object that caused problems.
> --
> Best regards,
> Vitalii Tymchyshyn
>