You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Jesse Farinacci <ji...@gmail.com> on 2012/11/06 22:42:51 UTC

Archiva 1.4-M3 needs restart frequently

Greetings,

I'm using Apache Archiva 1.4-M3 (JS) on a RHEL system, with OpenJDK
1.7. About once every two days, I need to restart Archiva because it
is only serving up HTTP 502 responses.

Is there some information I can collect to help diagnose this problem? Thanks,

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

Re: Archiva 1.4-M3 needs restart frequently

Posted by Olivier Lamy <ol...@apache.org>.
2012/11/12 Jesse Farinacci <ji...@gmail.com>:
> Greetings,
>
> On Thu, Nov 8, 2012 at 4:36 AM, Olivier Lamy <ol...@apache.org> wrote:
>> And please proxyConnectorRuleConfigurations section if you have .
>> I don't understand why this need restart ?
>> BTW I will try to add unit tests for such case next week (currently on
>> vacations)
>
> Vacation means you aren't checking email. :-)
>
> Here is my entire archiva.xml file: https://gist.github.com/f1b1ac1f41bc8dbf6658

    <proxyConnector>
      <order>1</order>
      <sourceRepoId>repository-external-codehaus-staged</sourceRepoId>
      <targetRepoId>remote-repository-external-codehaus-staged</targetRepoId>
      <blackListPatterns>
        <blackListPattern>com/acme/**</blackListPattern>
      </blackListPatterns>
      <policies>
        <propagate-errors>stop</propagate-errors>
        <releases>always</releases>
        <checksum>fail</checksum>
        <snapshots>always</snapshots>
        <propagate-errors-on-update>always</propagate-errors-on-update>
        <cache-failures>no</cache-failures>
      </policies>
    </proxyConnector>

 <propagate-errors>stop</propagate-errors> causes the error to be
returned immediately
That's probably the cause of your issue here when the remote repo doesn't work.


>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Archiva 1.4-M3 needs restart frequently

Posted by Jesse Farinacci <ji...@gmail.com>.
Greetings,

On Thu, Nov 8, 2012 at 4:36 AM, Olivier Lamy <ol...@apache.org> wrote:
> And please proxyConnectorRuleConfigurations section if you have .
> I don't understand why this need restart ?
> BTW I will try to add unit tests for such case next week (currently on
> vacations)

Vacation means you aren't checking email. :-)

Here is my entire archiva.xml file: https://gist.github.com/f1b1ac1f41bc8dbf6658

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

Re: Archiva 1.4-M3 needs restart frequently

Posted by Olivier Lamy <ol...@apache.org>.
Hi,
And please proxyConnectorRuleConfigurations section if you have .
I don't understand why this need restart ?
BTW I will try to add unit tests for such case next week (currently on
vacations)


2012/11/8 Brett Porter <br...@apache.org>:
> Hi Jesse,
>
> On 07/11/2012, at 1:05 PM, Jesse Farinacci <ji...@gmail.com> wrote:
>
>> Greetings,
>>
>> On Tue, Nov 6, 2012 at 8:20 PM, Brett Porter <br...@apache.org> wrote:
>>> Is 502 from Archiva itself, or a reverse proxy you have in front of it?
>>>
>>> Anything in the Archiva logs at that time? Perhaps you can use the "dump" function of the service wrapper to get a thread dump that might show any information about why it doesn't respond.
>>
>> The 502 is from Archiva itself.
>>
>> logs/archiva.log:2012-11-06 16:41:05,452 [qtp1145832897-27] WARN
>> org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] -
>> Transfer error from repository
>> "remote-repository-external-codehaus-staged" for resource
>> com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1,
>> continuing to next repository. Error message: Download failure on
>> resource [https://nexus.codehaus.org/content/groups/staging//com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1]:Failed
>> to transfer file:
>> https://nexus.codehaus.org/content/groups/staging/com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1.
>> Return code is: 502, ReasonPhrase:Bad Gateway.
>>
>> So perhaps this isn't exactly an Archiva problem, however, I am pretty
>> sure that I had blacklisted all my remote-repository-external-* from
>> my com/acme/* artifacts. Is there detailed documentation, and test
>> cases, that this is working properly in 1.4?
>
> Ok, that's quite different from what I understood :) It looks like nexus.codehaus.org was down at that time, but it's back up now.
>
> To your question about black/whitelisting - are you able to paste the relevant proxyConnector section for remote-repository-external-codehaus-staged from your archiva.xml?
>
> Thanks,
> Brett
>



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Archiva 1.4-M3 needs restart frequently

Posted by Brett Porter <br...@apache.org>.
Hi Jesse,

On 07/11/2012, at 1:05 PM, Jesse Farinacci <ji...@gmail.com> wrote:

> Greetings,
> 
> On Tue, Nov 6, 2012 at 8:20 PM, Brett Porter <br...@apache.org> wrote:
>> Is 502 from Archiva itself, or a reverse proxy you have in front of it?
>> 
>> Anything in the Archiva logs at that time? Perhaps you can use the "dump" function of the service wrapper to get a thread dump that might show any information about why it doesn't respond.
> 
> The 502 is from Archiva itself.
> 
> logs/archiva.log:2012-11-06 16:41:05,452 [qtp1145832897-27] WARN
> org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] -
> Transfer error from repository
> "remote-repository-external-codehaus-staged" for resource
> com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1,
> continuing to next repository. Error message: Download failure on
> resource [https://nexus.codehaus.org/content/groups/staging//com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1]:Failed
> to transfer file:
> https://nexus.codehaus.org/content/groups/staging/com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1.
> Return code is: 502, ReasonPhrase:Bad Gateway.
> 
> So perhaps this isn't exactly an Archiva problem, however, I am pretty
> sure that I had blacklisted all my remote-repository-external-* from
> my com/acme/* artifacts. Is there detailed documentation, and test
> cases, that this is working properly in 1.4?

Ok, that's quite different from what I understood :) It looks like nexus.codehaus.org was down at that time, but it's back up now.

To your question about black/whitelisting - are you able to paste the relevant proxyConnector section for remote-repository-external-codehaus-staged from your archiva.xml?

Thanks,
Brett

Re: Archiva 1.4-M3 needs restart frequently

Posted by Jesse Farinacci <ji...@gmail.com>.
Greetings,

On Tue, Nov 6, 2012 at 8:20 PM, Brett Porter <br...@apache.org> wrote:
> Is 502 from Archiva itself, or a reverse proxy you have in front of it?
>
> Anything in the Archiva logs at that time? Perhaps you can use the "dump" function of the service wrapper to get a thread dump that might show any information about why it doesn't respond.

The 502 is from Archiva itself.

logs/archiva.log:2012-11-06 16:41:05,452 [qtp1145832897-27] WARN
org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] -
Transfer error from repository
"remote-repository-external-codehaus-staged" for resource
com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1,
continuing to next repository. Error message: Download failure on
resource [https://nexus.codehaus.org/content/groups/staging//com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1]:Failed
to transfer file:
https://nexus.codehaus.org/content/groups/staging/com/acme/groupId/artifactId/1-SNAPSHOT/maven-metadata.xml.sha1.
Return code is: 502, ReasonPhrase:Bad Gateway.

So perhaps this isn't exactly an Archiva problem, however, I am pretty
sure that I had blacklisted all my remote-repository-external-* from
my com/acme/* artifacts. Is there detailed documentation, and test
cases, that this is working properly in 1.4?

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

Re: Archiva 1.4-M3 needs restart frequently

Posted by Brett Porter <br...@apache.org>.
Is 502 from Archiva itself, or a reverse proxy you have in front of it?

Anything in the Archiva logs at that time? Perhaps you can use the "dump" function of the service wrapper to get a thread dump that might show any information about why it doesn't respond.

- Brett

On 07/11/2012, at 8:42 AM, Jesse Farinacci <ji...@gmail.com> wrote:

> Greetings,
> 
> I'm using Apache Archiva 1.4-M3 (JS) on a RHEL system, with OpenJDK
> 1.7. About once every two days, I need to restart Archiva because it
> is only serving up HTTP 502 responses.
> 
> Is there some information I can collect to help diagnose this problem? Thanks,
> 
> -Jesse
> 
> -- 
> There are 10 types of people in this world, those
> that can read binary and those that can not.

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter