You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Elie Delorme (JIRA)" <ji...@codehaus.org> on 2010/07/30 15:35:32 UTC
[jira] Created: (MRM-1413) network-proxy configuration doesn't seen
to work
network-proxy configuration doesn't seen to work
------------------------------------------------
Key: MRM-1413
URL: http://jira.codehaus.org/browse/MRM-1413
Project: Archiva
Issue Type: Bug
Affects Versions: 1.3
Reporter: Elie Delorme
Attachments: archiva.xml
Our machine doesn't even have a public ip, so all outbound connections have to go through an http proxy.
1. Added a remote repository with url "https://maven.atlassian.com/repository/public"
2. Added a network proxy called "adenyo-proxy"
3. Added a proxy-connector that uses both
archiva.log:
{noformat}
2010-07-30 12:09:15,162 [btpool0-12] WARN org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer error from repository "atlassian" for artifact org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2::pom, continuing to next repository. Error message: Download failure on resource [https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom]:Error transferring file: Connection refused (cause: java.net.ConnectException: Connection refused)
{noformat}
Also, clicking on the settings link below a proxy connector and on the "Edit Network Proxy" link leads to an unconfigured proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1413) network-proxy configuration doesn't
seen to work
Posted by "Elie Delorme (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232943#action_232943 ]
Elie Delorme commented on MRM-1413:
-----------------------------------
I was able to make the proxy work for ssl repos by adding -Dhttps.proxyHost=my_proxy_host and -Dhttps.proxyPort=my_proxy_port to the wrapper.conf file.
It works, but I consider this a workaround.
> network-proxy configuration doesn't seen to work
> ------------------------------------------------
>
> Key: MRM-1413
> URL: http://jira.codehaus.org/browse/MRM-1413
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Elie Delorme
> Attachments: archiva.xml
>
>
> Our machine doesn't even have a public ip, so all outbound connections have to go through an http proxy.
> 1. Added a remote repository with url "https://maven.atlassian.com/repository/public"
> 2. Added a network proxy called "adenyo-proxy"
> 3. Added a proxy-connector that uses both
> archiva.log:
> {noformat}
> 2010-07-30 12:09:15,162 [btpool0-12] WARN org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer error from repository "atlassian" for artifact org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2::pom, continuing to next repository. Error message: Download failure on resource [https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom]:Error transferring file: Connection refused (cause: java.net.ConnectException: Connection refused)
> {noformat}
> Also, clicking on the settings link below a proxy connector and on the "Edit Network Proxy" link leads to an unconfigured proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRM-1413) network-proxy configuration doesn't seen
to work
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1413:
------------------------------
Fix Version/s: 1.4
thanks, that's something to look at. It should be a straightforward check on the URL to set the properties correctly in the proxy code.
> network-proxy configuration doesn't seen to work
> ------------------------------------------------
>
> Key: MRM-1413
> URL: http://jira.codehaus.org/browse/MRM-1413
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Elie Delorme
> Fix For: 1.4
>
> Attachments: archiva.xml
>
>
> Our machine doesn't even have a public ip, so all outbound connections have to go through an http proxy.
> 1. Added a remote repository with url "https://maven.atlassian.com/repository/public"
> 2. Added a network proxy called "adenyo-proxy"
> 3. Added a proxy-connector that uses both
> archiva.log:
> {noformat}
> 2010-07-30 12:09:15,162 [btpool0-12] WARN org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer error from repository "atlassian" for artifact org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2::pom, continuing to next repository. Error message: Download failure on resource [https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom]:Error transferring file: Connection refused (cause: java.net.ConnectException: Connection refused)
> {noformat}
> Also, clicking on the settings link below a proxy connector and on the "Edit Network Proxy" link leads to an unconfigured proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRM-1413) network-proxy configuration doesn't seen
to work
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRM-1413.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 1.4)
1.4-M1
Assignee: Olivier Lamy
should be fixed with wagon-http 2.0 and without adding sys props now
> network-proxy configuration doesn't seen to work
> ------------------------------------------------
>
> Key: MRM-1413
> URL: https://jira.codehaus.org/browse/MRM-1413
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Elie Delorme
> Assignee: Olivier Lamy
> Fix For: 1.4-M1
>
> Attachments: archiva.xml
>
>
> Our machine doesn't even have a public ip, so all outbound connections have to go through an http proxy.
> 1. Added a remote repository with url "https://maven.atlassian.com/repository/public"
> 2. Added a network proxy called "adenyo-proxy"
> 3. Added a proxy-connector that uses both
> archiva.log:
> {noformat}
> 2010-07-30 12:09:15,162 [btpool0-12] WARN org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer error from repository "atlassian" for artifact org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2::pom, continuing to next repository. Error message: Download failure on resource [https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom]:Error transferring file: Connection refused (cause: java.net.ConnectException: Connection refused)
> {noformat}
> Also, clicking on the settings link below a proxy connector and on the "Edit Network Proxy" link leads to an unconfigured proxy.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-1413) network-proxy configuration doesn't
seen to work
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231152#action_231152 ]
Brett Porter commented on MRM-1413:
-----------------------------------
It appears to have been configured correctly. There are some known issues with config not being persisted until restart - does it still fail after a restart?
Does it also fail with non-SSL remote repos?
Archiva is using the standard java.net.* library and its proxy connection settings. You might try running with the -Djavax.net.debug flag to get additional configuration info, or changing the log level in Archiva's log4j.xml for the proxy connectors. Make sure the app is not sharing a container with other apps that might conflict with the JVM proxy properties.
Let us know how it goes.
> network-proxy configuration doesn't seen to work
> ------------------------------------------------
>
> Key: MRM-1413
> URL: http://jira.codehaus.org/browse/MRM-1413
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Elie Delorme
> Attachments: archiva.xml
>
>
> Our machine doesn't even have a public ip, so all outbound connections have to go through an http proxy.
> 1. Added a remote repository with url "https://maven.atlassian.com/repository/public"
> 2. Added a network proxy called "adenyo-proxy"
> 3. Added a proxy-connector that uses both
> archiva.log:
> {noformat}
> 2010-07-30 12:09:15,162 [btpool0-12] WARN org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer error from repository "atlassian" for artifact org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2::pom, continuing to next repository. Error message: Download failure on resource [https://maven.atlassian.com/repository/public/org/apache/maven/plugins/maven-war-plugin/2.1-alpha-2/maven-war-plugin-2.1-alpha-2.pom]:Error transferring file: Connection refused (cause: java.net.ConnectException: Connection refused)
> {noformat}
> Also, clicking on the settings link below a proxy connector and on the "Edit Network Proxy" link leads to an unconfigured proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira