search

latos / wave-protocol

Automatically exported from code.google.com/p/wave-protocol
0 stars 0 forks source link

console client NPE #129

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. execute run-server.sh with fake account store
2. execute run-client-console.sh and type enter at passwd prompt

Then the client crashes with:

java.lang.NullPointerException
    at org.waveprotocol.box.client.ClientBackend.receiveWaveletUpdate(ClientBackend.java:683)
    at org.waveprotocol.box.client.ClientBackend$5.run(ClientBackend.java:490)
    at org.waveprotocol.box.client.ClientBackend$5.run(ClientBackend.java:485)
    at com.google.protobuf.RpcUtil$1.run(RpcUtil.java:81)
    at com.google.protobuf.RpcUtil$1.run(RpcUtil.java:73)
    at org.waveprotocol.box.server.rpc.ClientRpcController.response(ClientRpcController.java:131)
    at org.waveprotocol.box.server.rpc.ClientRpcChannelImpl$1.message(ClientRpcChannelImpl.java:73)
    at org.waveprotocol.box.server.rpc.WebSocketChannel.handleMessageString(WebSocketChannel.java:103)
    at org.waveprotocol.box.server.rpc.WebSocketClientChannel$1.run(WebSocketClientChannel.java:41)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:636)

Original issue reported on code.google.com by so...@google.com on 29 Oct 2010 at 4:26

GoogleCodeExporter commented 8 years ago 
I have a fix coming. The client was not handling messages that came with just a 
channel id.

Note that the client does actually continue to function after the NPE, well 
enough for testing, anyway.

Original comment by ano...@google.com on 29 Oct 2010 at 8:17

GoogleCodeExporter commented 8 years ago

Original comment by ano...@google.com on 1 Nov 2010 at 12:05