Juha Heinanen writes:
> in both cases, sems reports to syslog something like this:
>
> May 22 13:41:41 siika sems[25160]: [#7f6f56fb0700] [JsonrpcPeerConnection,
> RpcPeer.h:79] DEBUG: created connection '309F4F23-537DD465000D002D-56FB0700'
> May 22 13:41:41 siika sems[25160]: [#7f6f56fb0700] [registerConnection,
> RpcServerLoop.cpp:458] DEBUG: registered connection
> '309F4F23-537DD465000D002D-56FB0700'
> May 22 13:41:41 siika sems[25160]: [#7f6f56fb0700] [read_cb,
> RpcServerLoop.cpp:112] DEBUG: read_cb in connection 0x2535980
> May 22 13:41:41 siika sems[25160]: [#7f6f56fb0700] [netstringsRead,
> RpcPeer.cpp:211] DEBUG: received '{'
> May 22 13:41:41 siika sems[25160]: [#7f6f56fb0700] [netstringsRead,
> RpcPeer.cpp:257] INFO: Protocol error on connection [0x2535980/47]:
> invalid character in size
using tcp transport, ngrep shows this:
#######
T 2014/05/23 08:30:29.796710 127.0.0.1:59182 -> 127.0.0.1:7080 [AP]
{"jsonrpc":"2.0","method":"calls","id":"1394e7c6-18ec-442a-90a6-39cb7eaa8c14"}
the query looks ok to me. sems seems to be expecting to read a "size"
containing decimal digits and does not like it, when it receives json
request starting with '{'.
what is this "size" that sems wants to get? where is it specified?
-- juha
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
