How to catch server side errors for jsonrpc server?
php editor Zimo will introduce you how to capture server-side errors of the jsonrpc server. During the development process, server-side errors are often encountered, and it is very important to accurately capture these errors. To solve this problem, we can use try-catch statements to capture server-side errors and return error information to the client. In this way, we can better locate and handle server-side errors and improve program stability and reliability. In the following we will explain in detail how to achieve this process.
Question content
Suppose I have a basic golang jrpc server based on tcp:
package main import ( "fmt" "net" "net/rpc" "net/rpc/jsonrpc" ) type Arith int type Args struct { A, B int } func (t *Arith) Add(args *Args, result *int) error { *result = args.A + args.B return nil } func RunServer() { arith := new(Arith) rpc.Register(arith) listener, err := net.Listen("tcp", ":8080") if err != nil { fmt.Println("Error starting server:", err) return } defer listener.Close() for { conn, err := listener.Accept() if err != nil { fmt.Println("Error accepting connection:", err) continue } go jsonrpc.ServeConn(conn) } }
Is there a way to print "Client disconnected!" when the client disconnects from the server? Is there a callback or something similar on net.Conn?
func main() { go RunServer() client, err := jsonrpc.Dial("tcp", "localhost:8080") if err != nil { fmt.Println("Error connecting to server:", err) return } args := &Args{A: 3, B: 5} var result int // run a method err = client.Call("Arith.Add", args, &result) if err != nil { fmt.Println("Error calling Add method:", err) return } fmt.Printf("Result of %d + %d = %d\n", args.A, args.B, result) // suppose the client closes the client client.Close() // how does the server detect that the client is closed? // would be nice if I could print "client disconnected!" // without having to send jsonrpc heartbeats }
It would be nice if I didn't have to send jsonrpc heartbeat messages.
I tried periodically dummy reading from the conn in the goroutine, but this interferes with the jsonrpc connection.
Solution
The jsonrpc.ServeConn method returns when the client hangs up. Prints a "client disconnected" message after ServeConn returns.
func RunServer() { arith := new(Arith) rpc.Register(arith) listener, err := net.Listen("tcp", ":8080") if err != nil { fmt.Println("Error starting server:", err) return } defer listener.Close() for { conn, err := listener.Accept() if err != nil { fmt.Println("Error accepting connection:", err) continue } go func() { jsonrpc.ServeConn(conn) fmt.Println("client disconnected") // <--- new code here }() } }
The above is the detailed content of How to catch server side errors for jsonrpc server?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The article explains how to use the pprof tool for analyzing Go performance, including enabling profiling, collecting data, and identifying common bottlenecks like CPU and memory issues.Character count: 159

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The article discusses writing unit tests in Go, covering best practices, mocking techniques, and tools for efficient test management.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The article discusses managing Go module dependencies via go.mod, covering specification, updates, and conflict resolution. It emphasizes best practices like semantic versioning and regular updates.

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...
