Ask Your Question

Sage cell server dead after one request from client

asked 2017-03-01 15:47:08 +0200

wrogn gravatar image

I want to access the SAGE cell server programatically from Python 3. I found this example here, which uses the Websockets interface.

It works nice and smooth, but only for exactly one request, because after that the execution_state of the connection is dead. The documentation even describes that:

You’ll get a kernel dead message on the IOPub channel when the cell times out. If you don’t have 
interacts, it will time out pretty much immediately. If you do have interacts, then the timeout 
is something 30 or 60 seconds between each execute_request.

If I connect each time anew it will be slower for me and waste much more resources on the server side (I guess), so it would be best if I could somehow re-use the connection. Timeout only needs to be some 1-5 seconds, basically a couple of RTTs of the Internet.

Is there anything I could do?

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2017-03-07 22:05:22 +0200

updated 2017-03-19 21:07:00 +0200

Some aspects of the behavior of the cell sever are designed to reduce the costs of its operation, and I would assume that applies here. If you want to know whether a change to the public server is possible, you could open an issue on to get a reply from the maintainer of the server.

The documentation mentioned above has moved to here.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2017-03-01 15:47:08 +0200

Seen: 243 times

Last updated: Mar 19 '17