-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 1/12/2010 5:19 PM, Robin Wilson wrote:
Your point is well taken about not creating the short-duration
sessions, but alas, Tapestry is the chosen framework - and it uses
the session as a mechanism to pass (more-or-less) global values
The sensible approach would be
1. Refactor DeltaManager and BackupManager to defer the session creation
message until the request is complete
2. Then simply swap out the ReplicationValve with an implementation that
makes sense
Filip
On 01/12/2010 11:42 AM, Robin Wilson wrote:
REPOSTING
This is more-or-less what we've done. It seems to work for our situation.
We've added some variables to the DeltaManager config, so we can control the
behavior as well. We can now set the minimum threshold for a session
duration, where sessions less than this threshold will not get replicated
Earlier this week I posted a question about how to prevent sessions from being
created in our Tapestry pages, and/or how to get Tomcat to get rid of a bunch
of '1-second' sessions we're creating during a load test because the sessions
eventually fill up the heap. (They are being created faster
On 12/01/2010 16:47, Robin Wilson wrote:
Earlier this week I posted a question about how to prevent sessions from being
created in our Tapestry pages, and/or how to get Tomcat to get rid of a bunch
of '1-second' sessions we're creating during a load test because the sessions
eventually fill
REPOSTING this so it won't be on the other thread - sorry about that.
Earlier this week I posted a question about how to prevent sessions from being
created in our Tapestry pages, and/or how to get Tomcat to get rid of a bunch
of '1-second' sessions we're creating during a load test because the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 1/12/2010 1:42 PM, Robin Wilson wrote:
Earlier this week I posted a question about how to prevent sessions
from being created in our Tapestry pages, and/or how to get Tomcat to
get rid of a bunch of '1-second' sessions we're creating
Thanks for your response, here are my answers to your questions...
In our test environment, we have a 2 server cluster, but our front-end Apache
server is only hitting one of them. Regardless of that fact, all sessions
created on either server get replicated to the other. So as they are created
On 12/01/2010 21:05, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 1/12/2010 1:42 PM, Robin Wilson wrote:
Earlier this week I posted a question about how to prevent sessions
from being created in our Tapestry pages, and/or how to get Tomcat to
get rid of a
Did you think about a possibility instead of get rid of the session
overwriting
the manager - getting rid of the data stored in session?
If I understand correctly Tapestry needs the session for the page creation
time ,which means that you don't need all the data stored there after
the page was
10 matches
Mail list logo
