Archiva
  1. Archiva
  2. MRM-631

network proxy is always used when defined

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: 1.1.1
    • Component/s: remote proxy
    • Labels:
      None
    • Environment:
      Linux and Windows with JRE 1.5
    • Number of attachments :
      1

      Description

      I've installed Archiva 1.0 as a Maven proxy repository for internet and corporate repositories.
      I've added the remote Internet Repositories, the network proxy and the proxy connectors.

      It works well for the internet repositories but when Archiva tries to connect to the corporate repository in the same subnetwork, Archiva uses
      the network proxy despite the proxy connector is set to Direct Connection.

      If no proxy connectors is defined, Archiva didn't try to get data form the corporate repository.

      If no network proxy is defined, Archiva can contact the corporate repository but not the Internet ones.

      I've done a test with network capture (wireshark ex ethereal) to confirm the network proxy defined is used. And the result confirm my opinion, the proxy is used.

      I attach the archiva.xml configuration file in order to check it.
      The corporate repository is localrepo and is available in http form the archiva server using lynx, wget and telnet.

      Thanks for your help

      1. archiva.xml
        5 kB
        Jacques REYNARD

        Activity

        Hide
        Brian Jackson added a comment -

        Thanks Arnaud, maybe that's my confusion in understanding the comments on this issue. But like I said, I'm still experiencing it with 1.1.1 so its not fixed if its a workaround in the code base. I didn't have the -Dhttp.nonProxyHosts set so I'm trying that and hopefully that's the workaround Brett was referring to. I'll also try the http wagon if it doesn't work. I know I tried that under Archiva 1.0.1 and it hosed my instance so I'm hesitant to try it.

        Show
        Brian Jackson added a comment - Thanks Arnaud, maybe that's my confusion in understanding the comments on this issue. But like I said, I'm still experiencing it with 1.1.1 so its not fixed if its a workaround in the code base. I didn't have the -Dhttp.nonProxyHosts set so I'm trying that and hopefully that's the workaround Brett was referring to. I'll also try the http wagon if it doesn't work. I know I tried that under Archiva 1.0.1 and it hosed my instance so I'm hesitant to try it.
        Hide
        Brett Porter added a comment -

        we were using the http wagon for a while but encountered some deadlocking in the version of httpclient. I believe there's an open issue for switching to something else (we're now looking at the jetty http client), which is why I closed this one. The obvious bug was fixed, with limitations.

        Are you experiencing it in all cases, or only on concurrent access to both proxied and non-proxied repos?

        Show
        Brett Porter added a comment - we were using the http wagon for a while but encountered some deadlocking in the version of httpclient. I believe there's an open issue for switching to something else (we're now looking at the jetty http client), which is why I closed this one. The obvious bug was fixed, with limitations. Are you experiencing it in all cases, or only on concurrent access to both proxied and non-proxied repos?
        Hide
        Brian Jackson added a comment -

        I experience it after Archiva has been up for some time. For 1.0.2 it was only about 5 minutes, for 1.1.1 it was good for about 3 days. After that point it will switch to always using the proxy server even for remote repos configured to use direct connect. The concurrency of the access is not an issue since after this issue happens it will happen consistently until a restart even with no other users accessing the server.

        Show
        Brian Jackson added a comment - I experience it after Archiva has been up for some time. For 1.0.2 it was only about 5 minutes, for 1.1.1 it was good for about 3 days. After that point it will switch to always using the proxy server even for remote repos configured to use direct connect. The concurrency of the access is not an issue since after this issue happens it will happen consistently until a restart even with no other users accessing the server.
        Hide
        Brett Porter added a comment -

        Perhaps it is triggered by an exception that doesn't reset the properties. Would you mind creating a new issue for us to investigate this specifically?

        Show
        Brett Porter added a comment - Perhaps it is triggered by an exception that doesn't reset the properties. Would you mind creating a new issue for us to investigate this specifically?
        Hide
        Brian Jackson added a comment -

        Brett, I created MRM-909.

        Show
        Brian Jackson added a comment - Brett, I created MRM-909 .

          People

          • Assignee:
            Brett Porter
            Reporter:
            Jacques REYNARD
          • Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: