WaveService.fetchWavelet sometimes returns null even for existing waveId.

[GoogleCodeExporter]

I assume that since the Wave API became part of the Wiab project - issues with 
the Wave API should be opened here. Please correct me if I am wrong.

What steps will reproduce the problem?
1. Run Wiab server.
2. Setup OAUTH token to use the Wiab Data API (as described at 
http://code.google.com/apis/wave/wavedata. Just need to replace the OAUTH URLs  
for GWave with Wiab URLs). 
3. Try to fetch existing wave in Wiab instance from step (1) several times. 
(Make sure to access the correct Wiab RPC_URL - i.e. 
http://example.com:9898/robot/dataapi/rpc).

What is the expected output? What do you see instead?

Expected: The WaveService.fetchWavelet always returns the wavelet data.
Actual: sometimes (about 50% of attempts) the wavelet is null. 

Note - the issue does not happen with GWave - only with Wiab.

OS: Ubuntu
Wiab revision: 856

Original issue reported on code.google.com by vega113 on 24 Jan 2011 at 3:26

[GoogleCodeExporter]

Please review at: http://codereview.waveprotocol.org/522001

Original comment by vega113 on 24 Jan 2011 at 4:00

[GoogleCodeExporter]

Original comment by vega113 on 24 Jan 2011 at 4:01

• Changed state: Started

[GoogleCodeExporter]

Original comment by vega113 on 7 Feb 2011 at 6:35

• Changed state: Fixed