incubator-wave-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zachary “Gamer_Z.” Yaro (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (WAVE-305) Cannot open a new wave just after creation - No conversations in this wave.
Date Wed, 28 Mar 2012 13:42:28 GMT

    [ https://issues.apache.org/jira/browse/WAVE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240405#comment-13240405
] 

Zachary “Gamer_Z.” Yaro commented on WAVE-305:
----------------------------------------------

Has waveinabox.net been updated since the fix?  I got the “No conversations in this wave.”
error on a wave I just created.
                
> Cannot open a new wave just after creation - No conversations in this wave.
> ---------------------------------------------------------------------------
>
>                 Key: WAVE-305
>                 URL: https://issues.apache.org/jira/browse/WAVE-305
>             Project: Wave
>          Issue Type: Bug
>          Components: Web Client
>            Reporter: Yuri Zelikov
>            Assignee: Yuri Zelikov
>            Priority: Critical
>
> Steps to reproduce:
> Cannot be reproduced reliably. Doesn't happen in my local dev environment. Happens in
waveinabox.net, usually when the server is under load.
> 1. Create a new wave. Enter some text.
> 2. Click on the wave digest in order to reload the wave.
> Expected: The wave is reloaded and displayed with all content.
> Actual: Empty panel displayed with message:  "No conversations in this wave"
> This is the log that i think is related to the issue:
> 2011-11-25 09:48:28.775:DBUG:oejs.AsyncHttpConnection:async request (null null)@2782586
org.eclipse.jetty.server.Request@2a757a
> Nov 25, 2011 9:48:28 AM org.waveprotocol.box.server.frontend.WaveViewSubscription submitRequest
> INFO: Submit oustandinding on channel ch9
> Nov 25, 2011 9:48:28 AM org.waveprotocol.box.server.waveserver.WaveServerImpl submitDelta
> INFO: Submit to [WaveletName waveinabox.net/w+lAjXzMOY0eA/waveinabox.net/user+julianhanhart@waveinabox.net]
by julianhanhart@waveinabox.net @ 0 with 1 ops
> Nov 25, 2011 9:48:28 AM org.waveprotocol.box.server.waveserver.LocalWaveletContainerImpl
transformAndApplyLocalDelta
> INFO: Duplicate delta TransformedWaveletDelta(julianhanhart@waveinabox.net, 1:jDFIgvDgRupnm6BkVyXhy88rza8=,
1322214480147 -> 1 ops: [add participant julianhanhart@waveinabox.net by julianhanhart@waveinabox.net
at Fri Nov 25 09:48:00 UTC 2011 version 1:jDFIgvDgRupnm6BkVyXhy88rza8=]) for wavelet [WaveletName
waveinabox.net/w+lAjXzMOY0eA/waveinabox.net/user+julianhanhart@waveinabox.net]
> Nov 25, 2011 9:48:28 AM org.waveprotocol.box.server.waveserver.WaveServerImpl submitDelta
> INFO: Submit result for [WaveletName waveinabox.net/w+lAjXzMOY0eA/waveinabox.net/user+julianhanhart@waveinabox.net]
by julianhanhart@waveinabox.net applied 1 ops at v: 0 t: 1322214480147
> Nov 25, 2011 9:48:28 AM org.waveprotocol.box.server.frontend.WaveViewSubscription submitResponse
> INFO: Submit resolved on channel ch9
> Seems like the first delta that adds the participant to the new (empty) wavelet is somehow
duplicated and then on loading the participant is not recognized as author and doesn't have
the access to this wavelet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message