It appears that when an artifact is deployed to Archiva the md5 that is
generated only contains the hash. When Archiva runs a scan, which for us is
nightly, these md5 files are then fixed to contain both the hash and the
filename. Is there something Archiva can do for the md5 files that are
gen
quivalent?
Brent
On Fri, Feb 6, 2015 at 11:33 AM, Nerderman,Adam wrote:
> 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.
>
> ____
&
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
> sun.net.www.protocol.https.HttpsURLConnectionImpl.getHeaderFields(HttpsURLConnectionImpl.java:283)
> at TrySSL.main(TrySSL.java:61)
Brent
On Fri, Feb 6, 2015 at 9:53 AM, Nerderman,Adam wrote:
> We are running with Java jdk1.7.0_45.
>
>
>
pom]:Received
> fatal
> alert: bad_record_mac (cause: javax.net.ssl.SSLException: Received fatal
> alert: bad_record_mac)
On Fri, Feb 6, 2015 at 9:21 AM, Nerderman,Adam wrote:
> Here is the log from Archiva.
>
> 2015-02-05 02:13:01,111 [qtp1
:?]
From: Olivier Lamy
Sent: Friday, February 06, 2015 5:39 AM
To: users@archiva.apache.org
Subject: 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
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 some reason instead of always moving on it is failing with
a 500 error saying it failed to look for the file. Is there any know
?It looks like when a tar.gz file is uploaded Archiva displays it correctly in
all of the pages, but then when you go to the artifacts tab and try to download
the file is tries to just use the .gz file extension and then says the artifact
does not exist.
Is this a known bug, or something fixab
2014 00:31, "Nerderman,Adam" wrote:
> We've been seeing this error periodically when some of our uses that are
> trying to download artifacts far away from where the server is
> geographically since upgrading from Archiva 1.3.5 to 2.1.1.
>
>
> Has anyone else se
We've been seeing this error periodically when some of our uses that are trying
to download artifacts far away from where the server is geographically since
upgrading from Archiva 1.3.5 to 2.1.1.
Has anyone else seen this error? Is there something with Archiva or a
configuration that would hav
I was the one that brought this up and Deng was able to reproduce it and
created the issue. This had to do with if you try to view the artifacts tab for
a snapshot artifact in Archiva it is creating the resolver-status.properties
file in the data for some reason and then either not ignoring it o
iva.apache.org>"
mailto:users@archiva.apache.org>>
Cc: "Nerderman,Adam" mailto:nerde...@oclc.org>>, Janet
Bickle mailto:bic...@oclc.org>>, "Graham,Bill"
mailto:grah...@oclc.org>>
Subject: Re: Error viewing Artifacts tab
Hi Adam,
It seems you have a resolve
When I try to view the Artifacts tab we see the UI display: An error has
happened you must contact the administrator to check the logs
Then in the logs I see:
2014-09-05 14:37:51,865 [qtp871962456-2360] WARN
org.apache.cxf.phase.PhaseInterceptorChain [] - Application
{http://services.rest.ar
Archiva seemingly does not allow you to allocate more than 4096m to the heap.
Running version 2.0.1 of Archiva we can see the heap constantly going up until
Archiva runs out of memory and becomes unresponsive.
It doesn't seem like we were the only ones to see and report this issue with
performa
Sorry, I realized I wasn’t subscribed to the list so I think that was why I
didn’t see the responses to these.
I believe the stacktrace from the GET request email actually is related to
being unable to view the Artifacts tab or anything of the other tabs as well.
When we try to view the Artifa
Sorry, I realized I wasn’t subscribed to the list so I think that was why I
didn’t see the responses to these.
I believe the stacktrace from the GET request email actually is related to
being unable to view the Artifacts tab or anything of the other tabs as well.
When we try to view the Artifa
We have some requests to Archiva 2.0.1 with the following message from Maven
after saying the GET request failed: Premature end of Content-Length delimited
message body (expected: 85354042; received: 5038080
In the log I see:
2014-08-26 19:12:49,348 [qtp1180936672-509] ERROR
org.apache.jackra
When we try to view the Artifacts tab for an artifact we receive the error
"failed to retrieve state of intermediary node". Is this how people should be
able to see the jar, pom, javadoc, java-source or any artifacts related to this
artifact and if so then what might be the issue here and how do
18 matches
Mail list logo
