You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you create a minimal example where you demonstrate the problems with connections automatically going down? It could be a result of the server automatically closing the socket. There should be no such mechanism in the client code.
There's a JsonRpcFileLogger class which logs to file. I'm not sure what your question is regarding the logging.
I tried the same thing using the jconcpp server usi ng 2 distincts program, I have not found the problem with needing to disconnect before sending new call request.
Hi,
Using a tcp rpc client connection there seems being a disconnection after a while, if we don't send commands.
the call() replies with not connected
Is there an automatic disconnect ? That was the first problem.
I have tried using jcon client with many python json tcp servers. unfortunately most of them are not able to reliably communicate with jcon !!!!!
Finally I found this working API : https://github.com/joshmarshall/jsonrpctcp
It works , BUT... It is not possible to send 2 calls without disconnecting the client from the server and initiating a new connection.
The code for client side is :
the python code for server side is :
What is the way to log on the jconcpp side ? There is a jcon_client_log.txt file generated, but is empty !
The text was updated successfully, but these errors were encountered: