possible side effect of killed session

[seanpearsonuk]

After killing a solver session in Fluent UI itself and then using the Python interpreter to interact with the dead session, I get errors, which is OK (but maybe we can clean up the behaviour and messaging). However I then see the same errors in the same Python session when using subsequently created solver sessions.

This is the error:

Exception in thread Thread-1:
Traceback (most recent call last):
File "C:\Users\spearson\AppData\Local\Programs\Python\Python38\lib\threading.py", line 932, in _bootstrap_inner
self.run()
File "e:\ansysdev\pyfluent17\pyfluent\src\ansys\fluent\core\fluent_connection.py", line 60, in run
cb()
File "C:\Users\spearson\AppData\Local\Programs\Python\Python38\lib\weakref.py", line 566, in call
return info.func(*info.args, **(info.kwargs or {}))
File "e:\ansysdev\pyfluent17\pyfluent\src\ansys\fluent\core\fluent_connection.py", line 325, in _exit
scheme_eval.exec(("(exit-server)",))
File "e:\ansysdev\pyfluent17\pyfluent\src\ansys\fluent\core\services\scheme_eval.py", line 258, in exec
response = self.service.exec(request)
File "e:\ansysdev\pyfluent17\pyfluent\src\ansys\fluent\core\services\scheme_eval.py", line 47, in exec
return self.__stub.Exec(request, metadata=self.__metadata)
File "E:\ANSYSDev\pyfluent17.env\lib\site-packages\grpc_channel.py", line 946, in call
return _end_unary_response_blocking(state, call, False, None)
File "E:\ANSYSDev\pyfluent17.env\lib\site-packages\grpc_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses; last error: UNAVAILABLE: WSA Error"
debug_error_string = "UNKNOWN:Failed to pick subchannel {created_time:"2022-10-31T17:53:54.376601539+00:00", children:[UNKNOWN:failed to connect to all addresses; last error: UNAVAILABLE: WSA Error {created_time:"2022-10-31T17:53:54.376593887+00:00", grpc_status:14}]}"