Opened 7 years ago
Closed 7 years ago
#1670 closed defect (fixed)
RasdaPy_Cannot release connection to server by database.close()
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.5 |
Component: | rasdapy | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description (last modified by )
Normally rasdaman has 9 rasservers to serve queries from client. RasdaPy (https://pypi.python.org/pypi/rasdapy) is one of client as same as Rasql.
In the API, it has a feature to close the connection to rasserver (database.close()). However, it doesn't work as the python script cannot close the connection (the script hangs at closing connection).
Hence, run this test script (https://pastebin.com/g5j2uKFN) 10 times will cause error about no available servers and other client like rasql will have same error.
File "test.py", line 147, in <module> setUp() File "test.py", line 18, in setUp db = con.database("RASBASE") File "/home/rasdaman/.local/lib/python2.7/site-packages/rasdapy/core.py", line 148, in database database = Database(self, name) File "/home/rasdaman/.local/lib/python2.7/site-packages/rasdapy/core.py", line 172, in __init__ self.open() File "/home/rasdaman/.local/lib/python2.7/site-packages/rasdapy/core.py", line 184, in open self.name) File "/home/rasdaman/.local/lib/python2.7/site-packages/rasdapy/remote_procedures.py", line 73, in rasmgr_open_db _TIMEOUT_SECONDS) File "/home/rasdaman/.local/lib/python2.7/site-packages/grpc/beta/_client_adaptations.py", line 310, in __call__ self._request_serializer, self._response_deserializer) File "/home/rasdaman/.local/lib/python2.7/site-packages/grpc/beta/_client_adaptations.py", line 196, in _blocking_unary_unary raise _abortion_error(rpc_error_call) grpc.framework.interfaces.face.face.RemoteError: RemoteError(code=StatusCode.UNKNOWN, details=", There is no available server for the client.")
Change History (3)
comment:1 by , 7 years ago
Description: | modified (diff) |
---|
comment:2 by , 7 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:3 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
does the query otherwise execute correctly?