On Nov 24, 2010, at 12:41 AM, Mark Thomas wrote:
> On 24/11/2010 01:28, Blair Zajac wrote:
>> On Nov 23, 2010, at 4:49 PM, Blair Zajac wrote:
>>> On Nov 23, 2010, at 2:24 AM, Mark Thomas wrote:
Do let us know what the problem was when you find it.
>>>
>>> Does JNA provide its own clean up m
On 24/11/2010 01:28, Blair Zajac wrote:
> On Nov 23, 2010, at 4:49 PM, Blair Zajac wrote:
>> On Nov 23, 2010, at 2:24 AM, Mark Thomas wrote:
>>> Do let us know what the problem was when you find it.
>>
>> Does JNA provide its own clean up methods that I could run at shutdown? I
>> haven't looked
On Nov 23, 2010, at 4:49 PM, Blair Zajac wrote:
>
> On Nov 23, 2010, at 2:24 AM, Mark Thomas wrote:
>
>> On 23/11/2010 02:19, Blair Zajac wrote:
>>
>>> Any suggestions in tracking this down? Would a custom Tomcat build that
>>> gets each key and value in a try/catch block be useful?
>>
>> Al
On Nov 23, 2010, at 2:24 AM, Mark Thomas wrote:
> On 23/11/2010 02:19, Blair Zajac wrote:
>
>> Any suggestions in tracking this down? Would a custom Tomcat build that
>> gets each key and value in a try/catch block be useful?
>
> Almost certainly. As far as I can tell there is a collections ob
On 23/11/2010 02:19, Blair Zajac wrote:
> Any suggestions in tracking this down? Would a custom Tomcat build that
> gets each key and value in a try/catch block be useful?
Almost certainly. As far as I can tell there is a collections object in
a thread local that is non-null yet returns null for
With Tomcat 6.0.29 and Java 6u22, when I'm stopping Tomcat I'm getting
the attached log, which at the end is a NullPointerException thrown from
AbstractCollection#toString() which is called from clearThreadLocalMap().
java.lang.NullPointerException
at java.util.AbstractCollection.toStri
