-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 7.17.2
-
Component/s: None
-
Labels:None
-
Severity:High
-
Team:dev-artifactory-core3
-
Release Notes:Yes
Configuring Artifactory with event base pull replication with HTTPS (in the url) fails.
- Set up a generic local repository on Artifactory-1
- On Artifactory-2, set up a Generic Remote repository pointed to the local Artifactory-1 repo, using https:// in the url.
- Configure Pull Replication as normal in the UI, enable Event based pull replication
- Deploy a file to Artifactory-1 generic local
- Observe that the file does not get pulled to the Artifactory-2 remote repository cache
Note that you will need to configure HTTPS via Nginx.
2020-09-24 16:42:36,463 [Incoming-Replication-Channel-Target-Test2] [DEBUG] (o.a.a.r.c.r.e.InboundReplicationChannel:263) - Could not establish remote replication stream for Target-Test2
java.net.SocketTimeoutException: Read timed out
at java.base/java.net.SocketInputStream.socketRead0(Native Method)
at java.base/java.net.SocketInputStream.socketRead(SocketInputStream.java:115)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
Currently the workaround for fixing this is adding the below parameter in the Nginx.
Proxy_buffering off;
Please see the below link for more details on the above parameter.
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffering
- relates to
-
RTFACT-21262 Exhaustion of async pool when enabling event-based pull replication on HA
- Done