FYI, Using the org.apache.ojb.broker.cache.ObjectCacheEmptyImpl for caching generates similar exceptions.
Regards, *================================* | Scott T Weaver | | <[EMAIL PROTECTED]> | | Apache Jetspeed Portal Project | | Apache Pluto Portlet Container | *================================* > -----Original Message----- > From: Weaver, Scott [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 02, 2004 10:01 AM > To: 'OJB Users List' > Subject: RE: [OTM] invalidating cache causes NPE on next collection query > > I personally am not using proxies in the portlet registry portion, but I > know David LeStrat is in other parts of jetspeed 2 and he is posting that > is > having issues with them (proxies) not working correctly either. > > If I had the time to get down and dirty with OJB's core, I would, but I > don't. However, if a guiding light were show me were I should look in the > code, I might be convinced otherwise ;) > > Regards, > *================================* > | Scott T Weaver | > | <[EMAIL PROTECTED]> | > | Apache Jetspeed Portal Project | > | Apache Pluto Portlet Container | > *================================* > > > -----Original Message----- > > From: Martin Kal�n [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 02, 2004 9:13 AM > > To: OJB Users List > > Subject: Re: [OTM] invalidating cache causes NPE on next collection > query > > > > Weaver, Scott wrote: > > > > > Actually, this stack trace from sys out might prove more insightful. > > > > > > p.s. I am using a CVS HEAD version from yesterday. > > > > > > java.lang.NullPointerException > > > at > > > org.apache.ojb.broker.accesslayer.CollectionPrefetcher.associateBatch > > > ed(CollectionPrefetcher.java:190) > > > > I'm seeing similar exceptions with latest from CVS HEAD using only > > PersistenceBroker API and not touching the OTM parts. > > > > I have a reproducable testcase where setting proxy="true" fails and > > proxy="false" passes (using dynamic Collection-proxy). I can also avoid > > the problem by calling size() on the Collection-proxy before using > > direct data access. > > > > Something seems to be fishy (again) with collection prefetching in CVS > > head. Unfortunately my testcase involves a huge system and loads of > > data, and I don't have time to strip it down this week. If anyone else > > finds any info on this I'm all ears! > > > > (To me it seems that proxy-prefetching is the culprit.) > > > > Regards, > > Martin > > > > -- > > Martin Kal�n > > Curalia AB Web: http://www.curalia.se > > Orrspelsv�gen 2B Mail: [EMAIL PROTECTED] > > SE-182 79 Stocksund Tel: +46-8-410 064 40 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
