Re: 500 error: Failed to look for file

> > I just wanted to first investigate this failed to look for file error, > because even if the artifact exists and is available in another repository > I wasn't convinced it would solve the problem. It sounds like you are on the right track. Confirming secure connectivity to codehaus means the

Re: 500 error: Failed to look for file

We do not. I'm going to add that because the pom file for the artifact that is wanting this artifact as a dependency explicitly lists that repository as well. I just wanted to first investigate this failed to look for file error, because even if the artifact exists and is available in another re

Re: 500 error: Failed to look for file

> > I used the tryssl-1.0-SNAPSHOT.jar to run the same check you did and > received the exact same response back from the server that Archiva is > running on. In that case, the bad mac error seems like it could be an intermittent network-related error. Assuming that you actually want to find tha

Re: 500 error: Failed to look for file

I used the tryssl-1.0-SNAPSHOT.jar to run the same check you did and received the exact same response back from the server that Archiva is running on. From: Nerderman,Adam Sent: Friday, February 06, 2015 11:13 AM To: users Subject: Re: 500 error: Failed t

Re: 500 error: Failed to look for file

We are seeing it, but it has been inconsistent. Usually when I see the failure to transfer errors and record mac errors it moves on, but now sometimes it throws the download error with a stack trace. From: Brent Atkinson Sent: Friday, February 06, 2015 1

Re: 500 error: Failed to look for file

Adam, I just investigated an issue relating to record mac errors, similar to the ones you just posted. That issue was: http://jira.codehaus.org/browse/CONTINUUM-2501 Record mac errors can happen for a number of reasons, so there's no guarantee you are seeing exactly this situation. However, you

Re: 500 error: Failed to look for file

We are running with Java jdk1.7.0_45. From: Brent Atkinson Sent: Friday, February 06, 2015 9:48 AM To: users Subject: Re: 500 error: Failed to look for file It looks like your archiva installation is having issues negotiating a secure connection to nexus.

Re: 500 error: Failed to look for file

It looks like your archiva installation is having issues negotiating a secure connection to nexus.codehaus.org. My guess would be that it is somewhat related to SSLv3. What version of Java are you running on that host? Brent Repository.Codehaus: Download failure on resource [ > https://nexus.code

Re: 500 error: Failed to look for file

Here is the log from Archiva. 2015-02-05 02:13:01,111 [qtp1657925669-42747] WARN org.apache.archiva.proxy.DefaultRepositoryProxyConnectors [] - Transfer error from repository Repository.Codehaus for artifact org.olap4j:olap4j:0.9.7.309-JS-3::pom , continuing to next repository. Error message:

Re: 500 error: Failed to look for file

Hi, This is maven log. Is there any issue in archiva logs? Olivier On 6 February 2015 at 02:27, Nerderman,Adam wrote: > One of our applications is seeing this build failure intermittently. The > artifact that the application they are trying to get does not exist in this > repository, but for so