Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Sender: Brett Porter <brett@porterclan.net>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: HTTP code 500 when trying to access a artifact.
From: Brett Porter <brett@apache.org>
In-Reply-To: 
 <C32C5590B22C1B46A2CEABC254D4A74201042B0C30@courier.corp.upromise.com>
Date: Mon, 4 Oct 2010 10:06:59 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <97A957B6-A222-4F09-92AD-2DB47CCFFAA2@apache.org>
References: <4CA4A92F.5080803@upromise.com>
 <959AE288-735B-4CD4-9E56-7620F4C2B401@apache.org>
 <4CA616C7.3010609@upromise.com>,<AANLkTikSdbFX9TEDYtscsKL33fOqXwDjh=Ht0fshX7R+@mail.gmail.com>
 <C32C5590B22C1B46A2CEABC254D4A74201042B0C30@courier.corp.upromise.com>
To: users@archiva.apache.org

When you hit the URL in a browser, does the page give you any more =
details about the 500 error?

It's unusual for it not to show up in the server logs.

On 03/10/2010, at 3:01 AM, Delaney, Michael wrote:

> Yes, over 40Gb free on the server.
> ________________________________________
> From: odeaching@gmail.com [odeaching@gmail.com] On Behalf Of Deng =
Ching [oching@apache.org]
> Sent: Saturday, October 02, 2010 12:06 AM
> To: users@archiva.apache.org
> Subject: Re: HTTP code 500 when trying to access a artifact.
>=20
> Hi,
>=20
> Did you check if there is enough disk space in your server?
>=20
> Thanks,
> Deng
>=20
> On Sat, Oct 2, 2010 at 1:13 AM, Michael Delaney =
<mdelaney@upromise.com> wrote:
>>=20
>> I'm not seeing any exceptions but I am seeing the entries in request =
log
>> that contain the 500 error codes.
>>=20
>> On 9/30/2010 7:19 PM, Brett Porter wrote:
>>>=20
>>> Do you see anything in the archiva server log that would correspond =
to the
>>> return of the 500 code?
>>>=20
>>> - Brett
>>>=20
>>> On 01/10/2010, at 1:13 AM, Michael Delaney wrote:
>>>=20
>>>> All,
>>>>=20
>>>> Our Archiva 1.1.2 server has started to act up a lot as of late. =
We're
>>>> seeing some 500 error codes when trying to deply our artifacts. =
We're also
>>>> seeing some behavior where an artifact is uploaded to Archiva (any =
type:
>>>> pom, zip, jar, war; of varying size) but build freezes during the =
"upload"
>>>> process. The newly updated file is accessible via WGET/HTTP calls =
but the
>>>> build doesn't progress.
>>>>=20
>>>> I assume this requires me to bump a logging value in log4j but I'm =
not
>>>> sure which ones I should bump; or just brute force it and bump all =
of them.
>>>>=20
>>>> [ Error Snippet ]
>>>> [INFO] Error deploying artifact: Failed to transfer file:
>>>> =
http://archiva:8080/archiva/repository/snapshot/groupId/myProject/1.0.0-SN=
APSHOT/myProject-1.0.0-20100930.010002-48-config.jar.
>>>> Return code is: 500
>>>>=20
>>>>=20
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://brettporter.wordpress.com/
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>=20

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/