Opened 9 years ago
Closed 9 years ago
#1070 closed defect (fixed)
rasnet error handling needs improvement
Reported by: | Dimitar Misev | Owned by: | Alex Toader |
---|---|---|---|
Priority: | major | Milestone: | 9.1.x |
Component: | rasnet | Version: | development |
Keywords: | Cc: | Alex Dumitru | |
Complexity: | Medium |
Description
Try this query, which segfaults (info in comment:3:ticket:245), with single rasserver, and notice what happens to rasmgr (can't even shut it down with stop_rasdaman.sh):
rasql -q 'create collection test_insert GreySet' --user rasadmin --passwd rasadmin
Attachments (1)
Change History (8)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 9 years ago
Can you point the changeset that fixes this? Still seems to be an issue for me (note the query above will not cause a segfault anymore after my patch was applied).
comment:4 by , 9 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
ticket:1044 - Set a fixed timeout for client requests. If a server does not reply within 5 seconds, the service call is aborted.
I will test it again.
by , 9 years ago
Attachment: | 0001-ticket-1049-test-subsetting.patch added |
---|
comment:6 by , 9 years ago
Try the systemtest/testcases_mandatory/test_subsetting/test.sh after applying the attachment:0001-ticket-1049-test-subsetting.patch, some of the tests cause segfaults for example. My rasmgr.conf has 2 servers defined.
comment:7 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
The fix for the problem with rasmgr is waiting to be applied.