[VOTE] Release Archiva 1.2

[nicolas de loof-2]

The ClassNotFoundException are related to plexus roles,
the ConcurrentModificationException may be the real cause of my startup
failure, but it is related to redback :

Caused by: java.util.ConcurrentModificationException
 at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
at java.util.AbstractList$Itr.next(Unknown Source)
 at
org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processRoles(DefaultRoleModelProcessor.java:218)
at
org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.process(DefaultRoleModelProcessor.java:64)
 at
org.codehaus.plexus.redback.role.DefaultRoleManager.loadApplication(DefaultRoleManager.java:165)
at
org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(DefaultRoleManager.java:107)
 at
org.codehaus.plexus.redback.role.DefaultRoleManager.initialize(DefaultRoleManager.java:411)
at
org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)

On Tue, Mar 24, 2009 at 9:30 AM, nicolas de loof
<nicolas.deloof@...>wrote:

> Got some more infos on my startup error  :
>
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'modelResolver': Initialization of bean failed;
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.apache.maven.project.ModelResolver
>
> Is ModelResolver supposed to be a maven-project class ?
>
> I also get :
> ClassNotFoundException:
> org.apache.maven.artifact.repository.metadata.RepositoryMetadataBuilder
>
>
>
> I also notice some concurrency errors after this one :
>
> Caused by: java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> at java.util.AbstractList$Itr.next(Unknown Source)
>  at
> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processRoles(DefaultRoleModelProcessor.java:218)
>
> On Tue, Mar 24, 2009 at 9:07 AM, nicolas de loof <nicolas.deloof@...
> > 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@...>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@...> 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@...
>>> > http://blogs.exist.com/bporter/
>>> >
>>> >
>>>
>>>
>>> --
>>> Maria Odea Ching
>>> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>>> www.exist.com | Innovation Delivered
>>>
>>
>>
>

[nicolas de loof-2]

I've tried all possible grep expression but can't find where
"org.apache.maven.project.ModelResolver" is set in archiva codebase...
Seems to be used as a plexus role :
Failed to convert property value of type [java.lang.String] to required type
[java.lang.Class] for property 'role'; nested exception is
java.lang.IllegalArgumentException: Cannot find class
[org.apache.maven.project.ModelResolver]

but just can't find where / why :'(

On Tue, Mar 24, 2009 at 10:22 AM, nicolas de loof
<nicolas.deloof@...>wrote:

> The ClassNotFoundException are related to plexus roles,
> the ConcurrentModificationException may be the real cause of my startup
> failure, but it is related to redback :
>
> Caused by: java.util.ConcurrentModificationException
>  at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> at java.util.AbstractList$Itr.next(Unknown Source)
>  at
> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processRoles(DefaultRoleModelProcessor.java:218)
> at
> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.process(DefaultRoleModelProcessor.java:64)
>  at
> org.codehaus.plexus.redback.role.DefaultRoleManager.loadApplication(DefaultRoleManager.java:165)
> at
> org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(DefaultRoleManager.java:107)
>  at
> org.codehaus.plexus.redback.role.DefaultRoleManager.initialize(DefaultRoleManager.java:411)
> at
> org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)
>
> On Tue, Mar 24, 2009 at 9:30 AM, nicolas de loof <nicolas.deloof@...
> > wrote:
>
>> Got some more infos on my startup error  :
>>
>> org.springframework.beans.factory.BeanCreationException: Error creating
>> bean with name 'modelResolver': Initialization of bean failed;
>> ...
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.maven.project.ModelResolver
>>
>> Is ModelResolver supposed to be a maven-project class ?
>>
>> I also get :
>> ClassNotFoundException:
>> org.apache.maven.artifact.repository.metadata.RepositoryMetadataBuilder
>>
>>
>>
>> I also notice some concurrency errors after this one :
>>
>> Caused by: java.util.ConcurrentModificationException
>> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
>> at java.util.AbstractList$Itr.next(Unknown Source)
>>  at
>> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processRoles(DefaultRoleModelProcessor.java:218)
>>
>> On Tue, Mar 24, 2009 at 9:07 AM, nicolas de loof <
>> nicolas.deloof@...> 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@...>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@...> 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@...
>>>> > http://blogs.exist.com/bporter/
>>>> >
>>>> >
>>>>
>>>>
>>>> --
>>>> Maria Odea Ching
>>>> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>>>> www.exist.com | Innovation Delivered
>>>>
>>>
>>>
>>
>

[brettporter]

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@...> 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@...>  
>> 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@...
>>> 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@...
http://blogs.exist.com/bporter/

[nicolas de loof-2]

%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@...> 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@...>
>> 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@...> 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@...
>>>> 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@...
> http://blogs.exist.com/bporter/
>
>

[brettporter]

Is this one repeatable? It might be that the app is getting hit at the  
same time as it is trying to migrate the roles on startup and we need  
to put some sync in place.

- Brett

On 24/03/2009, at 8:22 PM, nicolas de loof wrote:

> The ClassNotFoundException are related to plexus roles,
> the ConcurrentModificationException may be the real cause of my  
> startup
> failure, but it is related to redback :
>
> Caused by: java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> at java.util.AbstractList$Itr.next(Unknown Source)
> at
> org
> .codehaus
> .plexus
> .redback
> .role
> .processor
> .DefaultRoleModelProcessor
> .processRoles(DefaultRoleModelProcessor.java:218)
> at
> org
> .codehaus
> .plexus
> .redback
> .role
> .processor
> .DefaultRoleModelProcessor.process(DefaultRoleModelProcessor.java:64)
> at
> org
> .codehaus
> .plexus
> .redback
> .role.DefaultRoleManager.loadApplication(DefaultRoleManager.java:165)
> at
> org
> .codehaus
> .plexus
> .redback
> .role.DefaultRoleManager.loadRoleModel(DefaultRoleManager.java:107)
> at
> org
> .codehaus
> .plexus
> .redback.role.DefaultRoleManager.initialize(DefaultRoleManager.java:
> 411)
> at
> org
> .codehaus
> .plexus
> .spring
> .PlexusLifecycleBeanPostProcessor
> .postProcessAfterInitialization
> (PlexusLifecycleBeanPostProcessor.java:217)
>
> On Tue, Mar 24, 2009 at 9:30 AM, nicolas de loof
> <nicolas.deloof@...>wrote:
>
>> Got some more infos on my startup error  :
>>
>> org.springframework.beans.factory.BeanCreationException: Error  
>> creating
>> bean with name 'modelResolver': Initialization of bean failed;
>> ...
>> Caused by: java.lang.ClassNotFoundException:
>> org.apache.maven.project.ModelResolver
>>
>> Is ModelResolver supposed to be a maven-project class ?
>>
>> I also get :
>> ClassNotFoundException:
>> org
>> .apache.maven.artifact.repository.metadata.RepositoryMetadataBuilder
>>
>>
>>
>> I also notice some concurrency errors after this one :
>>
>> Caused by: java.util.ConcurrentModificationException
>> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
>> at java.util.AbstractList$Itr.next(Unknown Source)
>> at
>> org
>> .codehaus
>> .plexus
>> .redback
>> .role
>> .processor
>> .DefaultRoleModelProcessor
>> .processRoles(DefaultRoleModelProcessor.java:218)
>>
>> On Tue, Mar 24, 2009 at 9:07 AM, nicolas de loof <nicolas.deloof@...
>>> 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@...>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@...>  
>>>> 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@...
>>>>> 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@...
http://blogs.exist.com/bporter/

[nicolas de loof-2]

This is fully repeatable, and the app is deployed on a private test context
path, so no request is coming in yet.

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

> Is this one repeatable? It might be that the app is getting hit at the same
> time as it is trying to migrate the roles on startup and we need to put some
> sync in place.
>
> - Brett
>
>
> On 24/03/2009, at 8:22 PM, nicolas de loof wrote:
>
>  The ClassNotFoundException are related to plexus roles,
>> the ConcurrentModificationException may be the real cause of my startup
>> failure, but it is related to redback :
>>
>> Caused by: java.util.ConcurrentModificationException
>> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
>> at java.util.AbstractList$Itr.next(Unknown Source)
>> at
>>
>> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processRoles(DefaultRoleModelProcessor.java:218)
>> at
>>
>> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.process(DefaultRoleModelProcessor.java:64)
>> at
>>
>> org.codehaus.plexus.redback.role.DefaultRoleManager.loadApplication(DefaultRoleManager.java:165)
>> at
>>
>> org.codehaus.plexus.redback.role.DefaultRoleManager.loadRoleModel(DefaultRoleManager.java:107)
>> at
>>
>> org.codehaus.plexus.redback.role.DefaultRoleManager.initialize(DefaultRoleManager.java:411)
>> at
>>
>> org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)
>>
>> On Tue, Mar 24, 2009 at 9:30 AM, nicolas de loof
>> <nicolas.deloof@...>wrote:
>>
>>  Got some more infos on my startup error  :
>>>
>>> org.springframework.beans.factory.BeanCreationException: Error creating
>>> bean with name 'modelResolver': Initialization of bean failed;
>>> ...
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.apache.maven.project.ModelResolver
>>>
>>> Is ModelResolver supposed to be a maven-project class ?
>>>
>>> I also get :
>>> ClassNotFoundException:
>>> org.apache.maven.artifact.repository.metadata.RepositoryMetadataBuilder
>>>
>>>
>>>
>>> I also notice some concurrency errors after this one :
>>>
>>> Caused by: java.util.ConcurrentModificationException
>>> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
>>> at java.util.AbstractList$Itr.next(Unknown Source)
>>> at
>>>
>>> org.codehaus.plexus.redback.role.processor.DefaultRoleModelProcessor.processRoles(DefaultRoleModelProcessor.java:218)
>>>
>>> On Tue, Mar 24, 2009 at 9:07 AM, nicolas de loof <
>>> nicolas.deloof@...
>>>
>>>> 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@...
>>>> >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@...>
>>>>> 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@...
>>>>>> 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@...
> http://blogs.exist.com/bporter/
>
>

[brettporter]

On 24/03/2009, at 9:41 PM, nicolas de loof wrote:

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

Looks right, does it work with the default setting?

- Brett

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

[brettporter]

You can remove wagon-ssh from WEB-INF/lib. Nexus-indexer drags in a  
large number of unneeded dependencies. I'm not sure why it's  
triggering an error for you and not others though.

- Brett

On 24/03/2009, at 6:38 PM, nicolas de loof wrote:

> Please don't forget the wagon-ssl issue with typo in  
> NullKnownHost*s*Provider
> class name
>
> On Tue, Mar 24, 2009 at 7:14 AM, Brett Porter <brett@...>  
> wrote:
>
>>
>> On 24/03/2009, at 5:09 PM, Shi Yusen wrote:
>>
>> Thanks - if you would like help fixing the issue on OpenJDK we can
>>>> work through that separately.
>>>>
>>> I guess it's a struts issue as I just found this in struts wiki:
>>> http://cwiki.apache.org/confluence/display/WW/Ready%2C+Set%2C
>>> +Go!?focusedCommentId=87257#comment-87257
>>> "Try adding xalan.jar and serializer.jar to common/endorsed  
>>> directory of
>>> Tomcat. This solved the problem for me (and many others,  
>>> apparently)."
>>>
>>
>> Thanks - feel free to put that in JIRA if you want to keep track.
>>
>>
>>> It is in JIRA already, hopefully someone will push that through for
>>>> the next release.
>>>>
>>> I'll try to translate the messages into Chinese when this is done.
>>>
>>
>> Much appreciated. We have quite a number of strings that are not  
>> yet in
>> resource files, and we could surely use the help :)
>>
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@...
>> http://blogs.exist.com/bporter/
>>
>>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

[brettporter]

On 24/03/2009, at 9:49 PM, nicolas de loof wrote:

> This is fully repeatable, and the app is deployed on a private test  
> context
> path, so no request is coming in yet.

Does the test set up have an existing users database or a clean users  
database?

Cheers,
Brett

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

[nicolas de loof-2]

Right, we may exclude it from dependencies then, archiva is huge enough ;)
Any idea where the "modelResolver" bean comes from ?


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

> You can remove wagon-ssh from WEB-INF/lib. Nexus-indexer drags in a large
> number of unneeded dependencies. I'm not sure why it's triggering an error
> for you and not others though.
>
> - Brett
>
>
> On 24/03/2009, at 6:38 PM, nicolas de loof wrote:
>
>  Please don't forget the wagon-ssl issue with typo in
>> NullKnownHost*s*Provider
>> class name
>>
>> On Tue, Mar 24, 2009 at 7:14 AM, Brett Porter <brett@...> wrote:
>>
>>
>>> On 24/03/2009, at 5:09 PM, Shi Yusen wrote:
>>>
>>> Thanks - if you would like help fixing the issue on OpenJDK we can
>>>
>>>> work through that separately.
>>>>>
>>>>>  I guess it's a struts issue as I just found this in struts wiki:
>>>> http://cwiki.apache.org/confluence/display/WW/Ready%2C+Set%2C
>>>> +Go!?focusedCommentId=87257#comment-87257
>>>> "Try adding xalan.jar and serializer.jar to common/endorsed directory of
>>>> Tomcat. This solved the problem for me (and many others, apparently)."
>>>>
>>>>
>>> Thanks - feel free to put that in JIRA if you want to keep track.
>>>
>>>
>>>  It is in JIRA already, hopefully someone will push that through for
>>>>
>>>>> the next release.
>>>>>
>>>>>  I'll try to translate the messages into Chinese when this is done.
>>>>
>>>>
>>> Much appreciated. We have quite a number of strings that are not yet in
>>> resource files, and we could surely use the help :)
>>>
>>>
>>> - Brett
>>>
>>> --
>>> Brett Porter
>>> brett@...
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

[nicolas de loof-2]

I'm sharing the database from my existing Archiva 1.1.1 instance

On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...> wrote:

> On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>
>  This is fully repeatable, and the app is deployed on a private test
>> context
>> path, so no request is coming in yet.
>>
>
> Does the test set up have an existing users database or a clean users
> database?
>
> Cheers,
> Brett
>
>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

[brettporter]

Are you able to check if it works with a clean one? I did try the  
upgrade earlier, but I wonder if anyone else is testing an upgrade  
from an older version?

- Brett

On 24/03/2009, at 10:04 PM, nicolas de loof wrote:

> I'm sharing the database from my existing Archiva 1.1.1 instance
>
> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...>  
> wrote:
>
>> On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>
>> This is fully repeatable, and the app is deployed on a private test
>>> context
>>> path, so no request is coming in yet.
>>>
>>
>> Does the test set up have an existing users database or a clean users
>> database?
>>
>> Cheers,
>> Brett
>>
>>
>> --
>> Brett Porter
>> brett@...
>> http://blogs.exist.com/bporter/
>>
>>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

[nicolas de loof-2]

java.lang.OutOfMemoryError: PermGen space :-/
Seems i've made too much start/stop tests - This time I will need some help
from my system admin :)

On Tue, Mar 24, 2009 at 12:10 PM, Brett Porter <brett@...> wrote:

> Are you able to check if it works with a clean one? I did try the upgrade
> earlier, but I wonder if anyone else is testing an upgrade from an older
> version?
>
> - Brett
>
>
> On 24/03/2009, at 10:04 PM, nicolas de loof wrote:
>
>  I'm sharing the database from my existing Archiva 1.1.1 instance
>>
>> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...> wrote:
>>
>>  On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>>
>>> This is fully repeatable, and the app is deployed on a private test
>>>
>>>> context
>>>> path, so no request is coming in yet.
>>>>
>>>>
>>> Does the test set up have an existing users database or a clean users
>>> database?
>>>
>>> Cheers,
>>> Brett
>>>
>>>
>>> --
>>> Brett Porter
>>> brett@...
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

[brettporter]

Ok, it looks like your instance is somehow picking out all the bad  
metadata in Maven releases :)

Same thing here:

http://mail-archives.apache.org/mod_mbox/continuum-dev/200902.mbox/%3CC889F1E980FF68449AE8DD327F2C9A1F050D5827@...%3E

That component is defined in maven-project, but the class doesn't exist.

Do you know if there's some setting in plexus-spring that might be  
trying to validate all these only in some environments?

- Brett

On 24/03/2009, at 7:30 PM, nicolas de loof wrote:

> Got some more infos on my startup error  :
>
> org.springframework.beans.factory.BeanCreationException: Error  
> creating bean
> with name 'modelResolver': Initialization of bean failed;
> ...
> Caused by: java.lang.ClassNotFoundException:
> org.apache.maven.project.ModelResolver
>
> Is ModelResolver supposed to be a maven-project class ?
>
> I also get :
> ClassNotFoundException:
> org
> .apache.maven.artifact.repository.metadata.RepositoryMetadataBuilder
>
>
>
> I also notice some concurrency errors after this one :
>
> Caused by: java.util.ConcurrentModificationException
> at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> at java.util.AbstractList$Itr.next(Unknown Source)
> at
> org
> .codehaus
> .plexus
> .redback
> .role
> .processor
> .DefaultRoleModelProcessor
> .processRoles(DefaultRoleModelProcessor.java:218)
>
> On Tue, Mar 24, 2009 at 9:07 AM, nicolas de loof
> <nicolas.deloof@...>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@...>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@...>  
>>> 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@...
>>>> 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@...
http://blogs.exist.com/bporter/

[nicolas de loof-2]

Archiva starts with a fresh new user database.
But I can't create the admin :
java.lang.IllegalAccessError: tried to access method
javax.mail.internet.InternetAddress.<init>(Ljava/lang/String;Z)

Seems my tomcat instance doesn't have the expected javamail version


On Tue, Mar 24, 2009 at 12:18 PM, nicolas de loof
<nicolas.deloof@...>wrote:

> java.lang.OutOfMemoryError: PermGen space :-/
> Seems i've made too much start/stop tests - This time I will need some help
> from my system admin :)
>
> On Tue, Mar 24, 2009 at 12:10 PM, Brett Porter <brett@...> wrote:
>
>> Are you able to check if it works with a clean one? I did try the upgrade
>> earlier, but I wonder if anyone else is testing an upgrade from an older
>> version?
>>
>> - Brett
>>
>>
>> On 24/03/2009, at 10:04 PM, nicolas de loof wrote:
>>
>>  I'm sharing the database from my existing Archiva 1.1.1 instance
>>>
>>> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...> wrote:
>>>
>>>  On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>>>
>>>> This is fully repeatable, and the app is deployed on a private test
>>>>
>>>>> context
>>>>> path, so no request is coming in yet.
>>>>>
>>>>>
>>>> Does the test set up have an existing users database or a clean users
>>>> database?
>>>>
>>>> Cheers,
>>>> Brett
>>>>
>>>>
>>>> --
>>>> Brett Porter
>>>> brett@...
>>>> http://blogs.exist.com/bporter/
>>>>
>>>>
>>>>
>> --
>> Brett Porter
>> brett@...
>> http://blogs.exist.com/bporter/
>>
>>
>

[brettporter]

I'm using 1.4.

On 24/03/2009, at 10:25 PM, nicolas de loof wrote:

> Archiva starts with a fresh new user database.
> But I can't create the admin :
> java.lang.IllegalAccessError: tried to access method
> javax.mail.internet.InternetAddress.<init>(Ljava/lang/String;Z)
>
> Seems my tomcat instance doesn't have the expected javamail version
>
>
> On Tue, Mar 24, 2009 at 12:18 PM, nicolas de loof
> <nicolas.deloof@...>wrote:
>
>> java.lang.OutOfMemoryError: PermGen space :-/
>> Seems i've made too much start/stop tests - This time I will need  
>> some help
>> from my system admin :)
>>
>> On Tue, Mar 24, 2009 at 12:10 PM, Brett Porter <brett@...>  
>> wrote:
>>
>>> Are you able to check if it works with a clean one? I did try the  
>>> upgrade
>>> earlier, but I wonder if anyone else is testing an upgrade from an  
>>> older
>>> version?
>>>
>>> - Brett
>>>
>>>
>>> On 24/03/2009, at 10:04 PM, nicolas de loof wrote:
>>>
>>> I'm sharing the database from my existing Archiva 1.1.1 instance
>>>>
>>>> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...>  
>>>> wrote:
>>>>
>>>> On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>>>>
>>>>> This is fully repeatable, and the app is deployed on a private  
>>>>> test
>>>>>
>>>>>> context
>>>>>> path, so no request is coming in yet.
>>>>>>
>>>>>>
>>>>> Does the test set up have an existing users database or a clean  
>>>>> users
>>>>> database?
>>>>>
>>>>> Cheers,
>>>>> Brett
>>>>>
>>>>>
>>>>> --
>>>>> Brett Porter
>>>>> brett@...
>>>>> http://blogs.exist.com/bporter/
>>>>>
>>>>>
>>>>>
>>> --
>>> Brett Porter
>>> brett@...
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

[brettporter]

+1

It has been working for me and the signatures look correct.

I'm quite concerned by the problems Nicolas is seeing, but we've seen  
a number of people with successful installs. We might need to focus on  
improving the Tomcat installation experience for 1.2.1.

- Brett

On 22/03/2009, at 4:59 PM, Maria Odea Ching wrote:

> Hi Everyone,
> The Archiva 1.2 release has been staged. The binaries, including the
> sources, signatures and checksums, are available here:
>
> http://people.apache.org/builds/archiva/1.2/<http://people.apache.org/builds/archiva/1.1.2/ 
> >
>
> You can take a look at the release notes at
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14288&styleName=Text&projectId=10980or
> http://people.apache.org/~oching/staging-sites/archiva-1.2/release-notes.html
> <http://people.apache.org/%7Eoching/archiva/1.1.2/release- 
> notes.html> While
> the staged site can be viewed here:
>
> http://people.apache.org/~oching/staging-sites/archiva-1.2/<http://people.apache.org/%7Eoching/archiva/1.1.2 
> >
>
> Everyone is encouraged to vote and give their feedback.
>
> [ ] +1 Release it!
> [ ] 0
> [ ] -1 Don't release it, because..
>
> The vote will be open for 72 hours.
> Thanks to everyone who contributed to this release :)
>
>
> Cheers,
> Deng
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype:  
> maria.odea.ching |
> www.exist.com | Innovation Delivered

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

[nicolas de loof-2]

My tomcat has mail.jar 1.2 in common/libbut this version allready defines a
public InternetAddress( String ) AFAIK.


On Tue, Mar 24, 2009 at 12:33 PM, Brett Porter <brett@...> wrote:

> I'm using 1.4.
>
>
> On 24/03/2009, at 10:25 PM, nicolas de loof wrote:
>
>  Archiva starts with a fresh new user database.
>> But I can't create the admin :
>> java.lang.IllegalAccessError: tried to access method
>> javax.mail.internet.InternetAddress.<init>(Ljava/lang/String;Z)
>>
>> Seems my tomcat instance doesn't have the expected javamail version
>>
>>
>> On Tue, Mar 24, 2009 at 12:18 PM, nicolas de loof
>> <nicolas.deloof@...>wrote:
>>
>>  java.lang.OutOfMemoryError: PermGen space :-/
>>> Seems i've made too much start/stop tests - This time I will need some
>>> help
>>> from my system admin :)
>>>
>>> On Tue, Mar 24, 2009 at 12:10 PM, Brett Porter <brett@...> wrote:
>>>
>>>  Are you able to check if it works with a clean one? I did try the
>>>> upgrade
>>>> earlier, but I wonder if anyone else is testing an upgrade from an older
>>>> version?
>>>>
>>>> - Brett
>>>>
>>>>
>>>> On 24/03/2009, at 10:04 PM, nicolas de loof wrote:
>>>>
>>>> I'm sharing the database from my existing Archiva 1.1.1 instance
>>>>
>>>>>
>>>>> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...>
>>>>> wrote:
>>>>>
>>>>> On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>>>>
>>>>>>
>>>>>> This is fully repeatable, and the app is deployed on a private test
>>>>>>
>>>>>>  context
>>>>>>> path, so no request is coming in yet.
>>>>>>>
>>>>>>>
>>>>>>>  Does the test set up have an existing users database or a clean
>>>>>> users
>>>>>> database?
>>>>>>
>>>>>> Cheers,
>>>>>> Brett
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Brett Porter
>>>>>> brett@...
>>>>>> http://blogs.exist.com/bporter/
>>>>>>
>>>>>>
>>>>>>
>>>>>>  --
>>>> Brett Porter
>>>> brett@...
>>>> http://blogs.exist.com/bporter/
>>>>
>>>>
>>>>
>>>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>
>

[nicolas de loof-2]

After javamail update I get it to work, and I also get logs in archiva.log
:D
So as a summary
- on tomcat 5.5 javamail > 1.2 seems to be required,
- migration from a 1.1 user database is broken
- some bad component.xml metadata are repported by the spring-plexus bridge

The 2nd one is a restriction that must be documented in the release note as
this is not easy to know what's wrong when the app didn't start.

As I really have fiew time to test the release, and even less to contribute,
here is my +0

On Tue, Mar 24, 2009 at 2:02 PM, nicolas de loof
<nicolas.deloof@...>wrote:

> My tomcat has mail.jar 1.2 in common/libbut this version allready defines
> a public InternetAddress( String ) AFAIK.
>
>
> On Tue, Mar 24, 2009 at 12:33 PM, Brett Porter <brett@...> wrote:
>
>> I'm using 1.4.
>>
>>
>> On 24/03/2009, at 10:25 PM, nicolas de loof wrote:
>>
>>  Archiva starts with a fresh new user database.
>>> But I can't create the admin :
>>> java.lang.IllegalAccessError: tried to access method
>>> javax.mail.internet.InternetAddress.<init>(Ljava/lang/String;Z)
>>>
>>> Seems my tomcat instance doesn't have the expected javamail version
>>>
>>>
>>> On Tue, Mar 24, 2009 at 12:18 PM, nicolas de loof
>>> <nicolas.deloof@...>wrote:
>>>
>>>  java.lang.OutOfMemoryError: PermGen space :-/
>>>> Seems i've made too much start/stop tests - This time I will need some
>>>> help
>>>> from my system admin :)
>>>>
>>>> On Tue, Mar 24, 2009 at 12:10 PM, Brett Porter <brett@...>
>>>> wrote:
>>>>
>>>>  Are you able to check if it works with a clean one? I did try the
>>>>> upgrade
>>>>> earlier, but I wonder if anyone else is testing an upgrade from an
>>>>> older
>>>>> version?
>>>>>
>>>>> - Brett
>>>>>
>>>>>
>>>>> On 24/03/2009, at 10:04 PM, nicolas de loof wrote:
>>>>>
>>>>> I'm sharing the database from my existing Archiva 1.1.1 instance
>>>>>
>>>>>>
>>>>>> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter <brett@...>
>>>>>> wrote:
>>>>>>
>>>>>> On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>>>>>
>>>>>>>
>>>>>>> This is fully repeatable, and the app is deployed on a private test
>>>>>>>
>>>>>>>  context
>>>>>>>> path, so no request is coming in yet.
>>>>>>>>
>>>>>>>>
>>>>>>>>  Does the test set up have an existing users database or a clean
>>>>>>> users
>>>>>>> database?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Brett
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Brett Porter
>>>>>>> brett@...
>>>>>>> http://blogs.exist.com/bporter/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>  --
>>>>> Brett Porter
>>>>> brett@...
>>>>> http://blogs.exist.com/bporter/
>>>>>
>>>>>
>>>>>
>>>>
>> --
>> Brett Porter
>> brett@...
>> http://blogs.exist.com/bporter/
>>
>>
>

[James William Dumay]

-1

I know it is a little late in the process, but I want to vote against
releasing 1.2.

MRM-1154 blocks all users of Maven 2.1.x from using Archiva since our
metadata merging barfs on the xml schema attributes that were slipped
into the 2.1.x format.

It might also be wise for us to ship a 1.1.4 release that allows
compatibility for those who are sticking to the current stable release
event after 1.2 is GA.

Thoughts?

James

nicolas de loof wrote:

> After javamail update I get it to work, and I also get logs in archiva.log
> :D
> So as a summary
> - on tomcat 5.5 javamail>  1.2 seems to be required,
> - migration from a 1.1 user database is broken
> - some bad component.xml metadata are repported by the spring-plexus bridge
>
> The 2nd one is a restriction that must be documented in the release note as
> this is not easy to know what's wrong when the app didn't start.
>
> As I really have fiew time to test the release, and even less to contribute,
> here is my +0
>
> On Tue, Mar 24, 2009 at 2:02 PM, nicolas de loof
> <nicolas.deloof@...>wrote:
>
>    
>> My tomcat has mail.jar 1.2 in common/libbut this version allready defines
>> a public InternetAddress( String ) AFAIK.
>>
>>
>> On Tue, Mar 24, 2009 at 12:33 PM, Brett Porter<brett@...>  wrote:
>>
>>      
>>> I'm using 1.4.
>>>
>>>
>>> On 24/03/2009, at 10:25 PM, nicolas de loof wrote:
>>>
>>>   Archiva starts with a fresh new user database.
>>>        
>>>> But I can't create the admin :
>>>> java.lang.IllegalAccessError: tried to access method
>>>> javax.mail.internet.InternetAddress.<init>(Ljava/lang/String;Z)
>>>>
>>>> Seems my tomcat instance doesn't have the expected javamail version
>>>>
>>>>
>>>> On Tue, Mar 24, 2009 at 12:18 PM, nicolas de loof
>>>> <nicolas.deloof@...>wrote:
>>>>
>>>>   java.lang.OutOfMemoryError: PermGen space :-/
>>>>          
>>>>> Seems i've made too much start/stop tests - This time I will need some
>>>>> help
>>>>> from my system admin :)
>>>>>
>>>>> On Tue, Mar 24, 2009 at 12:10 PM, Brett Porter<brett@...>
>>>>> wrote:
>>>>>
>>>>>   Are you able to check if it works with a clean one? I did try the
>>>>>            
>>>>>> upgrade
>>>>>> earlier, but I wonder if anyone else is testing an upgrade from an
>>>>>> older
>>>>>> version?
>>>>>>
>>>>>> - Brett
>>>>>>
>>>>>>
>>>>>> On 24/03/2009, at 10:04 PM, nicolas de loof wrote:
>>>>>>
>>>>>> I'm sharing the database from my existing Archiva 1.1.1 instance
>>>>>>
>>>>>>              
>>>>>>> On Tue, Mar 24, 2009 at 12:03 PM, Brett Porter<brett@...>
>>>>>>> wrote:
>>>>>>>
>>>>>>> On 24/03/2009, at 9:49 PM, nicolas de loof wrote:
>>>>>>>
>>>>>>>                
>>>>>>>> This is fully repeatable, and the app is deployed on a private test
>>>>>>>>
>>>>>>>>   context
>>>>>>>>                  
>>>>>>>>> path, so no request is coming in yet.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>   Does the test set up have an existing users database or a clean
>>>>>>>>>                    
>>>>>>>> users
>>>>>>>> database?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Brett
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Brett Porter
>>>>>>>> brett@...
>>>>>>>> http://blogs.exist.com/bporter/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>   --
>>>>>>>>                  
>>>>>> Brett Porter
>>>>>> brett@...
>>>>>> http://blogs.exist.com/bporter/
>>>>>>
>>>>>>
>>>>>>
>>>>>>              
>>> --
>>> Brett Porter
>>> brett@...
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>>        
>
>