From 8786d832a5ee3539b37ad7480ba58e377581006f Mon Sep 17 00:00:00 2001 From: Brett Porter Date: Tue, 22 Feb 2011 03:19:40 +0000 Subject: [PATCH] [MRM-1248] improve documentation about potential issues with the network proxy configuration git-svn-id: https://svn.apache.org/repos/asf/archiva/trunk@1073214 13f79535-47bb-0310-9956-ffa450edef68 --- .../src/site/apt/adminguide/network-proxies.apt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/archiva-docs/src/site/apt/adminguide/network-proxies.apt b/archiva-docs/src/site/apt/adminguide/network-proxies.apt index 320cac109..72ca9b823 100644 --- a/archiva-docs/src/site/apt/adminguide/network-proxies.apt +++ b/archiva-docs/src/site/apt/adminguide/network-proxies.apt @@ -17,5 +17,18 @@ Understanding Network Proxy Configuration of Apache Archiva Once configured, the network proxy can be attached to operations that access remote resources. At present, this is configured on the remote repository proxy connectors that need to access the remote repository over the HTTP protocol. +* Network Proxy Settings and the JVM + + As Archiva still targets Java 5 and uses the built-in networking libraries, it must configure these settings using + system properties. This can be problematic in two scenarios: + + * if you use multiple different network proxies on different proxy connectors, they may clash + + * if you deploy other applications into the same container as Archiva, they will likely pick up the settings + + [] + + Please refer to {{{http://jira.codehaus.org/browse/MRM-1248} MRM-1248}} for workarounds and to track the issue. + ~~TODO: walkthrough configuration