Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 67745 invoked by uid 500); 13 Mar 2002 15:21:04 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 67730 invoked from network); 13 Mar 2002 15:21:03 -0000 Date: Wed, 13 Mar 2002 16:21:03 +0100 (CET) From: Torsten Curdt X-X-Sender: To: Subject: RE: strange exception - store? In-Reply-To: <00e901c1caa1$67347100$0a00a8c0@vgritsenkopc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 13 Mar 2002, Vadim Gritsenko wrote: > > From: Torsten Curdt [mailto:tcurdt@dff.st] > > > > Can some of you please spend some cents on this one... > > Where to send these? :) over here :) > > ...I get this on some request but fail to see a pattern. > > This happens in HEAD from a few days ago but have seen it with > > an earlier version, too. > > > > Is this store related? (we are still using > > org.apache.cocoon.components.store.FilesystemStore) > > I took a look at the store... It looks *very* innocent. There no place > to pass null to the logger in the store implementation. I've just switch to the JispStore and will keep an eye on this... > > I have no clue yet... > > IIRC, similar exception was reported on the user list, but I'm not > sure... I've had a look into logkit... looks like the LogTargets are null But I wonder how this could happen.... I hate it if I cannot track things down... anyway Thanks, Vadim We need to watch this... -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org