[VOTE] Release Archiva 1.2

[nicolas de loof-2]

No idea how my issue relates to this issue as I have no log to check. The
appserver.base property is set in my application.properties, and I've
patched the log4j.xml with absolute path, but still get no log.
I have no way to investigate on the deployment server as this is a corporate
one with restricted access ... Will have to keep using 1.1* for a while.
On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...> wrote:

> I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
> (ubuntu
> linux)
> I had the following error during startup though (even after I edited the
> log4j.xml file in the war to set the path to the logs):
>
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /logs/archiva-security-audit.log (No such
> file or directory)
>        at java.io.FileOutputStream.openAppend(Native Method)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>        at
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>        at
>
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
>        at
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
>        at
>
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
> ...
> log4j:ERROR Either File or DatePattern options are not set for appender
> [redbackAuditLog].
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /logs/archiva.log (No such file or
> directory)
>        at java.io.FileOutputStream.openAppend(Native Method)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>        at
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>        at
>
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> ...
>
> I was still able to access Archiva webapp even with the above errors..
> Could the problem you encountered be related to
> http://jira.codehaus.org/browse/MRM-1085 ?
>
> Thanks,
> Deng
>
> On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
> >wrote:
>
> > I'll try deploying the war on my end as well and see if i can get
> anything
> > out from the logs..
> >
> > -Deng
> >
> >
> > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
> nicolas.deloof@...
> > > wrote:
> >
> >> Works far better on my dev environment with wagon-ssh component.xml
> fixed
> >> ;)
> >>
> >> But still not starts / no log on my target server, that I can't remote
> >> debug
> >> :'(
> >>
> >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
> >> <nicolas.deloof@...>wrote:
> >>
> >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
> >> >
> >> >
> >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
> >> nicolas.deloof@...
> >> > > wrote:
> >> >
> >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I get
> >> >> console logs, but not really fine :
> >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
> >> >> ...
> >> >> Related cause:
> >> >> ClassNotFoundException:
> >> >> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
> >> >>
> >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...>
> >> wrote:
> >> >>
> >> >>> I had to step into the app with a debugger unfortunately to find the
> >> >>> below - do you have all of these set?
> >> >>>
> >> >>> - Brett
> >> >>>
> >> >>>
> >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
> >> >>>
> >> >>>  Right, I have changed the log4j.xml to use hard-coded path and set
> >> all
> >> >>>> loggers to "debug", but still fail starting Archiva and have no log
> >> in
> >> >>>> archiva.log :'(
> >> >>>>
> >> >>>> Seems to be the "something went wrong, let's see if you can guess
> the
> >> >>>> exception" case :)
> >> >>>>
> >> >>>>
> >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <brett@...>
> >> >>>> wrote:
> >> >>>>
> >> >>>>
> >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
> >> >>>>>
> >> >>>>> Did I miss something or was this allready required in 1.1.* ?
> >> >>>>>
> >> >>>>>> I can't remember having patched the standard war but it woks fine
> >> on
> >> >>>>>> my
> >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM system
> >> >>>>>> properties
> >> >>>>>> :(
> >> >>>>>>
> >> >>>>>>
> >> >>>>> It was, but only for logs.
> >> >>>>>
> >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
> >> >>>>>
> >> >>>>> All of the following are required (the JSW startup scripts set
> them
> >> in
> >> >>>>> standalone):
> >> >>>>>
> >> >>>>> * appserver.base set
> >> >>>>> * appserver.home set
> >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
> >> >>>>>
> >> >>>>> I've wanted to remove this for a while, but it fell off my
> radar...
> >> >>>>> I'll
> >> >>>>> see if there's a way to set it elsewhere than the command line.
> >> >>>>>
> >> >>>>> - Brett
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>> Brett Porter
> >> >>>>> brett@...
> >> >>>>> http://blogs.exist.com/bporter/
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>> --
> >> >>> 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
> >
>
>
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> www.exist.com | Innovation Delivered
>

[Deng Ching-2]

Ok, at least now we're getting the same behavior with the logs.. I had the
errors I posted earlier and no log files were generated even after I've set
them to to the absolute path in log4j.xml. (Will file a separate bug for
this if none exists yet). I'll try deploying the war to a tomcat server
running on windows as well and see if I can access the webapp.

Thanks,
Deng

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

> No idea how my issue relates to this issue as I have no log to check. The
> appserver.base property is set in my application.properties, and I've
> patched the log4j.xml with absolute path, but still get no log.
> I have no way to investigate on the deployment server as this is a
> corporate
> one with restricted access ... Will have to keep using 1.1* for a while.
> On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...>
> wrote:
>
> > I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
> > (ubuntu
> > linux)
> > I had the following error during startup though (even after I edited the
> > log4j.xml file in the war to set the path to the logs):
> >
> > log4j:ERROR setFile(null,true) call failed.
> > java.io.FileNotFoundException: /logs/archiva-security-audit.log (No such
> > file or directory)
> >        at java.io.FileOutputStream.openAppend(Native Method)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> >        at
> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> >        at
> >
> >
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> >        at
> > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
> >        at
> >
> >
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
> > ...
> > log4j:ERROR Either File or DatePattern options are not set for appender
> > [redbackAuditLog].
> > log4j:ERROR setFile(null,true) call failed.
> > java.io.FileNotFoundException: /logs/archiva.log (No such file or
> > directory)
> >        at java.io.FileOutputStream.openAppend(Native Method)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> >        at
> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> >        at
> >
> >
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> > ...
> >
> > I was still able to access Archiva webapp even with the above errors..
> > Could the problem you encountered be related to
> > http://jira.codehaus.org/browse/MRM-1085 ?
> >
> > Thanks,
> > Deng
> >
> > On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
> > >wrote:
> >
> > > I'll try deploying the war on my end as well and see if i can get
> > anything
> > > out from the logs..
> > >
> > > -Deng
> > >
> > >
> > > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
> > nicolas.deloof@...
> > > > wrote:
> > >
> > >> Works far better on my dev environment with wagon-ssh component.xml
> > fixed
> > >> ;)
> > >>
> > >> But still not starts / no log on my target server, that I can't remote
> > >> debug
> > >> :'(
> > >>
> > >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
> > >> <nicolas.deloof@...>wrote:
> > >>
> > >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
> > >> >
> > >> >
> > >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
> > >> nicolas.deloof@...
> > >> > > wrote:
> > >> >
> > >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I get
> > >> >> console logs, but not really fine :
> > >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
> > >> >> ...
> > >> >> Related cause:
> > >> >> ClassNotFoundException:
> > >> >>
> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
> > >> >>
> > >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...>
> > >> wrote:
> > >> >>
> > >> >>> I had to step into the app with a debugger unfortunately to find
> the
> > >> >>> below - do you have all of these set?
> > >> >>>
> > >> >>> - Brett
> > >> >>>
> > >> >>>
> > >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
> > >> >>>
> > >> >>>  Right, I have changed the log4j.xml to use hard-coded path and
> set
> > >> all
> > >> >>>> loggers to "debug", but still fail starting Archiva and have no
> log
> > >> in
> > >> >>>> archiva.log :'(
> > >> >>>>
> > >> >>>> Seems to be the "something went wrong, let's see if you can guess
> > the
> > >> >>>> exception" case :)
> > >> >>>>
> > >> >>>>
> > >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <brett@...
> >
> > >> >>>> wrote:
> > >> >>>>
> > >> >>>>
> > >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
> > >> >>>>>
> > >> >>>>> Did I miss something or was this allready required in 1.1.* ?
> > >> >>>>>
> > >> >>>>>> I can't remember having patched the standard war but it woks
> fine
> > >> on
> > >> >>>>>> my
> > >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM
> system
> > >> >>>>>> properties
> > >> >>>>>> :(
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>> It was, but only for logs.
> > >> >>>>>
> > >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
> > >> >>>>>
> > >> >>>>> All of the following are required (the JSW startup scripts set
> > them
> > >> in
> > >> >>>>> standalone):
> > >> >>>>>
> > >> >>>>> * appserver.base set
> > >> >>>>> * appserver.home set
> > >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
> > >> >>>>>
> > >> >>>>> I've wanted to remove this for a while, but it fell off my
> > radar...
> > >> >>>>> I'll
> > >> >>>>> see if there's a way to set it elsewhere than the command line.
> > >> >>>>>
> > >> >>>>> - Brett
> > >> >>>>>
> > >> >>>>>
> > >> >>>>> --
> > >> >>>>> Brett Porter
> > >> >>>>> brett@...
> > >> >>>>> http://blogs.exist.com/bporter/
> > >> >>>>>
> > >> >>>>>
> > >> >>>>>
> > >> >>> --
> > >> >>> 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
> > >
> >
> >
> >
> > --
> > Maria Odea Ching
> > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> > www.exist.com | Innovation Delivered
> >
>

--
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

[Emmanuel Venisse-2]

The logs directory isn't created automatically, so you must create it first.I
don't think it is good to use "/logs", /var/tomcat/logs or something else
would be better

Emmanuel

On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...> wrote:

> I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
> (ubuntu
> linux)
> I had the following error during startup though (even after I edited the
> log4j.xml file in the war to set the path to the logs):
>
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /logs/archiva-security-audit.log (No such
> file or directory)
>        at java.io.FileOutputStream.openAppend(Native Method)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>        at
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>        at
>
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
>        at
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
>        at
>
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
> ...
> log4j:ERROR Either File or DatePattern options are not set for appender
> [redbackAuditLog].
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: /logs/archiva.log (No such file or
> directory)
>        at java.io.FileOutputStream.openAppend(Native Method)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>        at
> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>        at
>
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> ...
>
> I was still able to access Archiva webapp even with the above errors..
> Could the problem you encountered be related to
> http://jira.codehaus.org/browse/MRM-1085 ?
>
> Thanks,
> Deng
>
> On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
> >wrote:
>
> > I'll try deploying the war on my end as well and see if i can get
> anything
> > out from the logs..
> >
> > -Deng
> >
> >
> > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
> nicolas.deloof@...
> > > wrote:
> >
> >> Works far better on my dev environment with wagon-ssh component.xml
> fixed
> >> ;)
> >>
> >> But still not starts / no log on my target server, that I can't remote
> >> debug
> >> :'(
> >>
> >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
> >> <nicolas.deloof@...>wrote:
> >>
> >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
> >> >
> >> >
> >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
> >> nicolas.deloof@...
> >> > > wrote:
> >> >
> >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I get
> >> >> console logs, but not really fine :
> >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
> >> >> ...
> >> >> Related cause:
> >> >> ClassNotFoundException:
> >> >> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
> >> >>
> >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...>
> >> wrote:
> >> >>
> >> >>> I had to step into the app with a debugger unfortunately to find the
> >> >>> below - do you have all of these set?
> >> >>>
> >> >>> - Brett
> >> >>>
> >> >>>
> >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
> >> >>>
> >> >>>  Right, I have changed the log4j.xml to use hard-coded path and set
> >> all
> >> >>>> loggers to "debug", but still fail starting Archiva and have no log
> >> in
> >> >>>> archiva.log :'(
> >> >>>>
> >> >>>> Seems to be the "something went wrong, let's see if you can guess
> the
> >> >>>> exception" case :)
> >> >>>>
> >> >>>>
> >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <brett@...>
> >> >>>> wrote:
> >> >>>>
> >> >>>>
> >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
> >> >>>>>
> >> >>>>> Did I miss something or was this allready required in 1.1.* ?
> >> >>>>>
> >> >>>>>> I can't remember having patched the standard war but it woks fine
> >> on
> >> >>>>>> my
> >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM system
> >> >>>>>> properties
> >> >>>>>> :(
> >> >>>>>>
> >> >>>>>>
> >> >>>>> It was, but only for logs.
> >> >>>>>
> >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
> >> >>>>>
> >> >>>>> All of the following are required (the JSW startup scripts set
> them
> >> in
> >> >>>>> standalone):
> >> >>>>>
> >> >>>>> * appserver.base set
> >> >>>>> * appserver.home set
> >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
> >> >>>>>
> >> >>>>> I've wanted to remove this for a while, but it fell off my
> radar...
> >> >>>>> I'll
> >> >>>>> see if there's a way to set it elsewhere than the command line.
> >> >>>>>
> >> >>>>> - Brett
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>> Brett Porter
> >> >>>>> brett@...
> >> >>>>> http://blogs.exist.com/bporter/
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>> --
> >> >>> 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
> >
>
>
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> www.exist.com | Innovation Delivered
>

[Ceki Gulcu]

Log4j version 1.2.12 and later will create the missing directories, if any.

Emmanuel Venisse wrote:
> The logs directory isn't created automatically, so you must create it first.I
> don't think it is good to use "/logs", /var/tomcat/logs or something else
> would be better
>
> Emmanuel
>

--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch

[Deng Ching-2]

The logs dir already exists in [TOMCAT_INSTALLATION]/logs. That was where I
pointed the archiva logs in log4j.xml but when I started up the server, it
was still looking in the /logs dir and not in [TOMCAT_INSTALLATION]/logs
where I pointed it to..

-Deng

On Tue, Mar 24, 2009 at 12:36 AM, Emmanuel Venisse <
emmanuel.venisse@...> wrote:

> The logs directory isn't created automatically, so you must create it
> first.I
> don't think it is good to use "/logs", /var/tomcat/logs or something else
> would be better
>
> Emmanuel
>
> On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...>
> wrote:
>
> > I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
> > (ubuntu
> > linux)
> > I had the following error during startup though (even after I edited the
> > log4j.xml file in the war to set the path to the logs):
> >
> > log4j:ERROR setFile(null,true) call failed.
> > java.io.FileNotFoundException: /logs/archiva-security-audit.log (No such
> > file or directory)
> >        at java.io.FileOutputStream.openAppend(Native Method)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> >        at
> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> >        at
> >
> >
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> >        at
> > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
> >        at
> >
> >
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
> > ...
> > log4j:ERROR Either File or DatePattern options are not set for appender
> > [redbackAuditLog].
> > log4j:ERROR setFile(null,true) call failed.
> > java.io.FileNotFoundException: /logs/archiva.log (No such file or
> > directory)
> >        at java.io.FileOutputStream.openAppend(Native Method)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> >        at
> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> >        at
> >
> >
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> > ...
> >
> > I was still able to access Archiva webapp even with the above errors..
> > Could the problem you encountered be related to
> > http://jira.codehaus.org/browse/MRM-1085 ?
> >
> > Thanks,
> > Deng
> >
> > On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
> > >wrote:
> >
> > > I'll try deploying the war on my end as well and see if i can get
> > anything
> > > out from the logs..
> > >
> > > -Deng
> > >
> > >
> > > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
> > nicolas.deloof@...
> > > > wrote:
> > >
> > >> Works far better on my dev environment with wagon-ssh component.xml
> > fixed
> > >> ;)
> > >>
> > >> But still not starts / no log on my target server, that I can't remote
> > >> debug
> > >> :'(
> > >>
> > >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
> > >> <nicolas.deloof@...>wrote:
> > >>
> > >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
> > >> >
> > >> >
> > >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
> > >> nicolas.deloof@...
> > >> > > wrote:
> > >> >
> > >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I get
> > >> >> console logs, but not really fine :
> > >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
> > >> >> ...
> > >> >> Related cause:
> > >> >> ClassNotFoundException:
> > >> >>
> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
> > >> >>
> > >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...>
> > >> wrote:
> > >> >>
> > >> >>> I had to step into the app with a debugger unfortunately to find
> the
> > >> >>> below - do you have all of these set?
> > >> >>>
> > >> >>> - Brett
> > >> >>>
> > >> >>>
> > >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
> > >> >>>
> > >> >>>  Right, I have changed the log4j.xml to use hard-coded path and
> set
> > >> all
> > >> >>>> loggers to "debug", but still fail starting Archiva and have no
> log
> > >> in
> > >> >>>> archiva.log :'(
> > >> >>>>
> > >> >>>> Seems to be the "something went wrong, let's see if you can guess
> > the
> > >> >>>> exception" case :)
> > >> >>>>
> > >> >>>>
> > >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <brett@...
> >
> > >> >>>> wrote:
> > >> >>>>
> > >> >>>>
> > >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
> > >> >>>>>
> > >> >>>>> Did I miss something or was this allready required in 1.1.* ?
> > >> >>>>>
> > >> >>>>>> I can't remember having patched the standard war but it woks
> fine
> > >> on
> > >> >>>>>> my
> > >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM
> system
> > >> >>>>>> properties
> > >> >>>>>> :(
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>> It was, but only for logs.
> > >> >>>>>
> > >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
> > >> >>>>>
> > >> >>>>> All of the following are required (the JSW startup scripts set
> > them
> > >> in
> > >> >>>>> standalone):
> > >> >>>>>
> > >> >>>>> * appserver.base set
> > >> >>>>> * appserver.home set
> > >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
> > >> >>>>>
> > >> >>>>> I've wanted to remove this for a while, but it fell off my
> > radar...
> > >> >>>>> I'll
> > >> >>>>> see if there's a way to set it elsewhere than the command line.
> > >> >>>>>
> > >> >>>>> - Brett
> > >> >>>>>
> > >> >>>>>
> > >> >>>>> --
> > >> >>>>> Brett Porter
> > >> >>>>> brett@...
> > >> >>>>> http://blogs.exist.com/bporter/
> > >> >>>>>
> > >> >>>>>
> > >> >>>>>
> > >> >>> --
> > >> >>> 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
> > >
> >
> >
> >
> > --
> > Maria Odea Ching
> > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> > www.exist.com | Innovation Delivered
> >
>

--
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

[Shi Yusen]

Mmm, I forgot to copy xalan.jar and serializer.jar to WEB-INF/lib/. Now
Archiva 1.2 works. As a newcomer, I'm curious why you don't put these
jars into the war file. And in 1.1.3, if no these jars, I can see error
messages in tomcat log. In 1.2, no any output to complain this error.

Regards,

Shi Yusen/Beijing Langhua Ltd.

在 2009-03-24二的 00:35 +0800，Maria Odea Ching写道：

> Ok, at least now we're getting the same behavior with the logs.. I had the
> errors I posted earlier and no log files were generated even after I've set
> them to to the absolute path in log4j.xml. (Will file a separate bug for
> this if none exists yet). I'll try deploying the war to a tomcat server
> running on windows as well and see if I can access the webapp.
>
> Thanks,
> Deng
>
> On Tue, Mar 24, 2009 at 12:26 AM, nicolas de loof
> <nicolas.deloof@...>wrote:
>
> > No idea how my issue relates to this issue as I have no log to check. The
> > appserver.base property is set in my application.properties, and I've
> > patched the log4j.xml with absolute path, but still get no log.
> > I have no way to investigate on the deployment server as this is a
> > corporate
> > one with restricted access ... Will have to keep using 1.1* for a while.
> > On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...>
> > wrote:
> >
> > > I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
> > > (ubuntu
> > > linux)
> > > I had the following error during startup though (even after I edited the
> > > log4j.xml file in the war to set the path to the logs):
> > >
> > > log4j:ERROR setFile(null,true) call failed.
> > > java.io.FileNotFoundException: /logs/archiva-security-audit.log (No such
> > > file or directory)
> > >        at java.io.FileOutputStream.openAppend(Native Method)
> > >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> > >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> > >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> > >        at
> > > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> > >        at
> > >
> > >
> > org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> > >        at
> > > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
> > >        at
> > >
> > >
> > org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
> > > ...
> > > log4j:ERROR Either File or DatePattern options are not set for appender
> > > [redbackAuditLog].
> > > log4j:ERROR setFile(null,true) call failed.
> > > java.io.FileNotFoundException: /logs/archiva.log (No such file or
> > > directory)
> > >        at java.io.FileOutputStream.openAppend(Native Method)
> > >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> > >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> > >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> > >        at
> > > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> > >        at
> > >
> > >
> > org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> > > ...
> > >
> > > I was still able to access Archiva webapp even with the above errors..
> > > Could the problem you encountered be related to
> > > http://jira.codehaus.org/browse/MRM-1085 ?
> > >
> > > Thanks,
> > > Deng
> > >
> > > On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
> > > >wrote:
> > >
> > > > I'll try deploying the war on my end as well and see if i can get
> > > anything
> > > > out from the logs..
> > > >
> > > > -Deng
> > > >
> > > >
> > > > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
> > > nicolas.deloof@...
> > > > > wrote:
> > > >
> > > >> Works far better on my dev environment with wagon-ssh component.xml
> > > fixed
> > > >> ;)
> > > >>
> > > >> But still not starts / no log on my target server, that I can't remote
> > > >> debug
> > > >> :'(
> > > >>
> > > >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
> > > >> <nicolas.deloof@...>wrote:
> > > >>
> > > >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
> > > >> >
> > > >> >
> > > >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
> > > >> nicolas.deloof@...
> > > >> > > wrote:
> > > >> >
> > > >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I get
> > > >> >> console logs, but not really fine :
> > > >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
> > > >> >> ...
> > > >> >> Related cause:
> > > >> >> ClassNotFoundException:
> > > >> >>
> > org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
> > > >> >>
> > > >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...>
> > > >> wrote:
> > > >> >>
> > > >> >>> I had to step into the app with a debugger unfortunately to find
> > the
> > > >> >>> below - do you have all of these set?
> > > >> >>>
> > > >> >>> - Brett
> > > >> >>>
> > > >> >>>
> > > >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
> > > >> >>>
> > > >> >>>  Right, I have changed the log4j.xml to use hard-coded path and
> > set
> > > >> all
> > > >> >>>> loggers to "debug", but still fail starting Archiva and have no
> > log
> > > >> in
> > > >> >>>> archiva.log :'(
> > > >> >>>>
> > > >> >>>> Seems to be the "something went wrong, let's see if you can guess
> > > the
> > > >> >>>> exception" case :)
> > > >> >>>>
> > > >> >>>>
> > > >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <brett@...
> > >
> > > >> >>>> wrote:
> > > >> >>>>
> > > >> >>>>
> > > >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
> > > >> >>>>>
> > > >> >>>>> Did I miss something or was this allready required in 1.1.* ?
> > > >> >>>>>
> > > >> >>>>>> I can't remember having patched the standard war but it woks
> > fine
> > > >> on
> > > >> >>>>>> my
> > > >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM
> > system
> > > >> >>>>>> properties
> > > >> >>>>>> :(
> > > >> >>>>>>
> > > >> >>>>>>
> > > >> >>>>> It was, but only for logs.
> > > >> >>>>>
> > > >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
> > > >> >>>>>
> > > >> >>>>> All of the following are required (the JSW startup scripts set
> > > them
> > > >> in
> > > >> >>>>> standalone):
> > > >> >>>>>
> > > >> >>>>> * appserver.base set
> > > >> >>>>> * appserver.home set
> > > >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
> > > >> >>>>>
> > > >> >>>>> I've wanted to remove this for a while, but it fell off my
> > > radar...
> > > >> >>>>> I'll
> > > >> >>>>> see if there's a way to set it elsewhere than the command line.
> > > >> >>>>>
> > > >> >>>>> - Brett
> > > >> >>>>>
> > > >> >>>>>
> > > >> >>>>> --
> > > >> >>>>> Brett Porter
> > > >> >>>>> brett@...
> > > >> >>>>> http://blogs.exist.com/bporter/
> > > >> >>>>>
> > > >> >>>>>
> > > >> >>>>>
> > > >> >>> --
> > > >> >>> 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
> > > >
> > >
> > >
> > >
> > > --
> > > Maria Odea Ching
> > > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> > > www.exist.com | Innovation Delivered
> > >
> >
>
>
>

[Deng Ching-2]

Sorry, my bad.. (too little sleep)
I just changed the log4j.xml in the archiva war itself and didn't change the
path to the unpacked war in tomcat's webapps directory. That was why it was
still looking at the /logs/ dir. The errors went away now :D

-Deng

On Tue, Mar 24, 2009 at 12:50 AM, Maria Odea Ching <oching@...>wrote:

> The logs dir already exists in [TOMCAT_INSTALLATION]/logs. That was where I
> pointed the archiva logs in log4j.xml but when I started up the server, it
> was still looking in the /logs dir and not in [TOMCAT_INSTALLATION]/logs
> where I pointed it to..
>
> -Deng
>
>
> On Tue, Mar 24, 2009 at 12:36 AM, Emmanuel Venisse <
> emmanuel.venisse@...> wrote:
>
>> The logs directory isn't created automatically, so you must create it
>> first.I
>> don't think it is good to use "/logs", /var/tomcat/logs or something else
>> would be better
>>
>> Emmanuel
>>
>> On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...>
>> wrote:
>>
>> > I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
>> > (ubuntu
>> > linux)
>> > I had the following error during startup though (even after I edited the
>> > log4j.xml file in the war to set the path to the logs):
>> >
>> > log4j:ERROR setFile(null,true) call failed.
>> > java.io.FileNotFoundException: /logs/archiva-security-audit.log (No such
>> > file or directory)
>> >        at java.io.FileOutputStream.openAppend(Native Method)
>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>> >        at
>> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>> >        at
>> >
>> >
>> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
>> >        at
>> > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
>> >        at
>> >
>> >
>> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
>> > ...
>> > log4j:ERROR Either File or DatePattern options are not set for appender
>> > [redbackAuditLog].
>> > log4j:ERROR setFile(null,true) call failed.
>> > java.io.FileNotFoundException: /logs/archiva.log (No such file or
>> > directory)
>> >        at java.io.FileOutputStream.openAppend(Native Method)
>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>> >        at
>> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>> >        at
>> >
>> >
>> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
>> > ...
>> >
>> > I was still able to access Archiva webapp even with the above errors..
>> > Could the problem you encountered be related to
>> > http://jira.codehaus.org/browse/MRM-1085 ?
>> >
>> > Thanks,
>> > Deng
>> >
>> > On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
>> > >wrote:
>> >
>> > > I'll try deploying the war on my end as well and see if i can get
>> > anything
>> > > out from the logs..
>> > >
>> > > -Deng
>> > >
>> > >
>> > > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
>> > nicolas.deloof@...
>> > > > wrote:
>> > >
>> > >> Works far better on my dev environment with wagon-ssh component.xml
>> > fixed
>> > >> ;)
>> > >>
>> > >> But still not starts / no log on my target server, that I can't
>> remote
>> > >> debug
>> > >> :'(
>> > >>
>> > >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
>> > >> <nicolas.deloof@...>wrote:
>> > >>
>> > >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
>> > >> >
>> > >> >
>> > >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
>> > >> nicolas.deloof@...
>> > >> > > wrote:
>> > >> >
>> > >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I
>> get
>> > >> >> console logs, but not really fine :
>> > >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
>> > >> >> ...
>> > >> >> Related cause:
>> > >> >> ClassNotFoundException:
>> > >> >>
>> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
>> > >> >>
>> > >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...>
>> > >> wrote:
>> > >> >>
>> > >> >>> I had to step into the app with a debugger unfortunately to find
>> the
>> > >> >>> below - do you have all of these set?
>> > >> >>>
>> > >> >>> - Brett
>> > >> >>>
>> > >> >>>
>> > >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
>> > >> >>>
>> > >> >>>  Right, I have changed the log4j.xml to use hard-coded path and
>> set
>> > >> all
>> > >> >>>> loggers to "debug", but still fail starting Archiva and have no
>> log
>> > >> in
>> > >> >>>> archiva.log :'(
>> > >> >>>>
>> > >> >>>> Seems to be the "something went wrong, let's see if you can
>> guess
>> > the
>> > >> >>>> exception" case :)
>> > >> >>>>
>> > >> >>>>
>> > >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <
>> brett@...>
>> > >> >>>> wrote:
>> > >> >>>>
>> > >> >>>>
>> > >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
>> > >> >>>>>
>> > >> >>>>> Did I miss something or was this allready required in 1.1.* ?
>> > >> >>>>>
>> > >> >>>>>> I can't remember having patched the standard war but it woks
>> fine
>> > >> on
>> > >> >>>>>> my
>> > >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM
>> system
>> > >> >>>>>> properties
>> > >> >>>>>> :(
>> > >> >>>>>>
>> > >> >>>>>>
>> > >> >>>>> It was, but only for logs.
>> > >> >>>>>
>> > >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
>> > >> >>>>>
>> > >> >>>>> All of the following are required (the JSW startup scripts set
>> > them
>> > >> in
>> > >> >>>>> standalone):
>> > >> >>>>>
>> > >> >>>>> * appserver.base set
>> > >> >>>>> * appserver.home set
>> > >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
>> > >> >>>>>
>> > >> >>>>> I've wanted to remove this for a while, but it fell off my
>> > radar...
>> > >> >>>>> I'll
>> > >> >>>>> see if there's a way to set it elsewhere than the command line.
>> > >> >>>>>
>> > >> >>>>> - Brett
>> > >> >>>>>
>> > >> >>>>>
>> > >> >>>>> --
>> > >> >>>>> Brett Porter
>> > >> >>>>> brett@...
>> > >> >>>>> http://blogs.exist.com/bporter/
>> > >> >>>>>
>> > >> >>>>>
>> > >> >>>>>
>> > >> >>> --
>> > >> >>> 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
>> > >
>> >
>> >
>> >
>> > --
>> > Maria Odea Ching
>> > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>> > www.exist.com | Innovation Delivered
>> >
>>
>
>
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> www.exist.com | Innovation Delivered
>

--
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

[Deng Ching-2]

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

On Tue, Mar 24, 2009 at 1:03 AM, Maria Odea Ching <oching@...> wrote:

> Sorry, my bad.. (too little sleep)
> I just changed the log4j.xml in the archiva war itself and didn't change
> the path to the unpacked war in tomcat's webapps directory. That was why it
> was still looking at the /logs/ dir. The errors went away now :D
>
> -Deng
>
>
> On Tue, Mar 24, 2009 at 12:50 AM, Maria Odea Ching <oching@...>wrote:
>
>> The logs dir already exists in [TOMCAT_INSTALLATION]/logs. That was where
>> I pointed the archiva logs in log4j.xml but when I started up the server, it
>> was still looking in the /logs dir and not in [TOMCAT_INSTALLATION]/logs
>> where I pointed it to..
>>
>> -Deng
>>
>>
>> On Tue, Mar 24, 2009 at 12:36 AM, Emmanuel Venisse <
>> emmanuel.venisse@...> wrote:
>>
>>> The logs directory isn't created automatically, so you must create it
>>> first.I
>>> don't think it is good to use "/logs", /var/tomcat/logs or something else
>>> would be better
>>>
>>> Emmanuel
>>>
>>> On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...>
>>> wrote:
>>>
>>> > I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
>>> > (ubuntu
>>> > linux)
>>> > I had the following error during startup though (even after I edited
>>> the
>>> > log4j.xml file in the war to set the path to the logs):
>>> >
>>> > log4j:ERROR setFile(null,true) call failed.
>>> > java.io.FileNotFoundException: /logs/archiva-security-audit.log (No
>>> such
>>> > file or directory)
>>> >        at java.io.FileOutputStream.openAppend(Native Method)
>>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>>> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>>> >        at
>>> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>>> >        at
>>> >
>>> >
>>> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
>>> >        at
>>> >
>>> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
>>> >        at
>>> >
>>> >
>>> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
>>> > ...
>>> > log4j:ERROR Either File or DatePattern options are not set for appender
>>> > [redbackAuditLog].
>>> > log4j:ERROR setFile(null,true) call failed.
>>> > java.io.FileNotFoundException: /logs/archiva.log (No such file or
>>> > directory)
>>> >        at java.io.FileOutputStream.openAppend(Native Method)
>>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
>>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
>>> >        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
>>> >        at
>>> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
>>> >        at
>>> >
>>> >
>>> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
>>> > ...
>>> >
>>> > I was still able to access Archiva webapp even with the above errors..
>>> > Could the problem you encountered be related to
>>> > http://jira.codehaus.org/browse/MRM-1085 ?
>>> >
>>> > Thanks,
>>> > Deng
>>> >
>>> > On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <oching@...
>>> > >wrote:
>>> >
>>> > > I'll try deploying the war on my end as well and see if i can get
>>> > anything
>>> > > out from the logs..
>>> > >
>>> > > -Deng
>>> > >
>>> > >
>>> > > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
>>> > nicolas.deloof@...
>>> > > > wrote:
>>> > >
>>> > >> Works far better on my dev environment with wagon-ssh component.xml
>>> > fixed
>>> > >> ;)
>>> > >>
>>> > >> But still not starts / no log on my target server, that I can't
>>> remote
>>> > >> debug
>>> > >> :'(
>>> > >>
>>> > >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
>>> > >> <nicolas.deloof@...>wrote:
>>> > >>
>>> > >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
>>> > >> >
>>> > >> >
>>> > >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
>>> > >> nicolas.deloof@...
>>> > >> > > wrote:
>>> > >> >
>>> > >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I
>>> get
>>> > >> >> console logs, but not really fine :
>>> > >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
>>> > >> >> ...
>>> > >> >> Related cause:
>>> > >> >> ClassNotFoundException:
>>> > >> >>
>>> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
>>> > >> >>
>>> > >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
>>> > >> >>
>>> > >> >>
>>> > >> >>
>>> > >> >>
>>> > >> >>
>>> > >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <brett@...
>>> >
>>> > >> wrote:
>>> > >> >>
>>> > >> >>> I had to step into the app with a debugger unfortunately to find
>>> the
>>> > >> >>> below - do you have all of these set?
>>> > >> >>>
>>> > >> >>> - Brett
>>> > >> >>>
>>> > >> >>>
>>> > >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
>>> > >> >>>
>>> > >> >>>  Right, I have changed the log4j.xml to use hard-coded path and
>>> set
>>> > >> all
>>> > >> >>>> loggers to "debug", but still fail starting Archiva and have no
>>> log
>>> > >> in
>>> > >> >>>> archiva.log :'(
>>> > >> >>>>
>>> > >> >>>> Seems to be the "something went wrong, let's see if you can
>>> guess
>>> > the
>>> > >> >>>> exception" case :)
>>> > >> >>>>
>>> > >> >>>>
>>> > >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <
>>> brett@...>
>>> > >> >>>> wrote:
>>> > >> >>>>
>>> > >> >>>>
>>> > >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
>>> > >> >>>>>
>>> > >> >>>>> Did I miss something or was this allready required in 1.1.* ?
>>> > >> >>>>>
>>> > >> >>>>>> I can't remember having patched the standard war but it woks
>>> fine
>>> > >> on
>>> > >> >>>>>> my
>>> > >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM
>>> system
>>> > >> >>>>>> properties
>>> > >> >>>>>> :(
>>> > >> >>>>>>
>>> > >> >>>>>>
>>> > >> >>>>> It was, but only for logs.
>>> > >> >>>>>
>>> > >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
>>> > >> >>>>>
>>> > >> >>>>> All of the following are required (the JSW startup scripts set
>>> > them
>>> > >> in
>>> > >> >>>>> standalone):
>>> > >> >>>>>
>>> > >> >>>>> * appserver.base set
>>> > >> >>>>> * appserver.home set
>>> > >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
>>> > >> >>>>>
>>> > >> >>>>> I've wanted to remove this for a while, but it fell off my
>>> > radar...
>>> > >> >>>>> I'll
>>> > >> >>>>> see if there's a way to set it elsewhere than the command
>>> line.
>>> > >> >>>>>
>>> > >> >>>>> - Brett
>>> > >> >>>>>
>>> > >> >>>>>
>>> > >> >>>>> --
>>> > >> >>>>> Brett Porter
>>> > >> >>>>> brett@...
>>> > >> >>>>> http://blogs.exist.com/bporter/
>>> > >> >>>>>
>>> > >> >>>>>
>>> > >> >>>>>
>>> > >> >>> --
>>> > >> >>> 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
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Maria Odea Ching
>>> > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>>> > www.exist.com | Innovation Delivered
>>> >
>>>
>>
>>
>>
>> --
>> Maria Odea Ching
>> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
>> www.exist.com | Innovation Delivered
>>
>
>
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> www.exist.com | Innovation Delivered
>

--
Maria Odea Ching
Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
www.exist.com | Innovation Delivered

[nicolas de loof-2]

I'm happy not beeing alone in the dark anymore ;)
On Mon, Mar 23, 2009 at 6:24 PM, Maria Odea Ching <oching@...> 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
>
> On Tue, Mar 24, 2009 at 1:03 AM, Maria Odea Ching <oching@...>
> wrote:
>
> > Sorry, my bad.. (too little sleep)
> > I just changed the log4j.xml in the archiva war itself and didn't change
> > the path to the unpacked war in tomcat's webapps directory. That was why
> it
> > was still looking at the /logs/ dir. The errors went away now :D
> >
> > -Deng
> >
> >
> > On Tue, Mar 24, 2009 at 12:50 AM, Maria Odea Ching <oching@...
> >wrote:
> >
> >> The logs dir already exists in [TOMCAT_INSTALLATION]/logs. That was
> where
> >> I pointed the archiva logs in log4j.xml but when I started up the
> server, it
> >> was still looking in the /logs dir and not in [TOMCAT_INSTALLATION]/logs
> >> where I pointed it to..
> >>
> >> -Deng
> >>
> >>
> >> On Tue, Mar 24, 2009 at 12:36 AM, Emmanuel Venisse <
> >> emmanuel.venisse@...> wrote:
> >>
> >>> The logs directory isn't created automatically, so you must create it
> >>> first.I
> >>> don't think it is good to use "/logs", /var/tomcat/logs or something
> else
> >>> would be better
> >>>
> >>> Emmanuel
> >>>
> >>> On Mon, Mar 23, 2009 at 5:14 PM, Maria Odea Ching <oching@...>
> >>> wrote:
> >>>
> >>> > I was able to deploy and access the archiva 1.2 war in tomcat 5.5.17
> >>> > (ubuntu
> >>> > linux)
> >>> > I had the following error during startup though (even after I edited
> >>> the
> >>> > log4j.xml file in the war to set the path to the logs):
> >>> >
> >>> > log4j:ERROR setFile(null,true) call failed.
> >>> > java.io.FileNotFoundException: /logs/archiva-security-audit.log (No
> >>> such
> >>> > file or directory)
> >>> >        at java.io.FileOutputStream.openAppend(Native Method)
> >>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> >>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> >>> >        at
> org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> >>> >        at
> >>> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> >>> >        at
> >>> >
> >>> >
> >>>
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> >>> >        at
> >>> >
> >>>
> org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
> >>> >        at
> >>> >
> >>> >
> >>>
> org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:220)
> >>> > ...
> >>> > log4j:ERROR Either File or DatePattern options are not set for
> appender
> >>> > [redbackAuditLog].
> >>> > log4j:ERROR setFile(null,true) call failed.
> >>> > java.io.FileNotFoundException: /logs/archiva.log (No such file or
> >>> > directory)
> >>> >        at java.io.FileOutputStream.openAppend(Native Method)
> >>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
> >>> >        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> >>> >        at
> org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
> >>> >        at
> >>> > org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
> >>> >        at
> >>> >
> >>> >
> >>>
> org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:215)
> >>> > ...
> >>> >
> >>> > I was still able to access Archiva webapp even with the above
> errors..
> >>> > Could the problem you encountered be related to
> >>> > http://jira.codehaus.org/browse/MRM-1085 ?
> >>> >
> >>> > Thanks,
> >>> > Deng
> >>> >
> >>> > On Mon, Mar 23, 2009 at 11:25 PM, Maria Odea Ching <
> oching@...
> >>> > >wrote:
> >>> >
> >>> > > I'll try deploying the war on my end as well and see if i can get
> >>> > anything
> >>> > > out from the logs..
> >>> > >
> >>> > > -Deng
> >>> > >
> >>> > >
> >>> > > On Mon, Mar 23, 2009 at 9:01 PM, nicolas de loof <
> >>> > nicolas.deloof@...
> >>> > > > wrote:
> >>> > >
> >>> > >> Works far better on my dev environment with wagon-ssh
> component.xml
> >>> > fixed
> >>> > >> ;)
> >>> > >>
> >>> > >> But still not starts / no log on my target server, that I can't
> >>> remote
> >>> > >> debug
> >>> > >> :'(
> >>> > >>
> >>> > >> On Mon, Mar 23, 2009 at 1:43 PM, nicolas de loof
> >>> > >> <nicolas.deloof@...>wrote:
> >>> > >>
> >>> > >> > Hey, the class is "NullKnownHostProvider", with singular "Host"
> >>> > >> >
> >>> > >> >
> >>> > >> > On Mon, Mar 23, 2009 at 1:39 PM, nicolas de loof <
> >>> > >> nicolas.deloof@...
> >>> > >> > > wrote:
> >>> > >> >
> >>> > >> >> Trying to run archiva 1.2 on my local dev Tomcat is better as I
> >>> get
> >>> > >> >> console logs, but not really fine :
> >>> > >> >> ClassNotFoundException: org.apache.maven.project.ModelResolver
> >>> > >> >> ...
> >>> > >> >> Related cause:
> >>> > >> >> ClassNotFoundException:
> >>> > >> >>
> >>> org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider
> >>> > >> >>
> >>> > >> >> (but wagon-ssh-common is in WEB-NF/lib ???)
> >>> > >> >>
> >>> > >> >>
> >>> > >> >>
> >>> > >> >>
> >>> > >> >>
> >>> > >> >> On Mon, Mar 23, 2009 at 12:51 PM, Brett Porter <
> brett@...
> >>> >
> >>> > >> wrote:
> >>> > >> >>
> >>> > >> >>> I had to step into the app with a debugger unfortunately to
> find
> >>> the
> >>> > >> >>> below - do you have all of these set?
> >>> > >> >>>
> >>> > >> >>> - Brett
> >>> > >> >>>
> >>> > >> >>>
> >>> > >> >>> On 23/03/2009, at 10:36 PM, nicolas de loof wrote:
> >>> > >> >>>
> >>> > >> >>>  Right, I have changed the log4j.xml to use hard-coded path
> and
> >>> set
> >>> > >> all
> >>> > >> >>>> loggers to "debug", but still fail starting Archiva and have
> no
> >>> log
> >>> > >> in
> >>> > >> >>>> archiva.log :'(
> >>> > >> >>>>
> >>> > >> >>>> Seems to be the "something went wrong, let's see if you can
> >>> guess
> >>> > the
> >>> > >> >>>> exception" case :)
> >>> > >> >>>>
> >>> > >> >>>>
> >>> > >> >>>> On Mon, Mar 23, 2009 at 12:27 PM, Brett Porter <
> >>> brett@...>
> >>> > >> >>>> wrote:
> >>> > >> >>>>
> >>> > >> >>>>
> >>> > >> >>>>> On 23/03/2009, at 10:15 PM, nicolas de loof wrote:
> >>> > >> >>>>>
> >>> > >> >>>>> Did I miss something or was this allready required in 1.1.*
> ?
> >>> > >> >>>>>
> >>> > >> >>>>>> I can't remember having patched the standard war but it
> woks
> >>> fine
> >>> > >> on
> >>> > >> >>>>>> my
> >>> > >> >>>>>> tomcat. Beeing a shared instance I can't setup custom JVM
> >>> system
> >>> > >> >>>>>> properties
> >>> > >> >>>>>> :(
> >>> > >> >>>>>>
> >>> > >> >>>>>>
> >>> > >> >>>>> It was, but only for logs.
> >>> > >> >>>>>
> >>> > >> >>>>> http://archiva.apache.org/docs/1.1.3/adminguide/webapp.html
> >>> > >> >>>>>
> >>> > >> >>>>> All of the following are required (the JSW startup scripts
> set
> >>> > them
> >>> > >> in
> >>> > >> >>>>> standalone):
> >>> > >> >>>>>
> >>> > >> >>>>> * appserver.base set
> >>> > >> >>>>> * appserver.home set
> >>> > >> >>>>> * activation.jar and mail.jar in tomcat's common/lib
> >>> > >> >>>>>
> >>> > >> >>>>> I've wanted to remove this for a while, but it fell off my
> >>> > radar...
> >>> > >> >>>>> I'll
> >>> > >> >>>>> see if there's a way to set it elsewhere than the command
> >>> line.
> >>> > >> >>>>>
> >>> > >> >>>>> - Brett
> >>> > >> >>>>>
> >>> > >> >>>>>
> >>> > >> >>>>> --
> >>> > >> >>>>> Brett Porter
> >>> > >> >>>>> brett@...
> >>> > >> >>>>> http://blogs.exist.com/bporter/
> >>> > >> >>>>>
> >>> > >> >>>>>
> >>> > >> >>>>>
> >>> > >> >>> --
> >>> > >> >>> 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
> >>> > >
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Maria Odea Ching
> >>> > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching
> |
> >>> > www.exist.com | Innovation Delivered
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> Maria Odea Ching
> >> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> >> www.exist.com | Innovation Delivered
> >>
> >
> >
> >
> > --
> > Maria Odea Ching
> > Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> > www.exist.com | Innovation Delivered
> >
>
>
>
> --
> Maria Odea Ching
> Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching |
> www.exist.com | Innovation Delivered
>

[brettporter]

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/

[brettporter]

On 24/03/2009, at 3:50 AM, Shi Yusen wrote:

> Mmm, I forgot to copy xalan.jar and serializer.jar to WEB-INF/lib/.  
> Now
> Archiva 1.2 works. As a newcomer, I'm curious why you don't put these
> jars into the war file. And in 1.1.3, if no these jars, I can see  
> error
> messages in tomcat log. In 1.2, no any output to complain this error.

I've never encountered the need to add those - I thought they were  
both in the JDK?

Cheers,
Brett

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

[Shi Yusen]

I should miss Sun JDK if so :). I guess they were removed from OpenJDK
because of Apache License 2.0. Correct me if I'm wrong.

Anyway, Archiva 1.2 is great.

Another question, is there any plan to change the web page encoding
from iso-8859-1 to utf-8? In iso-8859-1, CJK charactors cannot be
displayed.

Kind Regards,

Shi Yusen/Beijing Langhua Ltd.


在 2009-03-24二的 10:30 +1100，Brett Porter写道：

> On 24/03/2009, at 3:50 AM, Shi Yusen wrote:
>
> > Mmm, I forgot to copy xalan.jar and serializer.jar to WEB-INF/lib/.  
> > Now
> > Archiva 1.2 works. As a newcomer, I'm curious why you don't put these
> > jars into the war file. And in 1.1.3, if no these jars, I can see  
> > error
> > messages in tomcat log. In 1.2, no any output to complain this error.
>
> I've never encountered the need to add those - I thought they were  
> both in the JDK?
>
> Cheers,
> Brett
>
> --
> Brett Porter
> brett@...
> http://blogs.exist.com/bporter/
>

[brettporter]

On 24/03/2009, at 4:37 PM, Shi Yusen wrote:

> I should miss Sun JDK if so :). I guess they were removed from OpenJDK
> because of Apache License 2.0. Correct me if I'm wrong.

Thanks - if you would like help fixing the issue on OpenJDK we can  
work through that separately.

>
> Anyway, Archiva 1.2 is great.
>
> Another question, is there any plan to change the web page encoding
> from iso-8859-1 to utf-8? In iso-8859-1, CJK charactors cannot be
> displayed.

It is in JIRA already, hopefully someone will push that through for  
the next release.

Thanks for testing!

- Brett

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

[Shi Yusen]

> 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)."

> 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.

Cheers,

Shi Yusen/Beijing Langhua Ltd.

[brettporter]

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/

[nicolas de loof-2]

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/
>
>

[Deng Ching-2]

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 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]

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
>>
>
>

[Shi Yusen]

+1

Our archiva is online now:
http://maven2.langhua.org/
http://maven2.langhua.org/public/

Fedora 9 + OpenJDK 1.6.0 + Apache 2.2.x + Tomcat 5.5.x + MySQL 5.0.x +
OpenLDAP 2.4.x, and of course, the Archiva 1.2.

Cheers,

Shi Yusen/Beijing Langhua Ltd.

在 2009-03-24二的 15:52 +0800，Maria Odea Ching写道：

> 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/
> >
> >
>
>