[OPENDJ-5002] 200s timeout when stopping a replication server Created: 17/Apr/18 Updated: 08/Nov/19 Resolved: 24/Apr/18
|Reporter:||Viktor Nawrath [X] (Inactive)||Assignee:||Fabio Pistolesi|
|Attachments:||5002_script.sh 5002_script2.sh image-2018-04-18-17-43-54-305.png|
|Epic Link:||Bugs 6.5|
Found with DS 6.0.0-RC1
Sometimes when we try to stop a replication server, we reach the timeout of 200s, with a parameter error saying the --port must be specified. This happens randomly in many of our tests, but always when stopping a replication server.
|Comment by Viktor Nawrath [X] (Inactive) [ 17/Apr/18 ]|
The most consistant way to reproduce it is to run:
a few times in a row.
|Comment by Viktor Nawrath [X] (Inactive) [ 18/Apr/18 ]|
I added a script I used to try to reproduce the issue easier/more reliably than with pyforge. You just need to setup 2 DS's and setup the ports in the script... It configures/uncofigures replication, and then restarts both DS's to try to hit the issue, all in a loop.
I went through a few versions of the script, but in the end I found there are 2 general outcomes, depending on wether we provide connection parameters to stop-ds or not:
1) stop-ds without connection parameters
2) stop-ds with connection parameters
|Comment by Viktor Nawrath [X] (Inactive) [ 19/Apr/18 ]|
One more update, instead of `stop-ds -R` I'm doing stop and start... I was able to hit the 200s timeout in the second run, with this log messages on the stderr of stop-ds:
I'm uploading the updated script I used for that.
|Comment by Viktor Nawrath [X] (Inactive) [ 09/Nov/18 ]|
Verified using 6.5.0-RC4 6f964a7cb1f