I know this has been a while, but was this ever resolved? We're seeing the
same problem. And, because of this problem, Wicket is never cleaning up old
session pagemap files which leads to oodles of files in our tomcat work
directory.
Thanks,
Meetesh
On Sat, Nov 22, 2008 at 5:55 AM, Carlos Pita
Unfortunately I wasn't able to reproduce this so I don't think this
got resolved.
-Matej
On Thu, Mar 5, 2009 at 8:47 PM, Meetesh Karia meetesh.ka...@gmail.com wrote:
I know this has been a while, but was this ever resolved? We're seeing the
same problem. And, because of this problem, Wicket
I'm not sure I can provide any additional information as we just started
looking into it (though we've been seeing it for a while). For the time
being, I'm just going to set up a cron job to remove old pagemap files.
Perhaps we could make the restore block allow a null lastPage? Btw - what
Matej,
forget what I said yesterday about session lastAccessedDate, I've
debugged it in detail and tomcat is doing its part fine, I was
confused by a sequence of logs that implied that the session was
swapped out before a page was added to its pagemap. But later I found
out that this wasn't the
Hi all,
as I've a requirement to maintain long lived sessions (~120s) I'm
using tomcat's PersistentManager to avoid keeping lots of sessions in
memory, each one with its own lastPage. I'm observing, specially in a
heavy loaded production environment, permanent errors with a trace
like
Nov 19,
Another fact that could be relevant is that this only happens upon
processexpires, but never for swapin, which seems to suggest that the
span of the sessions that fail to restore is just one request (maybe
the ones coming from bots that don't support cookies).
Best regards
-Carlos
On Wed, Nov
The last one of the saga for now, I badly need to sleep.
I've been sampling tomcat work dir every second:
i=0; while [[ i -le 300 ]]; do echo $i; ls -lt /u01/tomcatWork/_
/tmp/work$i; sleep 1; i=$((i + 1)); done
Then I greped a number of session ids corresponding to
restoreAfterSerialization
This really is weird. I added couple of warnings and null check to 1.4
trunk. I wonder if that helps it though.
-Matej
On Wed, Nov 19, 2008 at 12:44 PM, Carlos Pita [EMAIL PROTECTED] wrote:
The last one of the saga for now, I badly need to sleep.
I've been sampling tomcat work dir every
Hi Matej,
I'm browsing your changes. Please notice that according to my own
debugging it's lastPage itself that is null and not only the result of
prepareForSerialization. So I don't think the warning PageStore
prepared non-null page as null for serialization will ever be
reached. Anyway, I will
