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

Vicente J. Ruiz Jurado commented on WAVE-312:
---------------------------------------------

This annoying bug is still present.

I can reproduce easily using the file store, but I can't with the memory store.

For some reason the delta retrieved in 
DeltaStoreBasedWaveletState.readDeltasInRange
   delta = reader.getDelta(i);
is null.

User [email protected] stay in unsaved state
INFO: Submit to [WaveletName local.net/w+ueh3s7m50sv7A/local.net/conv+root] by 
[email protected] @ 383 with 1 ops
java.lang.NullPointerException
        at 
com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
        at 
com.google.common.collect.ImmutableList$Builder.add(ImmutableList.java:584)
        at 
org.waveprotocol.box.server.waveserver.DeltaStoreBasedWaveletState.readDeltasInRange(DeltaStoreBasedWaveletState.java:150)
        at 
org.waveprotocol.box.server.waveserver.DeltaStoreBasedWaveletState.getTransformedDeltaHistory(DeltaStoreBasedWaveletState.java:354)
        at 
org.waveprotocol.box.server.waveserver.WaveletContainerImpl.transformSubmittedDelta(WaveletContainerImpl.java:370)
        at 
org.waveprotocol.box.server.waveserver.WaveletContainerImpl.maybeTransformSubmittedDelta(WaveletContainerImpl.java:356)
        at 
org.waveprotocol.box.server.waveserver.LocalWaveletContainerImpl.transformAndApplyLocalDelta(LocalWaveletContainerImpl.java:138)
        at 
org.waveprotocol.box.server.waveserver.LocalWaveletContainerImpl.submitRequest(LocalWaveletContainerImpl.java:96)
        at 
org.waveprotocol.box.server.waveserver.WaveServerImpl.submitDelta(WaveServerImpl.java:542)
        at 
org.waveprotocol.box.server.waveserver.WaveServerImpl.submitRequest(WaveServerImpl.java:344)
        at 
org.waveprotocol.box.server.frontend.ClientFrontendImpl.submitRequest(ClientFrontendImpl.java:194)
        at 
org.waveprotocol.box.server.frontend.WaveClientRpcImpl.submit(WaveClientRpcImpl.java:164)
        at 
org.waveprotocol.box.common.comms.WaveClientRpc$ProtocolWaveClientRpc$1.submit(WaveClientRpc.java:4459)
        at 
org.waveprotocol.box.common.comms.WaveClientRpc$ProtocolWaveClientRpc.callMethod(WaveClientRpc.java:4589)
        at 
org.waveprotocol.box.server.rpc.ServerRpcControllerImpl.run(ServerRpcControllerImpl.java:200)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
30-jul-2012 10:26:52 
org.waveprotocol.box.server.rpc.ServerRpcProvider$Connection$1 run
INFO: error = java.lang.NullPointerException


                
> Not saving editions when concurrent editions in same wave
> ---------------------------------------------------------
>
>                 Key: WAVE-312
>                 URL: https://issues.apache.org/jira/browse/WAVE-312
>             Project: Wave
>          Issue Type: Bug
>          Components: Web Client
>         Environment: Tried in http://waveinabox.net  and http://kune.cc
>            Reporter: Samer
>              Labels: bug, concurrency, edit,, editor,, persistence
>
> - Alice: begins editing a blip of a wave. She needs to write a long paragraph.
> - Bob: begins editing a while after Alice, in another blip in the same wave.
> - Alice doesn't see that Bob is writing, nothing new appears
> - Alice finishes editing her wave and moves to another wave.
> - Bobs finishes editing that wave and moves to another wave.
> - When Alice comes back to the same wave, she sees her edition was not fully 
> saved. It saved only until the instant that Bob began editing.
> - When Bob comes back to the wave, he sees nothing of what he wrote was saved.
> Sometimes it shows the mysterious delta error from:
> http://www.mail-archive.com/[email protected]/msg02036.html
> https://issues.apache.org/jira/browse/WAVE-307
> but other times it shows nothing on the log, so don't know if it's directly 
> related or just chance.

--
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

        

Reply via email to