I'm working on this bug; there will be a 5.0.18 release for this bug (and the deadlock bug which may have resurfaced).
https://issues.apache.org/jira/browse/TAP5-399 On Wed, Dec 3, 2008 at 5:07 AM, Cliff Willsher <[EMAIL PROTECTED]> wrote: > > Hi, > > We are trying to cluster several instances of our Tapestry application using > Tapestry 5.0.17 and Tomcat 5.5. > > When running the application I can see the ASOs being added to the session > when they are created and replicated across the other Tomcat instances, > however when the existing ASOs are modified the changes are not replicated. > > After some digging I placed a breakpoint in > SessionApplicationStatePersistenceStrategy.requestDidComplete() method where > I assumed that the ASOs would be set back in the session at the end of the > request and found that it was never called. > > As this method is part of the EndOfRequestListener interface, I added a > breakpoint in EndOfRequestListenerHubImpl.fire() method and found that was > being called but the "listeners" list was always empty. > > To test if writing back to the session was the issue I added my own > RequestFilter to the RequestHandler service to get all ASOs from the session > and set them back again, this fixed the clustering problem but isn't ideal. > > Is this a bug or do I need to do something else to get ASOs written back to > the session at the end of a request? > > Is there a way I can add/contribute > SessionApplicationStatePersistenceStrategy to the list of listeners in > EndOfRequestListenerHubImpl from my application's service module? > > Thanks > > Cliff > > > > -- > View this message in context: > http://www.nabble.com/ASOs-and-Clustering-tp20812617p20812617.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
