You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@verizon.net> on 2002/03/20 06:31:10 UTC
[future-showstopper] Sitemap reload & dispose() & NPEs
Hi,
I was playing with our almost-released Cocoon, and found quite serious
bug in component management, in the Excalibur. At least, after replacing
the excalibur with the older version, bug goes away.
Symptoms:
- Disposed XSLT transformer by component manager as part of sitemap
handler disposal in the sitemap Manager regenerate, AND TraxTransformer
with the instance of this XSLT transformer without any knowledge of
what's going on (net result: NPE);
- NPE in ContentAgregator were it never was observed before while
browsing documentation;
- Main sitemap is regenerated without reason (!) when there is first
access to the sub sitemap, and both sitemaps were already compiled;
... and other weird things.
After some investigation I decided just to fallback to well-tested and
known-to-be-working Excalibur version. All weird things went away. I'm
happy, puzzled, tired.
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Berin Loritsch [mailto:bloritsch@apache.org]
>
> I am copying this to the avalon list.
>
> I wonder if the issues you are experiencing have to do with
> JDK changes.... i.e. if it was compiled on one JVM and
> run on another....
No, jdk 1.3.1 only.
I'm trying not to mix them :)
Vadim
> > -----Original Message-----
> > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> > Sent: Wednesday, March 20, 2002 12:31 AM
> > To: cocoon-dev@xml.apache.org
> > Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
> >
> >
> > Hi,
> >
> > I was playing with our almost-released Cocoon, and found
> > quite serious bug in component management, in the Excalibur.
> > At least, after replacing the excalibur with the older
> > version, bug goes away.
> >
> > Symptoms:
> > - Disposed XSLT transformer by component manager as part of
> > sitemap handler disposal in the sitemap Manager regenerate,
> > AND TraxTransformer with the instance of this XSLT
> > transformer without any knowledge of what's going on (net
> > result: NPE);
> > - NPE in ContentAgregator were it never was observed before
> > while browsing documentation;
> > - Main sitemap is regenerated without reason (!) when there
> > is first access to the sub sitemap, and both sitemaps were
> > already compiled; ... and other weird things.
> >
> > After some investigation I decided just to fallback to
> > well-tested and known-to-be-working Excalibur version. All
> > weird things went away. I'm happy, puzzled, tired.
> >
> >
> > Vadim
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Berin Loritsch <bl...@apache.org>.
I am copying this to the avalon list.
I wonder if the issues you are experiencing have to do with
JDK changes.... i.e. if it was compiled on one JVM and
run on another....
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, March 20, 2002 12:31 AM
> To: cocoon-dev@xml.apache.org
> Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
>
>
> Hi,
>
> I was playing with our almost-released Cocoon, and found
> quite serious bug in component management, in the Excalibur.
> At least, after replacing the excalibur with the older
> version, bug goes away.
>
> Symptoms:
> - Disposed XSLT transformer by component manager as part of
> sitemap handler disposal in the sitemap Manager regenerate,
> AND TraxTransformer with the instance of this XSLT
> transformer without any knowledge of what's going on (net
> result: NPE);
> - NPE in ContentAgregator were it never was observed before
> while browsing documentation;
> - Main sitemap is regenerated without reason (!) when there
> is first access to the sub sitemap, and both sitemaps were
> already compiled; ... and other weird things.
>
> After some investigation I decided just to fallback to
> well-tested and known-to-be-working Excalibur version. All
> weird things went away. I'm happy, puzzled, tired.
>
>
> Vadim
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Berin Loritsch [mailto:bloritsch@apache.org]
>
> This could be something introduced by the code that Leif added
> to order the disposal of components.
>
> Still, this does not come into affect until the items are actually
> disposed.
>
> Could you send an offending log? It might help to determine what
> is going on.
Ok. Now that you have asked - I fail to reproduce it :*|
I think complete rebuild killed this unique combination of libs/classes.
Sorry for the noise.
I guess that was old BucketMap class (with the bug) with the modified
(new) component manager.
> Question:
>
> Does it happen when you use the TreeProcessor?
Don't know. I used the default (compiled) sitemap.
Vadim
> > -----Original Message-----
> > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> > Sent: Wednesday, March 20, 2002 7:31 AM
> > To: cocoon-dev@xml.apache.org
> > Subject: RE: [future-showstopper] Sitemap reload & dispose() & NPEs
> >
> >
> > > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> > >
> > > Has this something to do with this bug?
> > >
> > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6362
> >
> > No.
> >
> > > If so, the old avalon jars have the same problem
> >
> > Problem has gone away with older Excalibur. It was perfectly
> > 100% reproducible.
> >
> > Vadim
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Berin Loritsch <bl...@apache.org>.
This could be something introduced by the code that Leif added
to order the disposal of components.
Still, this does not come into affect until the items are actually
disposed.
Could you send an offending log? It might help to determine what
is going on.
Question:
Does it happen when you use the TreeProcessor?
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, March 20, 2002 7:31 AM
> To: cocoon-dev@xml.apache.org
> Subject: RE: [future-showstopper] Sitemap reload & dispose() & NPEs
>
>
> > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> >
> > Has this something to do with this bug?
> >
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6362
>
> No.
>
> > If so, the old avalon jars have the same problem
>
> Problem has gone away with older Excalibur. It was perfectly
> 100% reproducible.
>
> Vadim
>
> >
> > Carsten
> >
> > > -----Original Message-----
> > > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> > > Sent: Wednesday, March 20, 2002 6:31 AM
> > > To: cocoon-dev@xml.apache.org
> > > Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
> > >
> > >
> > > Hi,
> > >
> > > I was playing with our almost-released Cocoon, and found quite
> serious
> > > bug in component management, in the Excalibur. At least, after
> replacing
> > > the excalibur with the older version, bug goes away.
> > >
> > > Symptoms:
> > > - Disposed XSLT transformer by component manager as part
> of sitemap
> > > handler disposal in the sitemap Manager regenerate, AND
> TraxTransformer
> > > with the instance of this XSLT transformer without any
> knowledge of
> > > what's going on (net result: NPE);
> > > - NPE in ContentAgregator were it never was observed
> before while
> > > browsing documentation;
> > > - Main sitemap is regenerated without reason (!) when there is
> first
> > > access to the sub sitemap, and both sitemaps were already
> compiled;
> > > ... and other weird things.
> > >
> > > After some investigation I decided just to fallback to well-tested
> and
> > > known-to-be-working Excalibur version. All weird things went away.
> I'm
> > > happy, puzzled, tired.
> > >
> > >
> > > Vadim
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Berin Loritsch <bl...@apache.org>.
This could be something introduced by the code that Leif added
to order the disposal of components.
Still, this does not come into affect until the items are actually
disposed.
Could you send an offending log? It might help to determine what
is going on.
Question:
Does it happen when you use the TreeProcessor?
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, March 20, 2002 7:31 AM
> To: cocoon-dev@xml.apache.org
> Subject: RE: [future-showstopper] Sitemap reload & dispose() & NPEs
>
>
> > From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> >
> > Has this something to do with this bug?
> >
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6362
>
> No.
>
> > If so, the old avalon jars have the same problem
>
> Problem has gone away with older Excalibur. It was perfectly
> 100% reproducible.
>
> Vadim
>
> >
> > Carsten
> >
> > > -----Original Message-----
> > > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> > > Sent: Wednesday, March 20, 2002 6:31 AM
> > > To: cocoon-dev@xml.apache.org
> > > Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
> > >
> > >
> > > Hi,
> > >
> > > I was playing with our almost-released Cocoon, and found quite
> serious
> > > bug in component management, in the Excalibur. At least, after
> replacing
> > > the excalibur with the older version, bug goes away.
> > >
> > > Symptoms:
> > > - Disposed XSLT transformer by component manager as part
> of sitemap
> > > handler disposal in the sitemap Manager regenerate, AND
> TraxTransformer
> > > with the instance of this XSLT transformer without any
> knowledge of
> > > what's going on (net result: NPE);
> > > - NPE in ContentAgregator were it never was observed
> before while
> > > browsing documentation;
> > > - Main sitemap is regenerated without reason (!) when there is
> first
> > > access to the sub sitemap, and both sitemaps were already
> compiled;
> > > ... and other weird things.
> > >
> > > After some investigation I decided just to fallback to well-tested
> and
> > > known-to-be-working Excalibur version. All weird things went away.
> I'm
> > > happy, puzzled, tired.
> > >
> > >
> > > Vadim
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>
> Has this something to do with this bug?
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6362
No.
> If so, the old avalon jars have the same problem
Problem has gone away with older Excalibur. It was perfectly 100%
reproducible.
Vadim
>
> Carsten
>
> > -----Original Message-----
> > From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> > Sent: Wednesday, March 20, 2002 6:31 AM
> > To: cocoon-dev@xml.apache.org
> > Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
> >
> >
> > Hi,
> >
> > I was playing with our almost-released Cocoon, and found quite
serious
> > bug in component management, in the Excalibur. At least, after
replacing
> > the excalibur with the older version, bug goes away.
> >
> > Symptoms:
> > - Disposed XSLT transformer by component manager as part of sitemap
> > handler disposal in the sitemap Manager regenerate, AND
TraxTransformer
> > with the instance of this XSLT transformer without any knowledge of
> > what's going on (net result: NPE);
> > - NPE in ContentAgregator were it never was observed before while
> > browsing documentation;
> > - Main sitemap is regenerated without reason (!) when there is
first
> > access to the sub sitemap, and both sitemaps were already compiled;
> > ... and other weird things.
> >
> > After some investigation I decided just to fallback to well-tested
and
> > known-to-be-working Excalibur version. All weird things went away.
I'm
> > happy, puzzled, tired.
> >
> >
> > Vadim
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Has this something to do with this bug?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6362
If so, the old avalon jars have the same problem
Carsten
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, March 20, 2002 6:31 AM
> To: cocoon-dev@xml.apache.org
> Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
>
>
> Hi,
>
> I was playing with our almost-released Cocoon, and found quite serious
> bug in component management, in the Excalibur. At least, after replacing
> the excalibur with the older version, bug goes away.
>
> Symptoms:
> - Disposed XSLT transformer by component manager as part of sitemap
> handler disposal in the sitemap Manager regenerate, AND TraxTransformer
> with the instance of this XSLT transformer without any knowledge of
> what's going on (net result: NPE);
> - NPE in ContentAgregator were it never was observed before while
> browsing documentation;
> - Main sitemap is regenerated without reason (!) when there is first
> access to the sub sitemap, and both sitemaps were already compiled;
> ... and other weird things.
>
> After some investigation I decided just to fallback to well-tested and
> known-to-be-working Excalibur version. All weird things went away. I'm
> happy, puzzled, tired.
>
>
> Vadim
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [future-showstopper] Sitemap reload & dispose() & NPEs
Posted by Berin Loritsch <bl...@apache.org>.
I am copying this to the avalon list.
I wonder if the issues you are experiencing have to do with
JDK changes.... i.e. if it was compiled on one JVM and
run on another....
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Wednesday, March 20, 2002 12:31 AM
> To: cocoon-dev@xml.apache.org
> Subject: [future-showstopper] Sitemap reload & dispose() & NPEs
>
>
> Hi,
>
> I was playing with our almost-released Cocoon, and found
> quite serious bug in component management, in the Excalibur.
> At least, after replacing the excalibur with the older
> version, bug goes away.
>
> Symptoms:
> - Disposed XSLT transformer by component manager as part of
> sitemap handler disposal in the sitemap Manager regenerate,
> AND TraxTransformer with the instance of this XSLT
> transformer without any knowledge of what's going on (net
> result: NPE);
> - NPE in ContentAgregator were it never was observed before
> while browsing documentation;
> - Main sitemap is regenerated without reason (!) when there
> is first access to the sub sitemap, and both sitemaps were
> already compiled; ... and other weird things.
>
> After some investigation I decided just to fallback to
> well-tested and known-to-be-working Excalibur version. All
> weird things went away. I'm happy, puzzled, tired.
>
>
> Vadim
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>