Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@archiva.apache.org
Received-SPF: pass (nike.apache.org: domain of nicolas.deloof@gmail.com
 designates 209.85.128.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=KVb1rf9d0+ONAb2lFojwE0Bxua0b59z5O5UHbg1hz9Rbl1VBwlReAV4Wa/GU6axYJI
         0atHJWWveUT4Yj0arEOS2etp4sVNZRh+/KyCwoKtqn67fgd1pHLQXttL2J2rh+jgzITC
         JBU//CPpfWLaQjjasdffbwxrLptPYz2NmzpVI=
MIME-Version: 1.0
In-Reply-To: <D2F233A3-BCBD-417C-9357-EFB69A16A458@apache.org>
References: <1a57a2980903212259r6853be13h8d51ef26fed94bc4@mail.gmail.com>
	<1a57a2980903230914q1db4190en51a551b735f6a428@mail.gmail.com>
	<f345f3480903230936y4fa4298and8e626c10169b3@mail.gmail.com>
	<1a57a2980903230950h38cb7a02s10d25ef427b7e70d@mail.gmail.com>
	<1a57a2980903231003u669cf1f0v3f0e697ca4b8625d@mail.gmail.com>
	<1a57a2980903231024l5cf64a6ra9ae92dc7c568f3a@mail.gmail.com>
	<4D564A26-3357-4C57-8B12-9C27FFFD3E6F@apache.org>
 <1a57a2980903240052j55b859f5i324cbc3fa16f14cb@mail.gmail.com>
	<4c39e3030903240107w30b959bbh39077ce9106b05e1@mail.gmail.com>
	<D2F233A3-BCBD-417C-9357-EFB69A16A458@apache.org>
Date: Tue, 24 Mar 2009 11:41:52 +0100
Message-ID: <4c39e3030903240341u313f204fv8a08a74213dce5dd@mail.gmail.com>
Subject: Re: [VOTE] Release Archiva 1.2
From: nicolas de loof <nicolas.deloof@gmail.com>
To: dev@archiva.apache.org
Content-Type: multipart/alternative; boundary=0016e65b41a0d680160465db0850

--0016e65b41a0d680160465db0850
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

%d{ABSOLUTE}, how can this be missconfigured ?Anyway I don't focus on logs,
but on the spring BeanInstanciation errors


On Tue, Mar 24, 2009 at 11:39 AM, Brett Porter <brett@apache.org> wrote:

> This seems like it has to be a misconfiguration of log4j.xml on the
> PatternLayout?
>
>
> On 24/03/2009, at 7:07 PM, nicolas de loof wrote:
>
>  I changed the log4j.xml to use a ConsoleAppender and everything in TRACE
>> I now have a 20Mo log and still no running archiva, but this strange
>> stacktrace that could explain no log with "standard" setting :
>>
>> log4j:ERROR Error occured while converting date.
>> java.lang.NullPointerException
>> at java.lang.System.arraycopy(Native Method)
>> at java.lang.AbstractStringBuilder.getChars(Unknown Source)
>> at java.lang.StringBuffer.getChars(Unknown Source)
>> at
>>
>> org.apache.log4j.helpers.AbsoluteTimeDateFormat.format(AbsoluteTimeDateFormat.java:117)
>> at java.text.DateFormat.format(Unknown Source)
>> at
>>
>> org.apache.log4j.helpers.PatternParser$DatePatternConverter.convert(PatternParser.java:444)
>> at
>> org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64)
>> at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
>> at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
>> at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
>> at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
>> at
>>
>> org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
>> at org.apache.log4j.Category.callAppenders(Category.java:203)
>> at org.apache.log4j.Category.forcedLog(Category.java:388)
>> at org.apache.log4j.Category.log(Category.java:853)
>> at org.slf4j.impl.Log4jLoggerAdapter.log(Log4jLoggerAdapter.java:509)
>> at
>>
>> org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:106)
>>
>>
>>
>> On Tue, Mar 24, 2009 at 8:52 AM, Maria Odea Ching <oching@apache.org>
>> wrote:
>>
>>  It turns out I indeed forgot to set the appserver properties again
>>> yesterday, I was using a different console from where I've set the env so
>>> it
>>> didn't get set. I tried it again today, and I was able to access the
>>> Archiva
>>> webapp now (thanks Brett!) :) Maybe you did the same Nicolas?
>>>
>>> Anyway, here's my +1 for 1.2..
>>>
>>> -Deng
>>>
>>> On Tue, Mar 24, 2009 at 7:29 AM, Brett Porter <brett@apache.org> wrote:
>>>
>>>  Have you set the properties for the appserver[.base|.home] and added
>>>> mail
>>>> and activation into the Tomcat install?
>>>>
>>>> It sounds to me like this is still the same situation as in 1.1 by the
>>>>
>>> bugs
>>>
>>>> that were filed, so we can continue with the release (once there are
>>>>
>>> votes),
>>>
>>>> and I'd be happy to sit down later this week and remove all vestige of
>>>>
>>> those
>>>
>>>> system properties for a quick 1.2.1.
>>>>
>>>> Cheers,
>>>> Brett
>>>>
>>>> On 24/03/2009, at 4:24 AM, Maria Odea Ching wrote:
>>>>
>>>> The log errors went away during startup but now I get a 404 when I
>>>>
>>> access
>>>
>>>> the webapp. I'm now getting the same problem as Nicolas :( I wonder if
>>>>>
>>>> it
>>>
>>>> is
>>>>> indeed related to the logs.. because I was able to access Archiva when
>>>>> I
>>>>> was
>>>>> having the log errors during startup and now that the logs dir are
>>>>> properly
>>>>> set, I can no longer access the webapp and get a 404 instead.
>>>>>
>>>>> -Deng
>>>>>
>>>>>
>>>>>  --
>>>> Brett Porter
>>>> brett@apache.org
>>>> http://blogs.exist.com/bporter/
>>>>
>>>>
>>>>
>>>
>>> --
>>> Maria Odea Ching
>>> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>>> www.exist.com | Innovation Delivered
>>>
>>>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>

--0016e65b41a0d680160465db0850--