jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Schmidt <cschm...@prospricing.com>
Subject RE: NPE in ConcurrentCache
Date Mon, 31 Jan 2011 20:13:18 GMT
After looking at the Jira issue, I hit a related problem. It was due to IBM's 1.6 SR6 JDK.
We were getting a similar NPE within EHCache that went away after we upgraded to SR8. Based
on the stacktrace I think you are encountering the same issue.

Thanks,

 Chris Schmidt

-----Original Message-----
From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com] 
Sent: Monday, January 31, 2011 6:55 AM
To: users@jackrabbit.apache.org
Subject: Re: NPE in ConcurrentCache

On Mon, Jan 31, 2011 at 1:42 PM, PALMER, THOMAS C (ATTCORP)
<TP3310@att.com> wrote:
> Stefan -
> Don't see an attachment here ... or on JCR-2871.  Did you forget to attach?  Thanks
-

sorry, my bad. it has been stripped by the mailing list apparently.
i've added it to JCR-2871 now.
i didn't want to do that initially because it's not meant to 'fix' the
problem, but anyway...

cheers
stefan

>
> -----Original Message-----
> From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com]
> Sent: Monday, January 31, 2011 3:33 AM
> To: users@jackrabbit.apache.org
> Subject: Re: NPE in ConcurrentCache
>
> On Fri, Jan 28, 2011 at 7:06 PM, PALMER, THOMAS C (ATTCORP)
> <TP3310@att.com> wrote:
>> Thanks - but neither suggestion made a difference.  Always the same NPE at ConcurrentCache.java:47.
 Other suggestions welcomed ;)
>
> try the attached patch. it's not a fix, it just guards against the NPE.
> if it works, at least we know where the problem is.
>
> cheers
> stefan
>
>>
>>
>> -----Original Message-----
>> From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com]
>> Sent: Friday, January 28, 2011 11:17 AM
>> To: users@jackrabbit.apache.org
>> Subject: Re: NPE in ConcurrentCache
>>
>> On Fri, Jan 28, 2011 at 5:07 PM, PALMER, THOMAS C (ATTCORP)
>> <TP3310@att.com> wrote:
>>> Stefan -
>>> I see your initial assessment in Jira that this could be specific to the
>>> JVM.  At this point, we're just trying to load some initial nodes at
>>> repo create time.  Is there any change to our configuration that would
>>> let us temporarily work around this problem?  Thanks -
>>
>> not sure if it helps, but you could try to:
>>
>> - increase the jvm heap size
>> - use Workspace.importXML instead of Session.importXML
>>
>> cheers
>> stefan
>>
>>>
>>>
>>> -----Original Message-----
>>> From: PALMER, THOMAS C (ATTCORP)
>>> Sent: Friday, January 28, 2011 5:56 AM
>>> To: users@jackrabbit.apache.org
>>> Subject: RE: NPE in ConcurrentCache
>>>
>>> Created https://issues.apache.org/jira/browse/JCR-2871.  Thanks -
>>>
>>>
>>> -----Original Message-----
>>> From: Jukka Zitting [mailto:jzitting@adobe.com]
>>> Sent: Friday, January 28, 2011 4:50 AM
>>> To: users@jackrabbit.apache.org
>>> Subject: Re: NPE in ConcurrentCache
>>>
>>> Hi,
>>>
>>> On 28.01.2011 10:02, Stefan Guggisberg wrote:
>>>> On Thu, Jan 27, 2011 at 8:38 PM, PALMER, THOMAS C (ATTCORP)
>>>> <TP3310@att.com> wrote:
>>>>> I've created a simple project plus test node XML that can dup this.
>>>>> Where can I send it?  Thanks -
>>>>
>>>> please send it to my personal email address.
>>>
>>> Or better yet, file a bug in our issue tracker [1] and attach the test
>>> case.
>>>
>>> [1] https://issues.apache.org/jira/browse/JCR
>>>
>>> --
>>> Jukka Zitting
>>>
>>
>

Mime
View raw message