You can reproduce it with the Selenium script. (You would need also this plugin http://51elliot.blogspot.com/2008/02/selenium-ide-goto.html for while loop) Here are my findings regarding this problem: The message "No conversations" is actually means that no conversational wavelets were received from the server for this wave. However, in debugger I could see that two snapshots are sent to the client from ClientFrontendImpl (on the server) - just like for wavelets that are ok. However, in the client side I could see only the user data wavelet, the (root) conversational wavelet somehow disappeared. It is hard to understand where it actually happens due to very complicated logic of how wavelets are created, populated and operationalized.
On Tue, Jan 31, 2012 at 10:46 PM, Ali Lown <a...@lown.me.uk> wrote: > I hard disabled Websockets on my server looking into this issue, and > whilst it hasn't stopped it, it has certainly reduced its frequency. > -> This fits in with the idea of it being related to a communications > issue. > > When it occurs though, the only solution is a server restart. > > As for reproducing it on a dev machine: I haven't yet managed either > -> since some users reported it to me. > > On 31 January 2012 20:42, Yuri Z <vega...@gmail.com> wrote: > > Maybe you can take a look at issue > > https://issues.apache.org/jira/browse/WAVE-305 > > I made several attempts to fix it, but it's a bit elusive. It somehow > > related to recent changes, as it didn't happen before with such > frequency. > > The problem is probably in the connection between client and server, > maybe > > even in the communication level. It doesn't happen with the mobile client > > for example. > > The issue is a nasty one, so worth taking a look. > > > > On Tue, Jan 31, 2012 at 10:29 PM, Davide Carnovale < > > francesco.davide.carnov...@gmail.com> wrote: > > > >> Hi Michael, > >> I'd say start with persistence. > >> > >> D > >> Il giorno 31/gen/2012 21:26, "Michael MacFadden" < > >> michael.macfad...@gmail.com> ha scritto: > >> > >> > All, > >> > > >> > I have some free time to work on some patches. I am somewhat > interested > >> > on working on the server side of things, since I have done work on the > >> > client before. I see a few issues with performance and also with > >> > persistence. Have we captured the main issues that need to be > addressed > >> > anywhere. I know we have had conversations on the mailing list. > >> > > >> > The other task I have considered is putting design information on the > >> > wiki. I will probably do this as I go. > >> > > >> > Any votes on where to start with performance / persistence? > >> > > >> > ~Michael > >> >
