Hi Tim, do you have a reproducable test scenario you can provide? Which means, a simple pipeline provoking the exception.
Carsten Carsten Ziegeler Open Source Group, S&N AG > -----Original Message----- > From: Timothy Larson [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 31, 2003 3:00 PM > To: [EMAIL PROTECTED] > Subject: Re: [BUG] : java.util.EmptyStackException on EnvironmentStack > > > I have this problem as well. Has anyone found an approved fix for this? > Once I get the EmptyStackException, Cocoon is dead in the water. > It has to be restarted to get it working again. > > Tim > > >>>> [EMAIL PROTECTED] 12/31/02 07:56AM >>> > >Hi, > > > >I'm using cocoon 2.0.4, and after calling a request that causes > >an exception, sometimes I get an EmptyStackException from the > >environment stack. > > > >I traced this behavior, and found out that, the environment > >stack is sometimes not initialized, when the request is > >just starting to process, meaning, on the first call to > >CocoonComponentManager#enterEnvironment, environmentStack.get() > >returns an empty EnvironmentStack with offset = 1. > > > >I think resetting the thread's EnvironmentStack on entry > >(CocoonServlet#service) will solve this, but I'm not sure if > >that is the right solution. (I'm not fluent with the behavior > >of this part of the system) > > > >Please help me solve this. > > > > > >Thanks, > > > >Amir Rosen > >CTI Squared > >[EMAIL PROTECTED] > >+972-9-9605200 (258) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
