I'm seeing on occasions where a request is aborted if a user navigates too quickly within an application that is taking place within a long running conversation.
What happens is the view from which the request was made and conversation was aborted is reloaded but is outside the conversation since the conversation id has been lost. In this particular case a conversation is started or joined but the conversation is now gone so even though it should have been joined a new one is started causing all kinds of problems.
Looking at the debug.seam page it is clear there are now two conversations. One being on the original view and the other being on the view being navigated to.
I would think this is something that has been encountered before and was wondering if there are any recommended solutions?
