2015-06-01 20:55:27 +03:00
|
|
|
package server
|
|
|
|
|
|
|
|
import (
|
|
|
|
"bytes"
|
2015-11-25 22:50:05 +03:00
|
|
|
|
2015-11-28 14:22:29 +03:00
|
|
|
"github.com/micro/go-micro/codec"
|
2015-11-28 21:54:38 +03:00
|
|
|
"github.com/micro/go-micro/codec/jsonrpc"
|
|
|
|
"github.com/micro/go-micro/codec/protorpc"
|
2015-11-20 19:17:33 +03:00
|
|
|
"github.com/micro/go-micro/transport"
|
server/rpc_codec: if c.codec.Write fails, reset write buffer and encode an error message about the encoding failure
When developing go-micro services, it is frequently possible to set invalid results in the response pointer. When this happens (as I and @trushton personally experienced), `sendResponse()` returns an error correctly explaining what happened (e.g. protobuf refused to encode a bad struct) but the `call()` function one above it in the stack ignores the returned error object.
Thus, invalid structs go un-encoded and the _client side times out_. @trushton and I first caught this in our CI builds when we left a protobuf.Empty field uninitialized (nil) instead of setting it to `&ptypes.Empty{}`. This resulted in an `proto: oneof field has nil value` error, but it was dropped and became a terribly confusing client timeout instead.
This patch is two independent changes:
* In rpc_codec, when a serialization failure occurs serialize an error message, which will correctly become a 500 for HTTP services, about the encoding failure. This means rpc_codec only returns an `error` when a socket failure occurs, which I believe is the behavior that rpc_service is expecting anyway.
* In rpc_service, log any errors returned by sendResponse instead of dropping the error object. This will make debugging client timeouts less of a hassle.
2017-07-12 00:51:36 +03:00
|
|
|
"github.com/pkg/errors"
|
2015-06-01 20:55:27 +03:00
|
|
|
)
|
|
|
|
|
|
|
|
type rpcPlusCodec struct {
|
|
|
|
socket transport.Socket
|
2015-11-28 14:22:29 +03:00
|
|
|
codec codec.Codec
|
2015-06-01 20:55:27 +03:00
|
|
|
|
|
|
|
req *transport.Message
|
2015-10-16 00:06:43 +03:00
|
|
|
buf *readWriteCloser
|
|
|
|
}
|
2015-06-01 20:55:27 +03:00
|
|
|
|
2015-10-16 00:06:43 +03:00
|
|
|
type readWriteCloser struct {
|
2015-06-01 20:55:27 +03:00
|
|
|
wbuf *bytes.Buffer
|
|
|
|
rbuf *bytes.Buffer
|
|
|
|
}
|
|
|
|
|
2015-11-28 14:22:29 +03:00
|
|
|
var (
|
|
|
|
defaultCodecs = map[string]codec.NewCodec{
|
2015-11-28 21:54:38 +03:00
|
|
|
"application/json": jsonrpc.NewCodec,
|
|
|
|
"application/json-rpc": jsonrpc.NewCodec,
|
|
|
|
"application/protobuf": protorpc.NewCodec,
|
|
|
|
"application/proto-rpc": protorpc.NewCodec,
|
|
|
|
"application/octet-stream": protorpc.NewCodec,
|
2015-11-28 14:22:29 +03:00
|
|
|
}
|
|
|
|
)
|
|
|
|
|
2015-10-16 00:06:43 +03:00
|
|
|
func (rwc *readWriteCloser) Read(p []byte) (n int, err error) {
|
|
|
|
return rwc.rbuf.Read(p)
|
2015-06-01 20:55:27 +03:00
|
|
|
}
|
|
|
|
|
2015-10-16 00:06:43 +03:00
|
|
|
func (rwc *readWriteCloser) Write(p []byte) (n int, err error) {
|
|
|
|
return rwc.wbuf.Write(p)
|
|
|
|
}
|
2015-06-01 20:55:27 +03:00
|
|
|
|
2015-10-16 00:06:43 +03:00
|
|
|
func (rwc *readWriteCloser) Close() error {
|
|
|
|
rwc.rbuf.Reset()
|
|
|
|
rwc.wbuf.Reset()
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2015-12-02 02:32:23 +03:00
|
|
|
func newRpcPlusCodec(req *transport.Message, socket transport.Socket, c codec.NewCodec) serverCodec {
|
2015-11-25 22:50:05 +03:00
|
|
|
rwc := &readWriteCloser{
|
|
|
|
rbuf: bytes.NewBuffer(req.Body),
|
|
|
|
wbuf: bytes.NewBuffer(nil),
|
|
|
|
}
|
2015-10-16 13:15:17 +03:00
|
|
|
r := &rpcPlusCodec{
|
2015-11-25 22:50:05 +03:00
|
|
|
buf: rwc,
|
2015-11-28 14:22:29 +03:00
|
|
|
codec: c(rwc),
|
2015-10-16 13:15:17 +03:00
|
|
|
req: req,
|
2015-11-25 22:50:05 +03:00
|
|
|
socket: socket,
|
2015-06-01 20:55:27 +03:00
|
|
|
}
|
2015-10-16 00:06:43 +03:00
|
|
|
return r
|
|
|
|
}
|
|
|
|
|
2015-12-18 23:28:50 +03:00
|
|
|
func (c *rpcPlusCodec) ReadRequestHeader(r *request, first bool) error {
|
2016-01-28 21:11:13 +03:00
|
|
|
m := codec.Message{Header: c.req.Header}
|
2015-12-18 23:28:50 +03:00
|
|
|
|
|
|
|
if !first {
|
|
|
|
var tm transport.Message
|
|
|
|
if err := c.socket.Recv(&tm); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
c.buf.rbuf.Reset()
|
|
|
|
if _, err := c.buf.rbuf.Write(tm.Body); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
2016-01-28 21:11:13 +03:00
|
|
|
m.Header = tm.Header
|
2015-12-16 05:15:09 +03:00
|
|
|
}
|
|
|
|
|
2015-11-28 14:22:29 +03:00
|
|
|
err := c.codec.ReadHeader(&m, codec.Request)
|
|
|
|
r.ServiceMethod = m.Method
|
|
|
|
r.Seq = m.Id
|
|
|
|
return err
|
2015-06-01 20:55:27 +03:00
|
|
|
}
|
|
|
|
|
2015-11-28 14:22:29 +03:00
|
|
|
func (c *rpcPlusCodec) ReadRequestBody(b interface{}) error {
|
|
|
|
return c.codec.ReadBody(b)
|
2015-06-01 20:55:27 +03:00
|
|
|
}
|
|
|
|
|
2015-12-02 02:32:23 +03:00
|
|
|
func (c *rpcPlusCodec) WriteResponse(r *response, body interface{}, last bool) error {
|
2015-10-16 00:06:43 +03:00
|
|
|
c.buf.wbuf.Reset()
|
2015-11-28 14:22:29 +03:00
|
|
|
m := &codec.Message{
|
2016-01-28 21:11:13 +03:00
|
|
|
Method: r.ServiceMethod,
|
|
|
|
Id: r.Seq,
|
|
|
|
Error: r.Error,
|
|
|
|
Type: codec.Response,
|
|
|
|
Header: map[string]string{},
|
2015-11-28 14:22:29 +03:00
|
|
|
}
|
|
|
|
if err := c.codec.Write(m, body); err != nil {
|
server/rpc_codec: if c.codec.Write fails, reset write buffer and encode an error message about the encoding failure
When developing go-micro services, it is frequently possible to set invalid results in the response pointer. When this happens (as I and @trushton personally experienced), `sendResponse()` returns an error correctly explaining what happened (e.g. protobuf refused to encode a bad struct) but the `call()` function one above it in the stack ignores the returned error object.
Thus, invalid structs go un-encoded and the _client side times out_. @trushton and I first caught this in our CI builds when we left a protobuf.Empty field uninitialized (nil) instead of setting it to `&ptypes.Empty{}`. This resulted in an `proto: oneof field has nil value` error, but it was dropped and became a terribly confusing client timeout instead.
This patch is two independent changes:
* In rpc_codec, when a serialization failure occurs serialize an error message, which will correctly become a 500 for HTTP services, about the encoding failure. This means rpc_codec only returns an `error` when a socket failure occurs, which I believe is the behavior that rpc_service is expecting anyway.
* In rpc_service, log any errors returned by sendResponse instead of dropping the error object. This will make debugging client timeouts less of a hassle.
2017-07-12 00:51:36 +03:00
|
|
|
c.buf.wbuf.Reset()
|
|
|
|
m.Error = errors.Wrapf(err, "Unable to encode body").Error()
|
|
|
|
if err := c.codec.Write(m, nil); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2015-06-01 20:55:27 +03:00
|
|
|
}
|
2015-12-16 05:15:09 +03:00
|
|
|
|
2016-01-28 21:11:13 +03:00
|
|
|
m.Header["Content-Type"] = c.req.Header["Content-Type"]
|
2015-06-01 20:55:27 +03:00
|
|
|
return c.socket.Send(&transport.Message{
|
2016-01-28 21:11:13 +03:00
|
|
|
Header: m.Header,
|
2015-10-16 00:06:43 +03:00
|
|
|
Body: c.buf.wbuf.Bytes(),
|
2015-06-01 20:55:27 +03:00
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
func (c *rpcPlusCodec) Close() error {
|
2015-10-16 00:06:43 +03:00
|
|
|
c.buf.Close()
|
2015-11-28 14:22:29 +03:00
|
|
|
c.codec.Close()
|
2015-06-01 20:55:27 +03:00
|
|
|
return c.socket.Close()
|
|
|
|
}
|