Nabble - Continuum - Users

RE: Problem with multi module maven project

2009-12-15T02:03:41Z

Thank you! I agree. We will look into it.

Geir

-----Original Message-----
From: Brent Atkinson [mailto:batkinson@...]
Sent: 11. desember 2009 16:11
To: users@...
Subject: Re: Problem with multi module maven project

Gier,

I'd take Emmanuel's recommendation seriously if you're wanting the project to be manageable and work with the conventional tools. It may work this way, but you will have to fight against the tools where you wouldn't have to otherwise.

Brent

>>> Emmanuel Venisse 12/10/09 8:43 AM >>>
It's a bad practice to use a file that is stored under an other project.

The best practice is to create a module that store shared files then you add
it as a dependency of your project.

Emmanuel

On Thu, Dec 10, 2009 at 10:52 AM, Engebakken Geir
wrote:

> Thats correct, problem solved. Thank you!
>
>
> Geir
>
> -----Original Message-----
> From: Brent Atkinson [mailto:batkinson@...]
> Sent: 9. desember 2009 18:33
> To: users@...
> Subject: Re: Problem with multi module maven project
>
> You could add the project as a recursive build. This should run it like you
> would from the command line if I'm not mistaken.
>
> Brent
>
> >>> Engebakken Geir 12/09/09 10:43 AM >>>
> We have a multi module maven project that we have added to continuum, by
> the parent pom. Continuum then put all subprojects into continuum. But the
> problem is that all subprojects are placed in the same directory "level",
> that is for us this is :
>
> /usr/local/continuum/data/working-directory
>
> All projects are placed in a flat structure there with a numeric id as top
> level directory.
>
> This is a problem for the submodules, as they refer to some files in the
> parent project like this :
>
> ${basedir}/../../wsdl/documentws/document/Document.wsdl
>
> The ../.. notation from ($basedir) then fails. Any idea how we can fix this
> ?
>
> Geir
>
>
>
>

Re: Problem with multi module maven project

2009-12-11T07:10:30Z

Gier,

I'd take Emmanuel's recommendation seriously if you're wanting the project to be manageable and work with the conventional tools. It may work this way, but you will have to fight against the tools where you wouldn't have to otherwise.

Brent

>>> Emmanuel Venisse 12/10/09 8:43 AM >>>
It's a bad practice to use a file that is stored under an other project.

The best practice is to create a module that store shared files then you add
it as a dependency of your project.

Emmanuel

On Thu, Dec 10, 2009 at 10:52 AM, Engebakken Geir
wrote:

Re: Problem with multi module maven project

2009-12-10T05:42:16Z

It's a bad practice to use a file that is stored under an other project.

The best practice is to create a module that store shared files then you add
it as a dependency of your project.

Emmanuel

On Thu, Dec 10, 2009 at 10:52 AM, Engebakken Geir
<geir.engebakken@...>wrote:

RE: Problem with multi module maven project

2009-12-10T01:52:48Z

Thats correct, problem solved. Thank you!

Geir

-----Original Message-----
From: Brent Atkinson [mailto:batkinson@...]
Sent: 9. desember 2009 18:33
To: users@...
Subject: Re: Problem with multi module maven project

You could add the project as a recursive build. This should run it like you would from the command line if I'm not mistaken.

Brent

>>> Engebakken Geir 12/09/09 10:43 AM >>>
We have a multi module maven project that we have added to continuum, by the parent pom. Continuum then put all subprojects into continuum. But the problem is that all subprojects are placed in the same directory "level", that is for us this is :

/usr/local/continuum/data/working-directory

All projects are placed in a flat structure there with a numeric id as top level directory.

This is a problem for the submodules, as they refer to some files in the parent project like this :

${basedir}/../../wsdl/documentws/document/Document.wsdl

The ../.. notation from ($basedir) then fails. Any idea how we can fix this ?

Geir

Re: Problem with multi module maven project

2009-12-09T09:33:04Z

You could add the project as a recursive build. This should run it like you would from the command line if I'm not mistaken.

Brent

>>> Engebakken Geir 12/09/09 10:43 AM >>>
We have a multi module maven project that we have added to continuum, by the parent pom. Continuum then put all subprojects into continuum. But the problem is that all subprojects are placed in the same directory "level", that is for us this is :

/usr/local/continuum/data/working-directory

All projects are placed in a flat structure there with a numeric id as top level directory.

This is a problem for the submodules, as they refer to some files in the parent project like this :

${basedir}/../../wsdl/documentws/document/Document.wsdl

The ../.. notation from ($basedir) then fails. Any idea how we can fix this ?

Geir

Re: Problem with multi module maven project

2009-12-09T07:47:39Z

One idea- not really good solution but temporally hack - try to use
symbolic link on server for access to right directories

With best regards,

Dmitro Kopylov

2009/12/9 Engebakken Geir <geir.engebakken@...>:

> We have a multi module maven project that we have added to continuum, by the parent pom. Continuum then put all subprojects into continuum. But the problem is that all subprojects are placed in the same directory "level", that is for us this is :
>
> /usr/local/continuum/data/working-directory
>
> All projects are placed in a flat structure there with a numeric id as top level directory.
>
> This is a problem for the submodules, as they refer to some files in the parent project like this :
>
> <axis2.wsdlFile>${basedir}/../../wsdl/documentws/document/Document.wsdl</axis2.wsdlFile>
>
> The ../.. notation from ($basedir) then fails. Any idea how we can fix this ?
>
> Geir
>
>
>

Problem with multi module maven project

2009-12-09T07:41:57Z

We have a multi module maven project that we have added to continuum, by the parent pom. Continuum then put all subprojects into continuum. But the problem is that all subprojects are placed in the same directory "level", that is for us this is :

/usr/local/continuum/data/working-directory

All projects are placed in a flat structure there with a numeric id as top level directory.

This is a problem for the submodules, as they refer to some files in the parent project like this :

<axis2.wsdlFile>${basedir}/../../wsdl/documentws/document/Document.wsdl</axis2.wsdlFile>

The ../.. notation from ($basedir) then fails. Any idea how we can fix this ?

Geir

AW: Author, Date and Comment empty in SCM Changes section

2009-12-08T04:27:26Z

Hi,

I have an issue with the migration from 1.2.2 to 1.3.4.
I tried to export the data as described in the upgrade documentation.
Unfortunately the data management client version 1.2.3.1 throws an exception...

Any idea what might be wrong here?

Thanks a lot for your help!

java -Xmx512m -jar data-management-cli-1.2.3.1-app.jar -buildsJdbcUrl jdbc:derby:continuum-1.2.2/data/databases/continuum -mode EXPORT -directory backups
0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database...
Exception in thread "main" org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.settings.MavenSettingsBuilder', it co uld not be created
at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:151)
at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:69)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:297)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291)
at org.apache.maven.continuum.management.DataManagementCli.getSettings(DataManagementCli.java:426)
at org.apache.maven.continuum.management.DataManagementCli.initializeWagon(DataManagementCli.java:282)
at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:195)
at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:170)
Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instantiate component: role: 'org.apache.maven.settings.MavenSettingsBuilder', implementation: 'org.apache.maven.settings.DefaultMavenSettingsBuilder', role hint: 'default' realm: plexus.core
at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:113)
at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:87)
at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:239)
at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:128)
at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:90)
at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:147)
...7 more
Caused by: java.lang.NoClassDefFoundError: org.apache.maven.settings.DefaultMavenSettingsBuilder
at java.lang.Class.initializeClass(libgcj.so.81)
at java.lang.Class.newInstance(libgcj.so.81)
at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:66)
...11 more
Caused by: java.lang.VerifyError: verification failed at PC 63 in org.apache.maven.settings.DefaultMavenSettingsBuilder:readSettings((Ljava.io.File;)Lorg.apache.maven.settings.Settings;) : incompatible type on stack
at java.lang.Class.initializeClass(libgcj.so.81)
...13 more

Author, Date and Comment empty in SCM Changes section

2009-12-03T13:45:36Z

Hi all,

I can see that a file was modified but not author, date and comment. I've read in this forum that it may be related to date locale ? I'm using GIT as SCM here my URL in my POM:

<scm>
    <connection>scm:git:git://192.168.1.50/public/project.git</connection>
    <developerConnection>scm:git:git://192.168.1.50/public/project.git</developerConnection>
</scm>

I've also run this command "mvn scm:changelog" and got this output

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO] ------------------------------------------------------------------------
[INFO] Building snAssurance Maven Webapp
[INFO]    task-segment: [scm:changelog] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [scm:changelog]
[INFO] Executing: /bin/sh -c cd /usr/local/continuum-data/working-directory/5 && git whatchanged '--until=2009-12-03 21:44:07 +0000' --date=iso
[INFO] Working directory: /usr/local/continuum-data/working-directory/5
Sacha Fournier fourniers@...
Thu Dec 03 08:54:36 EST 2009
README, 09b6eb22eb0e8c2f24dd77f703335971fccf9dd9
change README
Sacha Fournier fourniers@...
Wed Dec 02 16:37:31 EST 2009
README, b802919fbe5298370a2fb94e840e6ba63cc97195
change README
...
...

Can some one help me ?

--
Signature

	Sacha Fournier Programmeur-Analyste		Tél. +1 (450) 348-5715 Fax +1 (450) 348-0224		385, 5ième avenue St-Jean-Sur-Richelieu (QC), J2X 1V2 fourniers@...
------------------------------------------------------------------------------------------------------------------------------------- Ce message et toutes les pièces jointes sont confidentiels et établis à l'attention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation écrite expresse. Si vous recevez ce message par erreur, merci de le détruire. -------------------------------------------------------------------------------------------------------------------------------------

Justin is out-of-office

2009-12-02T14:05:14Z

I will be out of the office starting 3 Dec 2009 and will not return until
10 Dec 2009.

I will have limited access to email during this time.

For all extensions listed below, please dial +86 20 8132 1833 or tieline
718630 internally

For QMS Deployment Support please contact:
HBMY - Erin L N Wang at x2835
HBUS - Linda D A Lin at x2833
HBME/FD - Bo Hai (Rikent) Gan at x2885

For HBME/HBMX/LATAM/HBCA/SABB GWIS projects, OHD1.2 AO QMS Deployment
Support and Captiva scanning including 1H Signature Scanning please contact
Xi M (Eros) Ye at x2693

For AMH/HASE/AOC/Europe GWIS projects, please contact Wen Y (Wiskey) Tang
at x2316

For Dialogue/CYS projects please contact Kenneth H Liu at x2668

Eros Ye (x2693) is my OIC in my absence.

For any issues requiring immediate escalation, please contact my manager
Jacob T K Kot at x2802

*********************************************************
This email may contain confidential information, and is intended
only for the named recipient and may be privileged. Distribution or
copying of this email by anyone other than the named recipient is
prohibited. If you are not the named recipient, please notify us
immediately and permanently destroy this email and all copies of
it. Internet email is not private, secure, or reliable. No member
of the HSBC Group is liable for any errors or omissions in the
content or transmission of this email. Any opinions contained in
this email are solely those of the author and, unless clearly
indicated otherwise in writing, are not endorsed by any member of
the HSBC Group.
***********************************************************
Ce courriel peut renfermer des renseignements confidentiels et
privilégiés et s'adresse au destinataire désigné seulement. La
distribution ou la copie de ce courriel par toute personne autre
que le destinataire désigné est interdite. Si vous n'êtes pas le
destinataire désigné, veuillez nous en aviser immédiatement et
détruire de façon permanente ce courriel ainsi que toute copie de
celui-ci. La transmission de courriel par Internet ne constitue pas
un mode de transmission confidentiel, sécuritaire ou fiable. Aucun
membre du Groupe HSBC ne sera responsable des erreurs ou des
omissions relatives au contenu ou à la transmission de ce courriel.
L'auteur de ce courriel est seul responsable des opinions émises
dans ce courriel, lesquelles, à moins d'un avis contraire fourni
par écrit, ne sont pas endossées par aucun membre du Groupe HSBC.
***********************************************************

"SAVE PAPER - THINK BEFORE YOU PRINT!"

"ÉCONOMISEZ LE PAPIER ? PENSEZ-Y À DEUX FOIS AVANT D'IMPRIMER!"

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-12-02T14:00:37Z

On Mon, Nov 30, 2009 at 1:04 PM, Bill Brown <wbrown@...> wrote:

> I'm getting the same error with tomcat 5.5.27 and tomcat 6.0.20 on Redhat
> linux 386.

I had no problems with Continuum 1.3.4 in Tomcat 6.0.20 on OS X. I
don't have a Linux box to test with at the moment, but I doubt that's
the issue.

I followed the instructions at
http://continuum.apache.org/docs/1.3.4/installation/tomcat.html using
option #2 for the JNDI resources and putting the four jars in
$TOMCAT_HOME/lib.

It started up, I added the admin user and saved the configuration,
added a project and built it.

If you're still having trouble, can you start a new thread and give
the exact steps you followed so someone can try to reproduce the
problem? (This one has wandered away from the original subject and
probably isn't getting the visibility you want.)

--
Wendy

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-30T12:04:21Z

Hi Wendy:

I'm getting the same error with tomcat 5.5.27 and tomcat 6.0.20 on Redhat linux 386.

Thanks again for looking at this.

Bill.

Wendy Smoak-3 wrote:

On Mon, Nov 30, 2009 at 11:39 AM, Bill Brown
<wbrown@colorfulsoftware.com> wrote:

> I tried your suggestion of starting with an empty embedded derby users db
> but am getting the same error. I also tried starting with a fresh empty
> embedded derby continuum db as well but get the same error.
>
> I am deploying on tomcat 6. Do you know if that is possible with this
> version? I'm not sure what to try next for debugging this?

... so now it sounds like a generic "Continuum 1.3.4 on Tomcat" issue
rather than anything to do with your data. Correct? (What specific
version of Tomcat are you using?)

I won't have time to test it in Tomcat until Wednesday at the
earliest, but maybe someone else here can comment on whether 1.3.4
works on Tomcat for them.

--
Wendy

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-30T11:01:56Z

On Mon, Nov 30, 2009 at 11:39 AM, Bill Brown
<wbrown@...> wrote:

> I tried your suggestion of starting with an empty embedded derby users db
> but am getting the same error. I also tried starting with a fresh empty
> embedded derby continuum db as well but get the same error.
>
> I am deploying on tomcat 6. Do you know if that is possible with this
> version? I'm not sure what to try next for debugging this?

... so now it sounds like a generic "Continuum 1.3.4 on Tomcat" issue
rather than anything to do with your data. Correct? (What specific
version of Tomcat are you using?)

I won't have time to test it in Tomcat until Wednesday at the
earliest, but maybe someone else here can comment on whether 1.3.4
works on Tomcat for them.

--
Wendy

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-30T10:39:35Z

Hi Wendy:

I tried your suggestion of starting with an empty embedded derby users db but am getting the same error. I also tried starting with a fresh empty embedded derby continuum db as well but get the same error.

I am deploying on tomcat 6. Do you know if that is possible with this version? I'm not sure what to try next for debugging this?

Thanks for looking at this issue.

Bill.

Here is the full trace again during app startup:

Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'authenticationManager': Invocation of init method failed; nes
ted exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'authenticator#keystore': Injection of resource fields f
ailed; nested exception is org.springframework.beans.factory.BeanCreationExcepti
on: Error creating bean with name 'userManager#configurable': Injection of resou
rce fields failed; nested exception is org.springframework.beans.factory.BeanCre
ationException: Error creating bean with name 'userConfiguration' defined in URL
[jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2
.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initia
lization of bean failed; nested exception is org.springframework.beans.factory.B
eanCreationException: Error creating bean with name 'registry#commons-configurat
ion': Post-processing of the FactoryBean's object failed; nested exception is or
g.springframework.beans.factory.BeanInitializationException: Failed to invoke pl
exus lifecycle Initializable.initialize on registry#commons-configuration; neste
d exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.Initializa
tionException: org.apache.commons.configuration.ConfigurationRuntimeException: o
rg.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns ca
nnot be set!
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBea
nPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProc
essor.java:147)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanF
actory.java:350)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1331)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
ject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
y.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
findAutowireCandidates(DefaultListableBeanFactory.java:671)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
resolveDependency(DefaultListableBeanFactory.java:610)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.autowireResource(CommonAnnotationBeanPostProcessor.java:431)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.getResource(CommonAnnotationBeanPostProcessor.java:409)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:5
37)
at org.springframework.beans.factory.annotation.InjectionMetadata$Inject
edElement.inject(InjectionMetadata.java:180)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject
Fields(InjectionMetadata.java:105)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:289)
... 58 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'authenticator#keystore': Injection of resource fields failed;
nested exception is org.springframework.beans.factory.BeanCreationException: Er
ror creating bean with name 'userManager#configurable': Injection of resource fi
elds failed; nested exception is org.springframework.beans.factory.BeanCreationE
xception: Error creating bean with name 'userConfiguration' defined in URL [jar:
file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/
org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initializati
on of bean failed; nested exception is org.springframework.beans.factory.BeanCre
ationException: Error creating bean with name 'registry#commons-configuration':
Post-processing of the FactoryBean's object failed; nested exception is org.spri
ngframework.beans.factory.BeanInitializationException: Failed to invoke plexus l
ifecycle Initializable.initialize on registry#commons-configuration; nested exce
ption is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationEx
ception: org.apache.commons.configuration.ConfigurationRuntimeException: org.apa
che.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot b
e set!
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:292)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.populateBean(AbstractAutowireCapableBeanFactory.java:959)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
ject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
y.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBea
n(AbstractApplicationContext.java:880)
at org.codehaus.plexus.spring.PlexusToSpringUtils.lookupMap(PlexusToSpri
ngUtils.java:148)
at org.codehaus.plexus.spring.PlexusToSpringUtils.lookupList(PlexusToSpr
ingUtils.java:160)
at org.codehaus.plexus.redback.authentication.DefaultAuthenticationManag
er.initialize(DefaultAuthenticationManager.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBea
nPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.ja
va:297)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBea
nPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPost
Processor.java:250)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBea
nPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProc
essor.java:144)
... 77 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'userManager#configurable': Injection of resource fields faile
d; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/
tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codeha
us/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean
failed; nested exception is org.springframework.beans.factory.BeanCreationExcep
tion: Error creating bean with name 'registry#commons-configuration': Post-proce
ssing of the FactoryBean's object failed; nested exception is org.springframewor
k.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle I
nitializable.initialize on registry#commons-configuration; nested exception is o
rg.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: o
rg.apache.commons.configuration.ConfigurationRuntimeException: org.apache.common
s.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:292)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.populateBean(AbstractAutowireCapableBeanFactory.java:959)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
ject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
y.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:168)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.autowireResource(CommonAnnotationBeanPostProcessor.java:435)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.getResource(CommonAnnotationBeanPostProcessor.java:409)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:5
37)
at org.springframework.beans.factory.annotation.InjectionMetadata$Inject
edElement.inject(InjectionMetadata.java:180)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject
Fields(InjectionMetadata.java:105)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:289)
... 98 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webap
ps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/re
dback/configuration/UserConfiguration.class]: Initialization of bean failed; nes
ted exception is org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'registry#commons-configuration': Post-processing of the
FactoryBean's object failed; nested exception is org.springframework.beans.fact
ory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable
.initialize on registry#commons-configuration; nested exception is org.codehaus.
plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.co
mmons.configuration.ConfigurationRuntimeException: org.apache.commons.configurat
ion.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
ject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
y.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:168)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.autowireResource(CommonAnnotationBeanPostProcessor.java:435)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.getResource(CommonAnnotationBeanPostProcessor.java:409)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:5
37)
at org.springframework.beans.factory.annotation.InjectionMetadata$Inject
edElement.inject(InjectionMetadata.java:180)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject
Fields(InjectionMetadata.java:105)
at org.springframework.context.annotation.CommonAnnotationBeanPostProces
sor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:289)
... 114 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'registry#commons-configuration': Post-processing of the Facto
ryBean's object failed; nested exception is org.springframework.beans.factory.Be
anInitializationException: Failed to invoke plexus lifecycle Initializable.initi
alize on registry#commons-configuration; nested exception is org.codehaus.plexus
.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.
configuration.ConfigurationRuntimeException: org.apache.commons.configuration.Co
nfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$
1.run(FactoryBeanRegistrySupport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.
doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:116)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.
getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:91)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObje
ctForBeanInstance(AbstractBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:217)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBea
n(AbstractApplicationContext.java:880)
at org.codehaus.plexus.spring.PlexusContainerAdapter.lookup(PlexusContai
nerAdapter.java:422)
at org.codehaus.plexus.redback.configuration.UserConfiguration.contextua
lize(UserConfiguration.java:212)
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProce
ssAfterInitialization(PlexusLifecycleBeanPostProcessor.java:157)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFa
ctory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1344)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
... 128 more
Caused by: org.springframework.beans.factory.BeanInitializationException: Failed
to invoke plexus lifecycle Initializable.initialize on registry#commons-configu
ration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.pha
se.InitializationException: org.apache.commons.configuration.ConfigurationRuntim
eException: org.apache.commons.configuration.ConfigurationRuntimeException: Prop
erty xmlns cannot be set!
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProce
ssAfterInitialization(PlexusLifecycleBeanPostProcessor.java:221)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFa
ctory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.postProcessObjectFromFactoryBean(AbstractAutowireCapableBeanFactory.java
:1429)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$
1.run(FactoryBeanRegistrySupport.java:139)
... 142 more
Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.Initialization
Exception: org.apache.commons.configuration.ConfigurationRuntimeException: org.a
pache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot
be set!
at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.ini
tialize(CommonsConfigurationRegistry.java:388)
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProce
ssAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)
... 145 more
Caused by: org.apache.commons.configuration.ConfigurationException: org.apache.c
ommons.configuration.ConfigurationRuntimeException: org.apache.commons.configura
tion.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.DefaultConfigurationBuilder.createCo
nfigurationAt(DefaultConfigurationBuilder.java:637)
at org.apache.commons.configuration.DefaultConfigurationBuilder.initComb
inedConfiguration(DefaultConfigurationBuilder.java:569)
at org.apache.commons.configuration.DefaultConfigurationBuilder.getConfi
guration(DefaultConfigurationBuilder.java:501)
at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.ini
tialize(CommonsConfigurationRegistry.java:374)
... 146 more
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: org.a
pache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot
be set!
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(Bean
Helper.java:250)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(Bean
Helper.java:267)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(Bean
Helper.java:281)
at org.apache.commons.configuration.DefaultConfigurationBuilder.createCo
nfigurationAt(DefaultConfigurationBuilder.java:632)
... 149 more
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: Prope
rty xmlns cannot be set!
at org.apache.commons.configuration.beanutils.BeanHelper.initProperty(Be
anHelper.java:197)
at org.apache.commons.configuration.beanutils.BeanHelper.initBean(BeanHe
lper.java:167)
at org.apache.commons.configuration.beanutils.DefaultBeanFactory.initBea
nInstance(DefaultBeanFactory.java:106)
at org.apache.commons.configuration.beanutils.DefaultBeanFactory.createB
ean(DefaultBeanFactory.java:62)
at org.apache.commons.configuration.DefaultConfigurationBuilder$Configur
ationProvider.getConfiguration(DefaultConfigurationBuilder.java:845)
at org.apache.commons.configuration.DefaultConfigurationBuilder$Configur
ationBeanFactory.createBean(DefaultConfigurationBuilder.java:1093)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(Bean
Helper.java:245)
... 152 more
2009-11-30 12:33:29,661 [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
INFO com.opensymphony.xwork2.util.ObjectTypeDeterminerFactory - Setting Defau
ltObjectTypeDeterminer as default ...

Wendy Smoak-3 wrote:

On Wed, Nov 25, 2009 at 10:42 AM, Bill Brown
<wbrown@colorfulsoftware.com> wrote:

> After shutting down the 1.2.3 build with mysql backend, I undeployed it and
> redeployed the 1.3.4 war. It seems to be failing in the redback library
> from some reason (below) do you know how I can work around this to get
> 1.3.4 running? Looks like maybe a version mis-match issue but I'm not sure
> what to change. Thanks for your comments.

In a quick check, I didn't have a problem pointing 1.3.4 at data from
1.2.3 using the embedded Derby database in the Jetty bundle. It was
only a couple of users and project groups, but it started right up.

The errors you posted are from Redback, which handles the users and security.

To narrow it down, can you try configuring a new/empty user database
and starting it with just the builds data? It should prompt you to
create the admin user.

If that works, then we can focus on the user data as the problem.
(Or, if you don't have very many users, you may elect to just
re-create them.)

--
Wendy

Re: Build queues.

2009-11-30T01:49:14Z

2009/11/27 Wendy Smoak <wsmoak@...>

> On Fri, Nov 27, 2009 at 7:06 AM, Butch Slayer <butch.slayers@...>
> wrote:
>
> > I have a single project of which I need to build three different targets.
> So
> > I did the following:
> > I made one project and put three build definitions in. Scheduled at
> > different times, using different schedules works fine. But I would like
> to
> > run all three build definition simultaneous. I tried to do this using
> queues
> > but did not succeed. Can anyone help me out please?
> >
> > I am using a shell project.
>
> What version of Continuum are you using?
>
> Thanks for the input.

I'm working with version 1.3.4, build 807129 of Continuum.

Just on the surface, I don't think it's going to let you do

> simultaneous builds from the same working copy.
>
> They would step on each other, trying to delete and write the same
> files -- or at least that's the assumption, based on the typical 'mvn
> clean install' build which first deletes the 'target' directory, then
> re-creates it and writes files there.
>
> Your shell project may not actually have that limitation, but I think
> it's built in. Someone more familiar with the code would need to
> confirm.
>
> That's right. I have a build directory for each target.

> You'll probably have to add the project three times so there are
> different working copies, possibly in three different project groups
> (it might complain about duplicates otherwise, not sure how that works
> with shell projects.)
>
> That is what I thought/feared. It's a petty, it feels like wasting
resources...
Next to these three (or more) targets I'll have more versions to build too
in the future.

Is there a way to share a single working copy between more than one project?

Kind regards,
Butch.

Re: Build queues.

2009-11-27T09:31:51Z

On Fri, Nov 27, 2009 at 7:06 AM, Butch Slayer <butch.slayers@...> wrote:

> I have a single project of which I need to build three different targets. So
> I did the following:
> I made one project and put three build definitions in. Scheduled at
> different times, using different schedules works fine. But I would like to
> run all three build definition simultaneous. I tried to do this using queues
> but did not succeed. Can anyone help me out please?
>
> I am using a shell project.

What version of Continuum are you using?

Just on the surface, I don't think it's going to let you do
simultaneous builds from the same working copy.

They would step on each other, trying to delete and write the same
files -- or at least that's the assumption, based on the typical 'mvn
clean install' build which first deletes the 'target' directory, then
re-creates it and writes files there.

Your shell project may not actually have that limitation, but I think
it's built in. Someone more familiar with the code would need to
confirm.

You'll probably have to add the project three times so there are
different working copies, possibly in three different project groups
(it might complain about duplicates otherwise, not sure how that works
with shell projects.)

--
Wendy

Build queues.

2009-11-27T06:06:15Z

Hi,

I have a single project of which I need to build three different targets. So
I did the following:
I made one project and put three build definitions in. Scheduled at
different times, using different schedules works fine. But I would like to
run all three build definition simultaneous. I tried to do this using queues
but did not succeed. Can anyone help me out please?

I am using a shell project.

Kind regards,
Butch.

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-25T15:24:41Z

On Wed, Nov 25, 2009 at 10:42 AM, Bill Brown
<wbrown@...> wrote:

> After shutting down the 1.2.3 build with mysql backend, I undeployed it and
> redeployed the 1.3.4 war. It seems to be failing in the redback library
> from some reason (below) do you know how I can work around this to get
> 1.3.4 running? Looks like maybe a version mis-match issue but I'm not sure
> what to change. Thanks for your comments.

In a quick check, I didn't have a problem pointing 1.3.4 at data from
1.2.3 using the embedded Derby database in the Jetty bundle. It was
only a couple of users and project groups, but it started right up.

The errors you posted are from Redback, which handles the users and security.

To narrow it down, can you try configuring a new/empty user database
and starting it with just the builds data? It should prompt you to
create the admin user.

If that works, then we can focus on the user data as the problem.
(Or, if you don't have very many users, you may elect to just
re-create them.)

--
Wendy

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-25T09:42:06Z

Hi Brett:

Thanks for the info.

After shutting down the 1.2.3 build with mysql backend, I undeployed it and redeployed the 1.3.4 war. It seems to be failing in the redback library from some reason (below) do you know how I can work around this to get 1.3.4 running? Looks like maybe a version mis-match issue but I'm not sure what to change. Thanks for your comments.

Thanks.
Bill.

Caught Exception while registering Interceptor class redbackEnvironmentCheckInterceptor - interceptor - file:/opt/tomcat/webapps/continuum/WEB-INF/classes/struts-security.xml:30:87
at com.opensymphony.xwork2.ObjectFactory.buildInterceptor(ObjectFactory.java:206)
at com.opensymphony.xwork2.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:57)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:905)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:743)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptorStacks(XmlConfigurationProvider.java:756)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptors(XmlConfigurationProvider.java:777)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.addPackage(XmlConfigurationProvider.java:410)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadPackages(XmlConfigurationProvider.java:239)
at org.apache.struts2.config.StrutsXmlConfigurationProvider.loadPackages(StrutsXmlConfigurationProvider.java:111)
at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reload(DefaultConfiguration.java:152)
at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:52)
at org.apache.struts2.dispatcher.Dispatcher.init_PreloadConfiguration(Dispatcher.java:395)
at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:452)
at org.apache.struts2.dispatcher.FilterDispatcher.init(FilterDispatcher.java:205)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:221)
at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:302)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:78)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3635)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4222)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1218)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1306)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1570)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1579)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'interceptor#redbackEnvironmentCheckInterceptor': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'environmentCheck#locked-admin-check': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userManager#configurable': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:116)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:91)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:217)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880)
at com.opensymphony.xwork2.spring.SpringObjectFactory.buildBean(SpringObjectFactory.java:126)
at com.opensymphony.xwork2.ObjectFactory.buildBean(ObjectFactory.java:143)
at org.codehaus.plexus.spring.Struts2PlexusInSpringObjectFactory.buildBean(Struts2PlexusInSpringObjectFactory.java:65)
at com.opensymphony.xwork2.ObjectFactory.buildInterceptor(ObjectFactory.java:184)
... 32 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'environmentCheck#locked-admin-check': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userManager#configurable': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:292)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:959)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.codehaus.plexus.spring.PlexusToSpringUtils.lookupMap(PlexusToSpringUtils.java:148)
at org.codehaus.plexus.spring.PlexusToSpringUtils.lookupList(PlexusToSpringUtils.java:160)
at org.codehaus.plexus.spring.PlexusComponentFactoryBean.resolveRequirement(PlexusComponentFactoryBean.java:242)
at org.codehaus.plexus.spring.PlexusComponentFactoryBean.createInstance(PlexusComponentFactoryBean.java:163)
at org.codehaus.plexus.spring.PlexusComponentFactoryBean.getObject(PlexusComponentFactoryBean.java:108)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:121)
... 44 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userManager#configurable': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:292)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:959)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:168)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.autowireResource(CommonAnnotationBeanPostProcessor.java:435)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.getResource(CommonAnnotationBeanPostProcessor.java:409)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:537)
at org.springframework.beans.factory.annotation.InjectionMetadata$InjectedElement.inject(InjectionMetadata.java:180)
at org.springframework.beans.factory.annotation.InjectionMetadata.injectFields(InjectionMetadata.java:105)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:289)
... 60 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:168)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.autowireResource(CommonAnnotationBeanPostProcessor.java:435)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.getResource(CommonAnnotationBeanPostProcessor.java:409)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor$ResourceElement.getResourceToInject(CommonAnnotationBeanPostProcessor.java:537)
at org.springframework.beans.factory.annotation.InjectionMetadata$InjectedElement.inject(InjectionMetadata.java:180)
at org.springframework.beans.factory.annotation.InjectionMetadata.injectFields(InjectionMetadata.java:105)
at org.springframework.context.annotation.CommonAnnotationBeanPostProcessor.postProcessAfterInstantiation(CommonAnnotationBeanPostProcessor.java:289)
... 76 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:116)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:91)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:217)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880)
at org.codehaus.plexus.spring.PlexusContainerAdapter.lookup(PlexusContainerAdapter.java:422)
at org.codehaus.plexus.redback.configuration.UserConfiguration.contextualize(UserConfiguration.java:212)
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:157)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1344)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
... 90 more
Caused by: org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:221)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.postProcessObjectFromFactoryBean(AbstractAutowireCapableBeanFactory.java:1429)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:139)
... 104 more
Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.initialize(CommonsConfigurationRegistry.java:388)
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)
... 107 more
Caused by: org.apache.commons.configuration.ConfigurationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.DefaultConfigurationBuilder.createConfigurationAt(DefaultConfigurationBuilder.java:637)
at org.apache.commons.configuration.DefaultConfigurationBuilder.initCombinedConfiguration(DefaultConfigurationBuilder.java:569)
at org.apache.commons.configuration.DefaultConfigurationBuilder.getConfiguration(DefaultConfigurationBuilder.java:501)
at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.initialize(CommonsConfigurationRegistry.java:374)
... 108 more
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:250)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:267)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:281)
at org.apache.commons.configuration.DefaultConfigurationBuilder.createConfigurationAt(DefaultConfigurationBuilder.java:632)
... 111 more
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.beanutils.BeanHelper.initProperty(BeanHelper.java:197)
at org.apache.commons.configuration.beanutils.BeanHelper.initBean(BeanHelper.java:167)
at org.apache.commons.configuration.beanutils.DefaultBeanFactory.initBeanInstance(DefaultBeanFactory.java:106)
at org.apache.commons.configuration.beanutils.DefaultBeanFactory.createBean(DefaultBeanFactory.java:62)
at org.apache.commons.configuration.DefaultConfigurationBuilder$ConfigurationProvider.getConfiguration(DefaultConfigurationBuilder.java:845)
at org.apache.commons.configuration.DefaultConfigurationBuilder$ConfigurationBeanFactory.createBean(DefaultConfigurationBuilder.java:1093)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:245)
... 114 more
2009-11-25 11:12:09,995 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] WARN com.opensymphony.xwork2.config.providers.InterceptorBuilder - Unable to load config class redbackForceAdminUserInterceptor at interceptor - file:/opt/tomcat/webapps/continuum/WEB-INF/classes/struts-security.xml:29:91 probably due to a missing jar, which might be fine if you never plan to use the redbackForceAdminUser interceptor
2009-11-25 11:12:09,995 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR com.opensymphony.xwork2.config.providers.InterceptorBuilder - Actual exception
Caught Exception while registering Interceptor class redbackForceAdminUserInterceptor - interceptor - file:/opt/tomcat/webapps/continuum/WEB-INF/classes/struts-security.xml:29:91
at com.opensymphony.xwork2.ObjectFactory.buildInterceptor(ObjectFactory.java:206)
at com.opensymphony.xwork2.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:57)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:905)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:743)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptorStacks(XmlConfigurationProvider.java:756)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptors(XmlConfigurationProvider.java:777)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.addPackage(XmlConfigurationProvider.java:410)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadPackages(XmlConfigurationProvider.java:239)
at org.apache.struts2.config.StrutsXmlConfigurationProvider.loadPackages(StrutsXmlConfigurationProvider.java:111)
at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reload(DefaultConfiguration.java:152)
at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:52)
at org.apache.struts2.dispatcher.Dispatcher.init_PreloadConfiguration(Dispatcher.java:395)
at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:452)
at org.apache.struts2.dispatcher.FilterDispatcher.init(FilterDispatcher.java:205)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:221)
at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:302)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:78)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3635)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4222)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1218)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1306)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1570)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1579)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'interceptor#redbackForceAdminUserInterceptor': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:116)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:91)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:217)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880)
at com.opensymphony.xwork2.spring.SpringObjectFactory.buildBean(SpringObjectFactory.java:126)
at com.opensymphony.xwork2.ObjectFactory.buildBean(ObjectFactory.java:143)
at org.codehaus.plexus.spring.Struts2PlexusInSpringObjectFactory.buildBean(Struts2PlexusInSpringObjectFactory.java:65)
at com.opensymphony.xwork2.ObjectFactory.buildInterceptor(ObjectFactory.java:184)
... 32 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.codehaus.plexus.spring.PlexusComponentFactoryBean.resolveRequirement(PlexusComponentFactoryBean.java:246)
at org.codehaus.plexus.spring.PlexusComponentFactoryBean.createInstance(PlexusComponentFactoryBean.java:163)
at org.codehaus.plexus.spring.PlexusComponentFactoryBean.getObject(PlexusComponentFactoryBean.java:108)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:121)
... 44 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:116)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:91)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1288)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:217)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880)
at org.codehaus.plexus.spring.PlexusContainerAdapter.lookup(PlexusContainerAdapter.java:422)
at org.codehaus.plexus.redback.configuration.UserConfiguration.contextualize(UserConfiguration.java:212)
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:157)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1344)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
... 56 more
Caused by: org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:221)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.postProcessObjectFromFactoryBean(AbstractAutowireCapableBeanFactory.java:1429)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:139)
... 70 more
Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.initialize(CommonsConfigurationRegistry.java:388)
at org.codehaus.plexus.spring.PlexusLifecycleBeanPostProcessor.postProcessAfterInitialization(PlexusLifecycleBeanPostProcessor.java:217)
... 73 more
Caused by: org.apache.commons.configuration.ConfigurationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.DefaultConfigurationBuilder.createConfigurationAt(DefaultConfigurationBuilder.java:637)
at org.apache.commons.configuration.DefaultConfigurationBuilder.initCombinedConfiguration(DefaultConfigurationBuilder.java:569)
at org.apache.commons.configuration.DefaultConfigurationBuilder.getConfiguration(DefaultConfigurationBuilder.java:501)
at org.codehaus.plexus.registry.commons.CommonsConfigurationRegistry.initialize(CommonsConfigurationRegistry.java:374)
... 74 more
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:250)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:267)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:281)
at org.apache.commons.configuration.DefaultConfigurationBuilder.createConfigurationAt(DefaultConfigurationBuilder.java:632)
... 77 more
Caused by: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
at org.apache.commons.configuration.beanutils.BeanHelper.initProperty(BeanHelper.java:197)
at org.apache.commons.configuration.beanutils.BeanHelper.initBean(BeanHelper.java:167)
at org.apache.commons.configuration.beanutils.DefaultBeanFactory.initBeanInstance(DefaultBeanFactory.java:106)
at org.apache.commons.configuration.beanutils.DefaultBeanFactory.createBean(DefaultBeanFactory.java:62)
at org.apache.commons.configuration.DefaultConfigurationBuilder$ConfigurationProvider.getConfiguration(DefaultConfigurationBuilder.java:845)
at org.apache.commons.configuration.DefaultConfigurationBuilder$ConfigurationBeanFactory.createBean(DefaultConfigurationBuilder.java:1093)
at org.apache.commons.configuration.beanutils.BeanHelper.createBean(BeanHelper.java:245)
... 80 more
2009-11-25 11:12:10,070 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] WARN com.opensymphony.xwork2.config.providers.InterceptorBuilder - Unable to load config class redbackAutoLoginInterceptor at interceptor - file:/opt/tomcat/webapps/continuum/WEB-INF/classes/struts-security.xml:31:81 probably due to a missing jar, which might be fine if you never plan to use the redbackAutoLogin interceptor
2009-11-25 11:12:10,070 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR com.opensymphony.xwork2.config.providers.InterceptorBuilder - Actual exception
Caught Exception while registering Interceptor class redbackAutoLoginInterceptor - interceptor - file:/opt/tomcat/webapps/continuum/WEB-INF/classes/struts-security.xml:31:81
at com.opensymphony.xwork2.ObjectFactory.buildInterceptor(ObjectFactory.java:206)
at com.opensymphony.xwork2.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:57)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:905)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:743)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptorStacks(XmlConfigurationProvider.java:756)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadInterceptors(XmlConfigurationProvider.java:777)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.addPackage(XmlConfigurationProvider.java:410)
at com.opensymphony.xwork2.config.providers.XmlConfigurationProvider.loadPackages(XmlConfigurationProvider.java:239)
at org.apache.struts2.config.StrutsXmlConfigurationProvider.loadPackages(StrutsXmlConfigurationProvider.java:111)
at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reload(DefaultConfiguration.java:152)
at com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:52)
at org.apache.struts2.dispatcher.Dispatcher.init_PreloadConfiguration(Dispatcher.java:395)
at org.apache.struts2.dispatcher.Dispatcher.init(Dispatcher.java:452)
at org.apache.struts2.dispatcher.FilterDispatcher.init(FilterDispatcher.java:205)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:221)
at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:302)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:78)
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3635)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4222)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1218)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1306)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1570)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1579)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'interceptor#redbackAutoLoginInterceptor': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'autoLoginCookies': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securitySystem': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationManager': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticator#keystore': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userManager#configurable': Injection of resource fields failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userConfiguration' defined in URL [jar:file:/opt/tomcat/webapps/continuum/WEB-INF/lib/redback-configuration-1.2.2.jar!/org/codehaus/plexus/redback/configuration/UserConfiguration.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'registry#commons-configuration': Post-processing of the FactoryBean's object failed; nested exception is org.springframework.beans.factory.BeanInitializationException: Failed to invoke plexus lifecycle Initializable.initialize on registry#commons-configuration; nested exception is org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializationException: org.apache.commons.configuration.ConfigurationRuntimeException: org.apache.commons.configuration.ConfigurationRuntimeException: Property xmlns cannot be set!
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'repositoryMetadataBuilder': Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: 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.artifact.repository.metadata.RepositoryMetadataBuilder]
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'modelResolver': Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: 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]
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'knownHostsProvider#null': Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: Failed to convert property value of type [java.lang.String] to required type [java.lang.Class] for property 'implementation'; nested exception is java.lang.IllegalArgumentException: Cannot find class [org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider]
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'repositoryMetadataBuilder': Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: 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.artifact.repository.metadata.RepositoryMetadataBuilder]
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'modelResolver': Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: 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]
Related cause: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'knownHostsProvider#null': Initialization of bean failed; nested exception is org.springframework.beans.TypeMismatchException: Failed to convert property value of type [java.lang.String] to required type [java.lang.Class] for property 'implementation'; nested exception is java.lang.IllegalArgumentException: Cannot find class [org.apache.maven.wagon.providers.ssh.knownhost.NullKnownHostsProvider]

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-25T08:26:58Z

You should be able to point 1.3.x at the existing database and it will work (as long as the other instance is first turned off). Of course, take a backup just in case.

- Brett

On 26/11/2009, at 1:38 AM, Bill Brown wrote:

>
> Thanks for the info Emmanuel:
>
> I would like to upgrade to the 1.3.x build but I have a mysql backend and I
> do not know how to upgrade the 1.2.3 db to the 1.3.x builds. Do you know
> how to do this or can point me to someone who may know?
>
> I apologize for diverging from this specific issue but I'm thinking you may
> be able to give me another helpful tip.
>
> Thanks
> Bill.
> --
> View this message in context: http://old.nabble.com/projects-mysteriously-leaving-the-build-queue-even-though-%28Always-Build%29-is-set.-tp26484565p26513748.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-25T06:38:01Z

Thanks for the info Emmanuel:

I would like to upgrade to the 1.3.x build but I have a mysql backend and I do not know how to upgrade the 1.2.3 db to the 1.3.x builds. Do you know how to do this or can point me to someone who may know?

I apologize for diverging from this specific issue but I'm thinking you may be able to give me another helpful tip.

Thanks
Bill.

Re: projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-24T21:57:48Z

It's a known issue for 1.2.x when Continuum is restarted with some build not
terminated.
This issue is fixed in 1.3.x

Emmanuel

On Mon, Nov 23, 2009 at 8:43 PM, Bill Brown <wbrown@...>wrote:

>
> Greetings:
>
> I'm using the latest stable continuum 1.2.3 (732759).
>
> I'm using it to build 204 maven projects split into 3 project groups
> (dev/stage/prod).
>
> I have the DEFAULT_SCHEDULE setup to fire every minute for all of the
> projects. Each project is set to "Always Build" and "Clean Checkout".
>
> I'm noticing that I can submit "Build All Project" for each group to put
> them all into the queue and everything is queued up. But after a build,
> lots of the projects are not going back into the queue after a successful
> build.
>
> The side effect is that some changes are committed via subversion into some
> of the projects but are never being rebuilt again because they don't stay
> in
> the queue.
>
> Do you know if I can do something in the configuration to always re-queue a
> build even if it builds successfully (I thought that was what the "Always"
> build setting is for)?
>
> Maybe this is a known issue?
>
> Thanks for any information or insights.
> Bill.
>
> --
> View this message in context:
> http://old.nabble.com/projects-mysteriously-leaving-the-build-queue-even-though-%28Always-Build%29-is-set.-tp26484565p26484565.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>
>

projects mysteriously leaving the build queue even though (Always Build) is set.

2009-11-23T11:43:48Z

Greetings:

I'm using the latest stable continuum 1.2.3 (732759).

I'm using it to build 204 maven projects split into 3 project groups (dev/stage/prod).

I have the DEFAULT_SCHEDULE setup to fire every minute for all of the projects. Each project is set to "Always Build" and "Clean Checkout".

I'm noticing that I can submit "Build All Project" for each group to put them all into the queue and everything is queued up. But after a build, lots of the projects are not going back into the queue after a successful build.

The side effect is that some changes are committed via subversion into some of the projects but are never being rebuilt again because they don't stay in the queue.

Do you know if I can do something in the configuration to always re-queue a build even if it builds successfully (I thought that was what the "Always" build setting is for)?

Maybe this is a known issue?

Thanks for any information or insights.
Bill.

RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-20T08:40:48Z

OK, thanks a lot I will try this!

My remark regarding lack of docs was just a hint that it could be better :)

Geir

-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@...]
Sent: 20. november 2009 00:42
To: users@...
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

On Thu, Nov 19, 2009 at 10:23 AM, Wendy Smoak <wsmoak@...> wrote:
> I vaguely remember a utility to automate deleting old build results,
> you might find it in the list archives.

Here it is (but I've only used it against 1.3.x, I don't know if it'll
work with 1.2.x):

http://svn.apache.org/repos/asf/continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-client/src/main/java/org/apache/maven/continuum/xmlrpc/client/BuildResultsPurge.java

--
Wendy

Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T15:42:28Z

On Thu, Nov 19, 2009 at 10:23 AM, Wendy Smoak <wsmoak@...> wrote:
> I vaguely remember a utility to automate deleting old build results,
> you might find it in the list archives.

Here it is (but I've only used it against 1.3.x, I don't know if it'll
work with 1.2.x):

http://svn.apache.org/repos/asf/continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-client/src/main/java/org/apache/maven/continuum/xmlrpc/client/BuildResultsPurge.java

--
Wendy

Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T09:23:24Z

On Thu, Nov 19, 2009 at 8:35 AM, Engebakken Geir
<geir.engebakken@...> wrote:
> There are some 500 build results in the list, I guess this is what halts the delete so there is a timeout, but I have to mark each one of them for deletion?
>
> I deleted 32 of them, and it took 5 minutes!
>
> There must be a way to set this up so that they are deleted manually each night, now where is the manual, oops doesn't exist ...

I think you said 1.2.2, so the docs are here...
http://continuum.apache.org/docs/1.2.2/

In 1.3.x there is a build output purge feature but it only deletes the
output directories, not the database records. The idea was that you
need to keep them around for statistics. I think there's a JIRA issue
open to change this, you can watch/vote for it.

I vaguely remember a utility to automate deleting old build results,
you might find it in the list archives.

Maybe you can use Selenium to automate deleting them through the web interface?

--
Wendy

RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T07:35:24Z

There are some 500 build results in the list, I guess this is what halts the delete so there is a timeout, but I have to mark each one of them for deletion?

I deleted 32 of them, and it took 5 minutes!

There must be a way to set this up so that they are deleted manually each night, now where is the manual, oops doesn't exist ...

Geir

-----Original Message-----
From: Engebakken Geir [mailto:geir.engebakken@...]
Sent: 19. november 2009 16:20
To: users@...; Emmanuel Venisse
Subject: RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

On a second thought, I guess you mean the build results in the DB of course, so I look into that now, but there is a lot!

I guess there must be a way to set up purging older builds or something.....

Geir

-----Original Message-----
From: Engebakken Geir [mailto:geir.engebakken@...]
Sent: 19. november 2009 16:14
To: Emmanuel Venisse; users@...
Subject: RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

I removed the build results (that is the output directory for the builds, which in this case was /usr/local/continuum/data/build-output-directory/67, this is what you meant?)

But had the same error when deleting the project. After that I can show the project group list in the web interface, but if I click any project group, continuum hangs and I must restart continuum.

Geir
From: Emmanuel Venisse [mailto:emmanuel.venisse@...]
Sent: 19. november 2009 14:03
To: users@...
Cc: Engebakken Geir
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

Can you try to delete build results first, maybe only some of them if you have lot.

Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <geir.engebakken@...<mailto:geir.engebakken@...>> wrote:
This must have happened for others as well, I guess, any ideas anybody?

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@...<mailto:users@...>
Subject: RE: A lock could not be obtained within the time requested

Forgot to say that this is continuum 1.2.2.

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@...<mailto:users@...>'
Subject: A lock could not be obtained within the time requested

We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :

A lock could not be obtained within the time requested

Any ideas what this might be.

Geir

RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T07:20:25Z

On a second thought, I guess you mean the build results in the DB of course, so I look into that now, but there is a lot!

I guess there must be a way to set up purging older builds or something.....

Geir

-----Original Message-----
From: Engebakken Geir [mailto:geir.engebakken@...]
Sent: 19. november 2009 16:14
To: Emmanuel Venisse; users@...
Subject: RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

I removed the build results (that is the output directory for the builds, which in this case was /usr/local/continuum/data/build-output-directory/67, this is what you meant?)

But had the same error when deleting the project. After that I can show the project group list in the web interface, but if I click any project group, continuum hangs and I must restart continuum.

Geir
From: Emmanuel Venisse [mailto:emmanuel.venisse@...]
Sent: 19. november 2009 14:03
To: users@...
Cc: Engebakken Geir
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

Can you try to delete build results first, maybe only some of them if you have lot.

Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <geir.engebakken@...<mailto:geir.engebakken@...>> wrote:
This must have happened for others as well, I guess, any ideas anybody?

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@...<mailto:users@...>
Subject: RE: A lock could not be obtained within the time requested

Forgot to say that this is continuum 1.2.2.

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@...<mailto:users@...>'
Subject: A lock could not be obtained within the time requested

We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :

A lock could not be obtained within the time requested

Any ideas what this might be.

Geir

RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T07:14:06Z

I removed the build results (that is the output directory for the builds, which in this case was /usr/local/continuum/data/build-output-directory/67, this is what you meant?)

But had the same error when deleting the project. After that I can show the project group list in the web interface, but if I click any project group, continuum hangs and I must restart continuum.

Geir
From: Emmanuel Venisse [mailto:emmanuel.venisse@...]
Sent: 19. november 2009 14:03
To: users@...
Cc: Engebakken Geir
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

Can you try to delete build results first, maybe only some of them if you have lot.

Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <geir.engebakken@...<mailto:geir.engebakken@...>> wrote:
This must have happened for others as well, I guess, any ideas anybody?

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@...<mailto:users@...>
Subject: RE: A lock could not be obtained within the time requested

Forgot to say that this is continuum 1.2.2.

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@...<mailto:users@...>'
Subject: A lock could not be obtained within the time requested

We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :

A lock could not be obtained within the time requested

Any ideas what this might be.

Geir

Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T05:03:11Z

Can you try to delete build results first, maybe only some of them if you
have lot.

Emmanuel

On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <geir.engebakken@...>wrote:

> This must have happened for others as well, I guess, any ideas anybody?
>
>
> Geir
>
> -----Original Message-----
> From: Engebakken Geir
> Sent: 17. november 2009 11:27
> To: Engebakken Geir; users@...
> Subject: RE: A lock could not be obtained within the time requested
>
> Forgot to say that this is continuum 1.2.2.
>
>
> Geir
>
> -----Original Message-----
> From: Engebakken Geir
> Sent: 17. november 2009 11:26
> To: 'users@...'
> Subject: A lock could not be obtained within the time requested
>
> We try to remove a project in our continuum setup, and continuum just hangs
> and the log shows a java stacktrace in an sql select statement ending with
> :
>
> A lock could not be obtained within the time requested
>
>
> Any ideas what this might be.
>
> Geir
>
>
>
>

YOHO, anybody out there? RE: A lock could not be obtained within the time requested

2009-11-19T04:03:15Z

This must have happened for others as well, I guess, any ideas anybody?

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@...
Subject: RE: A lock could not be obtained within the time requested

Forgot to say that this is continuum 1.2.2.

Geir

-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@...'
Subject: A lock could not be obtained within the time requested

We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :

A lock could not be obtained within the time requested

Any ideas what this might be.

Geir

Reset Build number and Continuum Landing page too slow to open.

2009-11-18T23:06:49Z

2 Questions/issues:

1. We had to delete and recreate a project in Continuum. We use the continuum.project.nextBuild.number value in the name of the artifact which we create during the build. Now, that we have recreated the project, this number gets reset to 1. Is there any way to change this number forcibly as the build numbers form an important reference point w.r.t release information.

2. We have noticed that the Continuum Web Interface takes a long time to show up when we start/restart Continuum. We have only 1 project group with about 10 projects running ANT builds. Is there any reason why performance degrades so much in this case ? Will a upgrade to 1.2 help ?

Thanks for your help in advance.

Regards,
Ashish

Re: Role Documentation for Continuum

2009-11-17T18:08:17Z

Hi Dave,

I'm not sure if you've already read this document already, but the Redback
docs for role management can be found here:

http://redback.codehaus.org/rbac/role-management.html

As for Continuum's documentation of its roles, I don't think there is one.
Your best bet is probably to look at the Redback descriptor itself, which is
located at the continuum-security module:

http://svn.apache.org/repos/asf/continuum/tags/continuum-1.2.3/continuum-security/src/main/resources/META-INF/redback/

HTH,
Deng

On Wed, Nov 18, 2009 at 12:26 AM, dbruley <
david.bruley@...> wrote:

>
> Hello,
>
> Thought I would follow-up on this older post to see if anyone might still
> be
> able to assist. Thought my origional subject heading specifying 1.2.3 may
> have reduced responses. Any documentation on roles even if it's in 1.3.x
> would be appreciated.
>
> Dug through the source a little and looks like Continuum is using Redback
> for Role Management, so I read some of the Redback documentation. Also
> experimented more in Continuum with the different roles, so I think I have
> a
> good enough idea to move forward.
>
> Just always interested in making sure I'm using the features correctly.
>
> Thanks in advance.
>
> Dave
>
>
> dbruley wrote:
> >
> > We're in the process of moving from Continuum 1.0.3 to 1.2.3 and I'm
> > wondering if there is any documentation for the various roles provided in
> > 1.2.3 such as info about each role, how they relate (noticed some roles
> > listed parent roles), and role management (does a user added to a
> specific
> > role also need to be added to any parent roles?), etc.
> >
> > Granted, I'll figure a lot of it out once I play around a bit through
> > trial and error, but if there is any good documentation, I'd like to
> > review it.
> >
> > I could not find anything under the admin or user guides on the Continuum
> > site nor did a search of the list archives or Google return much.
> > Apologize if I somehow overlooked the obvious.
> >
> > We're using LDAP for user authentication if that matters.
> >
> > Thanks in advance for your help and patience with a newbie!
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Role-Documentation-for-Continuum-1.2.3-tp25876812p26392904.html
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>
>

Re: Role Documentation for Continuum

2009-11-17T08:26:21Z

Hello,

Thought I would follow-up on this older post to see if anyone might still be able to assist. Thought my origional subject heading specifying 1.2.3 may have reduced responses. Any documentation on roles even if it's in 1.3.x would be appreciated.

Dug through the source a little and looks like Continuum is using Redback for Role Management, so I read some of the Redback documentation. Also experimented more in Continuum with the different roles, so I think I have a good enough idea to move forward.

Just always interested in making sure I'm using the features correctly.

Thanks in advance.

Dave

dbruley wrote:

We're in the process of moving from Continuum 1.0.3 to 1.2.3 and I'm wondering if there is any documentation for the various roles provided in 1.2.3 such as info about each role, how they relate (noticed some roles listed parent roles), and role management (does a user added to a specific role also need to be added to any parent roles?), etc.

Granted, I'll figure a lot of it out once I play around a bit through trial and error, but if there is any good documentation, I'd like to review it.

I could not find anything under the admin or user guides on the Continuum site nor did a search of the list archives or Google return much. Apologize if I somehow overlooked the obvious.

We're using LDAP for user authentication if that matters.

Thanks in advance for your help and patience with a newbie!

Re: Best Practices/Correct Use of Build Definitions and Templates

2009-11-17T08:14:36Z

Hello all,

Just wanted to follow-up and see if anyone might be able to offer any insight on this topic. Even if you're on 1.3.x I would still be interested in your thoughts as I'm sure at least some of it would apply to 1.2.3 and if nothing else it would be good info to have when we upgrade in the future.

I think through experimenting I have an idea of what I could do, but I just want to make sure it's what I should do!

Thanks in advance,

Dave

dbruley wrote:

Hello,

This is probably a newbie question, but I have a few questions on the correct/intended use of Build Definitions and Build Definition Templates in Continuum 1.2.3. We're developing our plan to upgrade to 1.2.3 from 1.0.3 and want to make sure we're taking full advantage of what 1.2.3 offers.

Reading the documentation and articles on the web, I've created different build definitions and build definition templates. If I add a Maven 2.0 project, I see where I can choose the build definition template I would like to use. That all makes sense.

Where I am a little less clear is what happens/should happen when I create a new group. It seems that it uses the predefined "Default Maven 2 Template". It also seems that the build definition for the group is listed under the Available Build Definitions section when I click "Build Definitions Template", so if I don't rename the group's definition, there will be two entries with a description of "Default Maven 2 Build Definition".

So a few questions:

1) If we want all new groups to have by default an additional goal, let's say site:site, is it acceptable to modify the predefined "Default Maven 2 Build Definition" used by the Default Maven 2 Template.

2) Or, should we modify the Default Maven 2 Template removing the Default Maven 2 Build Definition from Used Build Definitions and adding a definition we define.

3) Since it seems that the build definition for a group is added to the table of build defintions, is it correct to assume that it is good practice to change the description to reference the build definition for that group to avoid seeing multiple listings with a description of "Default Maven 2 Build Definition"

4) If we remove the group level build definition, what is used when we do a Build All Projects in that group?

Are there any other words of wisdom anyone has to offer?

Thanks in advance for any clarification or advice you can offer, I appreciate the help.

Dave

From forum: Continuum - Users (old)