We are getting null values so the values are being lost it's not sync
problem.
On 6/7/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
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 t
Hi John.
Does this still happen with caching *enabled*?
Cheers,
Nick.
John Menke wrote:
Peter it's definitely storing them... This problem is sporadic... we can't
reproduce - only we see the errors in the log
-
To unsubscrib
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 cli
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 th
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 ca
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 origi
We are using Tapestry 4
On 6/6/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
Yes we have been experienced those... Are you using tapestry 3 or tapestry
4? Which servlet engine?
Since we switched to tapestry 4, we have seen way less of these...
And I'm 99% positive this has not anything to do with
Yes we have been experienced those... Are you using tapestry 3 or tapestry
4? Which servlet engine?
Since we switched to tapestry 4, we have seen way less of these...
And I'm 99% positive this has not anything to do with the code.
On 6/5/06, John Menke <[EMAIL PROTECTED]> wrote:
Is anyone expe
I've seen something like this once before involving an app designed for a
small number of large sessions. My problem was that I was persisting my
sessions in-memory. When there was no more memory available, my app server
(weblogic 8.1) conveniently started discarding sessions. Turning on JDBC
se
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.
---
10 matches
Mail list logo
