On Fri, Jan 28, 2011 at 7:06 PM, PALMER, THOMAS C (ATTCORP) <[email protected]> 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:[email protected]] > Sent: Friday, January 28, 2011 11:17 AM > To: [email protected] > Subject: Re: NPE in ConcurrentCache > > On Fri, Jan 28, 2011 at 5:07 PM, PALMER, THOMAS C (ATTCORP) > <[email protected]> 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: [email protected] >> Subject: RE: NPE in ConcurrentCache >> >> Created https://issues.apache.org/jira/browse/JCR-2871. Thanks - >> >> >> -----Original Message----- >> From: Jukka Zitting [mailto:[email protected]] >> Sent: Friday, January 28, 2011 4:50 AM >> To: [email protected] >> 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) >>> <[email protected]> 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 >> >
