Just a wild guess, but are all of the object you're storing Serializable? I think that some (clustering) containers require that...
On Wednesday 07 June 2006 15:06, Phillip Rhodes wrote: > Sounds like your container is not able to tie the session to the client. > > Are cookies turned off for clients? > > Have a multi-domain site and the cookies are not going across domains? > > > Maybe synchronization glitches can be the cause? nothing prevents a user > > from firing two concurrent requests that would both modify your session > > objects at the same time. > > > > On 6/7/06, John Menke <[EMAIL PROTECTED]> wrote: > >> Peter it's definitely storing them... This problem is sporadic... we > >> can't > >> reproduce - only we see the errors in the log > >> > >> On 6/5/06, Peter Dawn <[EMAIL PROTECTED]> wrote: > >> > perhaps your variable is not being stored in the first place. i used > >> > to get the same errors and then i realised that my original code was > >> > not storing the variables in the first place. make sure that your code > >> > is storing session variables in the first place. > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > > Thanks, > > > > Henri. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Windows and DOS -- a turtle and it's shell. -------------- Jason Dyer BlueTarp Financial, inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
