I suspect the failing precondition is a mistake that's only become exposed
with the new wave panel and the user of userdata wavelets. It can probably
be removed.

On 4 November 2010 09:33, James Purser <[email protected]> wrote:

> After the latest build I'm starting to see errors like the below appear:
>
> INFO: Submit result for [WaveletName collaborynth.com.au!w+tHb25sdS_7A
> collaborynth.com.au!conv+root] by [email protected] applied 1 ops
> at v: 5 t: 1288823256714
> java.lang.IllegalStateException: Received overlapping submit requests to
> subscription [WaveViewSubscription wave: [WaveId 
> collaborynth.com.au!w+tHb25sdS_7A],
> channel: ch2]
>         at
> com.google.common.base.Preconditions.checkState(Preconditions.java:172)
>         at
> org.waveprotocol.box.server.frontend.WaveViewSubscription.submitRequest(WaveViewSubscription.java:82)
>         at
> org.waveprotocol.box.server.frontend.UserManager.submitRequest(UserManager.java:121)
>         at
> org.waveprotocol.box.server.frontend.ClientFrontendImpl.submitRequest(ClientFrontendImpl.java:252)
>         at
> org.waveprotocol.box.server.frontend.WaveClientRpcImpl.submit(WaveClientRpcImpl.java:159)
>         at
> org.waveprotocol.box.server.waveserver.WaveClientRpc$ProtocolWaveClientRpc$1.submit(WaveClientRpc.java:4459)
>         at
> org.waveprotocol.box.server.waveserver.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:619)
> 04/11/2010 9:27:36 AM
> org.waveprotocol.box.server.rpc.ServerRpcProvider$Connection$1 run
> INFO: error = java.lang.IllegalStateException: Received overlapping submit
> requests to subscription [WaveViewSubscription wave: [WaveId
> collaborynth.com.au!w+tHb25sdS_7A], channel: ch2]
> 04/11/2010 9:27:36 AM
> org.waveprotocol.box.server.frontend.WaveViewSubscription submitResponse
> INFO: Submit resolved on channel ch2
>
> This appears to crash the wave. It's happening with local and federated
> waves.
>
> James
>
> --
> You received this message because you are subscribed to the Google Groups
> "Wave Protocol" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<wave-protocol%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/wave-protocol?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en.

Reply via email to