Nabble - Continuum

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

From forum: Continuum - Users

[jira] Created: (CONTINUUM-2418) Status in Project Group Summary Page inconsistent with Build Results

2009-12-03T03:37:55Z

Status in Project Group Summary Page inconsistent with Build Results
--------------------------------------------------------------------

Key: CONTINUUM-2418
URL: http://jira.codehaus.org/browse/CONTINUUM-2418
Project: Continuum
Issue Type: Bug
Components: Web - UI
Affects Versions: 1.3.4
Environment: Windows 2008 Server, Jdk 6
Reporter: Stefan Cordes
Attachments: eai-deploy-helper-141-continuum.log, eai-deploy-helper-build-result.gif, eai-deploy-helper-continuum.log, eai-deploy-helper-status.gif

After Continuum is working a while the status in the
Project Group Summary Page
becomes inconsistent to the one in the
Build Result Page.

Sometimes the Group Summary shows "failed" but last build was sucessful or last build had never been executed (as in the attached example for eai-base-deploy-helper).

Sometimes the Group Summary shows "in progress" but there is no build in progress.
(A try to cancel says "Project is not in Build Queue", a try to Build says "Project is already in Build Queue").

Workaround: Restart Continuum and Status is consistent.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

[jira] Updated: (CONTINUUM-2418) Status in Project Group Summary Page inconsistent with Build Results

2009-12-03T03:37:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Cordes updated CONTINUUM-2418:
-------------------------------------

Attachment: eai-deploy-helper-141-continuum.log

> Status in Project Group Summary Page inconsistent with Build Results
> --------------------------------------------------------------------
>
> Key: CONTINUUM-2418
> URL: http://jira.codehaus.org/browse/CONTINUUM-2418
> Project: Continuum
> Issue Type: Bug
> Components: Web - UI
> Affects Versions: 1.3.4
> Environment: Windows 2008 Server, Jdk 6
> Reporter: Stefan Cordes
> Attachments: eai-deploy-helper-141-continuum.log, eai-deploy-helper-build-result.gif, eai-deploy-helper-continuum.log, eai-deploy-helper-status.gif
>
>
> After Continuum is working a while the status in the
> Project Group Summary Page
> becomes inconsistent to the one in the
> Build Result Page.
> Sometimes the Group Summary shows "failed" but last build was sucessful or last build had never been executed (as in the attached example for eai-base-deploy-helper).
> Sometimes the Group Summary shows "in progress" but there is no build in progress.
> (A try to cancel says "Project is not in Build Queue", a try to Build says "Project is already in Build Queue").
> Workaround: Restart Continuum and Status is consistent.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

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

From forum: Continuum - Users

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

From forum: Continuum - Users

[jira] Commented: (CONTINUUM-2412) FileNotFoundException when adding Project and Server is under heavy load

2009-12-02T03:09:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200253#action_200253 ]

Stefan Cordes commented on CONTINUUM-2412:
------------------------------------------

Workaround is to put the pom file on a http:// server and use the field "M1 POM Url:"

> FileNotFoundException when adding Project and Server is under heavy load
> ------------------------------------------------------------------------
>
> Key: CONTINUUM-2412
> URL: http://jira.codehaus.org/browse/CONTINUUM-2412
> Project: Continuum
> Issue Type: Bug
> Components: Jetty Bundle
> Affects Versions: 1.3.4
> Environment: Windows Server 2008
> java version "1.6.0_17"
> Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
> Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing)
> Reporter: Stefan Cordes
> Priority: Minor
>
> Add a project via "Maven 1.x Project" and selecting a file in the local file system
> leads into a FileNotFoundException
> After several retries the project is added normally.
> java.lang.RuntimeException: java.io.FileNotFoundException: Source '.\tmp\Jetty_0_0_0_0_9080_continuum__continuum__.7gr0yc\upload__1d4e7c7c_1252b73f861__7ff5_00000032.tmp' does not exist
> at org.apache.maven.continuum.web.action.AddMavenProjectAction.execute(AddMavenProjectAction.java:178)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:404)
> at com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:267)
> at org.apache.struts2.interceptor.BackgroundProcess$1.run(BackgroundProcess.java:56)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.io.FileNotFoundException: Source '.\tmp\Jetty_0_0_0_0_9080_continuum__continuum__.7gr0yc\upload__1d4e7c7c_1252b73f861__7ff5_00000032.tmp' does not exist
> at org.apache.commons.io.FileUtils.copyFile(FileUtils.java:637)
> at org.apache.commons.io.FileUtils.copyFile(FileUtils.java:607)
> at org.apache.maven.continuum.web.action.AddMavenProjectAction.execute(AddMavenProjectAction.java:168)
> ... 8 more

From forum: Continuum - Issues

[jira] Updated: (CONTINUUM-2411) IndexOutOfBoundsException in DefaultContinuum.executeAddProjectsFromMetadataActivity

2009-12-01T22:30:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan updated CONTINUUM-2411:
-------------------------------------------

Fix Version/s: 1.3.5

> IndexOutOfBoundsException in DefaultContinuum.executeAddProjectsFromMetadataActivity
> ------------------------------------------------------------------------------------
>
> Key: CONTINUUM-2411
> URL: http://jira.codehaus.org/browse/CONTINUUM-2411
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.3.4
> Environment: Microsoft Windows [Version 6.0.6002] (Windows Server 2008)
> java version "1.6.0_17"
> Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
> Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing)
> Reporter: Stefan Cordes
> Priority: Minor
> Fix For: 1.3.5
>
>
> When adding a project to continuum via "Add Maven 1.x Project" and selecting a file the Exception
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> appears.
> This seems to be independend from the selected project.
> After the action the project is in the group anyway and can be build normally.
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> at java.util.ArrayList.RangeCheck(Unknown Source)
> at java.util.ArrayList.get(Unknown Source)
> at org.apache.maven.continuum.DefaultContinuum.executeAddProjectsFromMetadataActivity(DefaultContinuum.java:1735)
> at org.apache.maven.continuum.DefaultContinuum.executeAddProjectsFromMetadataActivity(DefaultContinuum.java:1777)
> at org.apache.maven.continuum.DefaultContinuum.addMavenOneProject(DefaultContinuum.java:1276)
> at org.apache.maven.continuum.web.action.AddMavenOneProjectAction.doExecute(AddMavenOneProjectAction.java:45)
> at org.apache.maven.continuum.web.action.AddMavenProjectAction.execute(AddMavenProjectAction.java:189)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:404)
> at com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:267)
> at org.apache.struts2.interceptor.BackgroundProcess$1.run(BackgroundProcess.java:56)
> at java.lang.Thread.run(Unknown Source)
>

From forum: Continuum - Issues

[jira] Created: (CONTINUUM-2417) Add username into build notification

2009-12-01T09:04:55Z

Add username into build notification
------------------------------------

Key: CONTINUUM-2417
URL: http://jira.codehaus.org/browse/CONTINUUM-2417
Project: Continuum
Issue Type: Bug
Reporter: Vasyl

Please add possibility adding username under what build was built into build notification mail or just "Schedule" if build was built by Schedule.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

[jira] Created: (CONTINUUM-2416) The cvs command failed.

2009-11-30T23:43:55Z

The cvs command failed.
-----------------------

Key: CONTINUUM-2416
URL: http://jira.codehaus.org/browse/CONTINUUM-2416
Project: Continuum
Issue Type: Bug
Components: SCM
Affects Versions: 1.2.3
Environment: OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: Deepak Chavan
Attachments: continuum.log

Unable to checkout the code from CVS

==================================================
2009-12-01 12:59:52,054 [pool-1-thread-1] INFO action#checkout-project - Checking out project: 'so-core-7.0.1-SNAPSHOT', id: '28' to 'C:\apache-continuum-1.2.3-bin\data\working-directory\28'.
2009-12-01 12:59:52,054 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Executing: cmd.exe /X /C "cvs -z3 -f -d :pserver:DChavan@...:/cvs/dev -q checkout -d 28 soprojects/smartoffice/so-core"
2009-12-01 12:59:52,054 [pool-1-thread-1] INFO org.apache.continuum.scm.manager.Slf4jScmLogger - Working directory: C:\apache-continuum-1.2.3-bin\data\working-directory
2009-12-01 12:59:52,804 [pool-1-thread-1] WARN action#checkout-project - Error while checking out the code for project: 'so-core-7.0.1-SNAPSHOT', id: '28' to 'C:\apache-continuum-1.2.3-bin\data\working-directory\28'.
2009-12-01 12:59:52,804 [pool-1-thread-1] WARN action#checkout-project - Command output:
2009-12-01 12:59:52,804 [pool-1-thread-1] WARN action#checkout-project - Provider message: The cvs command failed.
2009-12-01 12:59:52,835 [pool-1-thread-1] INFO buildController - Merging SCM results
2009-12-01 12:59:52,960 [pool-1-thread-1] INFO buildController - Error updating from SCM, not building
============================================================================================

SCM tag in pom.xml --

<scm>
<developerConnection>scm:cvs:pserver:DChavan:@${cvs.server}:/cvs/dev:soprojects/smartoffice/so-core</developerConnection>
<connection>scm:cvs:pserver:DChavan:c36l6n9g@${cvs.server}:/cvs/dev:soprojects/smartoffice/so-core</connection>
<url>http://${cvs.server}/cgi-bin/cvsweb.cgi/soprojects/smartoffice/so-core/?cvsroot=Dev</url>
</scm>

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

[jira] Created: (CONTINUUM-2415) Error while generating mail contents

2009-11-30T23:38:55Z

Error while generating mail contents
------------------------------------

Key: CONTINUUM-2415
URL: http://jira.codehaus.org/browse/CONTINUUM-2415
Project: Continuum
Issue Type: Bug
Components: Notifier - Mail
Environment: OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
Reporter: Deepak Chavan
Attachments: continuum.log

Error while sending mail notification in Apache-continuum-1.2.3

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2009-12-01 13:03:23,798 [pool-1-thread-1] ERROR org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher - Error while trying to use the mail notifier.
org.apache.maven.continuum.notification.NotificationException: Error while generating mail contents.
at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:391)
at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:288)
at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.sendMessage(MailContinuumNotifier.java:266)
at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:201)
at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:184)
at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96)
at org.apache.maven.continuum.buildcontroller.DefaultBuildController.endBuild(DefaultBuildController.java:244)
at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:198)
at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Unknown Source)
Caused by: org.apache.maven.continuum.installation.InstallationException: cli to get mvn version return code 1
at org.apache.continuum.installation.DefaultInstallationService.getExecutorConfiguratorVersion(DefaultInstallationService.java:436)
at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.getBuilderVersion(MailContinuumNotifier.java:472)
at org.apache.maven.continuum.notification.mail.MailContinuumNotifier.buildComplete(MailContinuumNotifier.java:364)
... 14 more

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

[jira] Assigned: (CONTINUUM-2380) Clarify Description of Build Agent Attributes

2009-11-30T23:38:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan reassigned CONTINUUM-2380:
----------------------------------------------

Assignee: Maria Catherine Tan (was: Maria Odea Ching)

> Clarify Description of Build Agent Attributes
> ---------------------------------------------
>
> Key: CONTINUUM-2380
> URL: http://jira.codehaus.org/browse/CONTINUUM-2380
> Project: Continuum
> Issue Type: Improvement
> Components: Distributed Builds, Documentation
> Affects Versions: 1.3.4
> Reporter: George Snyder
> Assignee: Maria Catherine Tan
> Fix For: 1.3.5
>
>
> http://continuum.apache.org/docs/1.3.4/installation/build-agent.html says:
> "Note that all of your agents need to be identical, as there is no way to
> control which agent Continuum chooses.."
> This paragraph needs to be rewritten in the context of Build Agent Groups. Presumably, all the agents within a group must be identical. Or do they just need to be consistent? For example, if all are using JDK 1.6.0_11, is it OK for them to specify different locations in 'continuum-buildagent.xml' (e.g. /usr/jdk/1.6.0_11 on one, /usr/java/1.6.0_11 on another, and so on)?
> Also, please clarify the effects of a Build Environment's Installations on a distributed Build Agent. Are the Installation values passed to the Build Agent? If so, do they override values in the agent's 'continuum-buildagent.xml', or vice versa?

From forum: Continuum - Issues

[jira] Closed: (CONTINUUM-2380) Clarify Description of Build Agent Attributes

2009-11-30T23:38:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan closed CONTINUUM-2380.
------------------------------------------

Resolution: Fixed

fixed in
r885681 of 1.3.x branch
r885683 of trunk

From forum: Continuum - Issues

[jira] Commented: (CONTINUUM-2373) Distributed Master needs more detailed logging

2009-11-30T18:44:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200077#action_200077 ]

Jevica Arianne B. Zurbano commented on CONTINUUM-2373:
------------------------------------------------------

Changes made in r884391:
* added the IDs of the project/group/release in the logs both in master and slave
* added more logs in some methods

> Distributed Master needs more detailed logging
> ----------------------------------------------
>
> Key: CONTINUUM-2373
> URL: http://jira.codehaus.org/browse/CONTINUUM-2373
> Project: Continuum
> Issue Type: Improvement
> Components: Distributed Builds
> Affects Versions: 1.3.4
> Reporter: Wendy Smoak
> Assignee: Jevica Arianne B. Zurbano
> Fix For: 1.4.0
>
>
> Watching the continuum.log file on the master with distributed builds enabled, I can't tell what projects are building or where they're going (to which agent).
> Here are some example log messages:
> 2009-09-28 08:05:11,467 [btpool0-6] INFO org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportClient - Checking if project group is in queue
> 2009-09-28 08:05:11,620 [btpool0-6] INFO org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportClient - Retrieving build size of agent
> 2009-09-28 08:05:11,649 [pool-10-thread-1] INFO org.apache.continuum.builder.distributed.executor.DistributedBuildProjectTaskExecutor - initializing buildContext
> 2009-09-28 08:05:13,380 [pool-10-thread-1] INFO org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportClient - Building projects.
> 2009-09-28 08:05:13,421 [btpool0-6] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Start prepare build.
> 2009-09-28 08:05:24,892 [btpool0-6] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Start prepare build.
> 2009-09-28 08:05:25,473 [pool-3-thread-1] INFO org.apache.continuum.distributed.transport.slave.SlaveBuildAgentTransportClient - Building projects.
> 2009-09-28 08:05:25,491 [btpool0-7] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Start prepare build.
> 2009-09-28 08:05:26,350 [btpool0-0] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Prepare build finished.
> 2009-09-28 08:05:26,503 [btpool0-0] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Start prepare build.
> 2009-09-28 08:05:26,507 [btpool0-7] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Retrieving environments
> 2009-09-28 08:05:26,883 [btpool0-7] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Checking if project should build
> 2009-09-28 08:05:27,080 [btpool0-7] INFO org.apache.continuum.builder.distributed.DefaultDistributedBuildService - The project build is forced, building
> 2009-09-28 08:05:27,101 [btpool0-7] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Start project build.
> 2009-09-28 08:05:27,368 [btpool0-7] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Start updating project
> 2009-09-28 08:05:32,119 [btpool0-6] INFO org.apache.continuum.distributed.transport.master.MasterBuildAgentTransportServer - Build result returned.
> These all need to say what project/group/agent is involved.
> It is not until a build finishes that you find out what project was building:
> 2009-09-28 08:05:32,120 [btpool0-6] INFO org.apache.continuum.builder.distributed.DefaultDistributedBuildService - update build result of project '1'

From forum: Continuum - Issues

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

From forum: Continuum - Users

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

From forum: Continuum - Users

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

From forum: Continuum - Users

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.

From forum: Continuum - Users

[jira] Created: (CONTINUUM-2414) need to document changes to wrapper.conf on upgrade

2009-11-29T16:45:55Z

need to document changes to wrapper.conf on upgrade
---------------------------------------------------

Key: CONTINUUM-2414
URL: http://jira.codehaus.org/browse/CONTINUUM-2414
Project: Continuum
Issue Type: Task
Components: Documentation
Affects Versions: 1.3.5
Reporter: Brett Porter

the new release moves to a new version of Jetty and changes the library contents listed in wrapper.conf. Anyone that has a copy of it in their $CONTINUUM_BASE directory (if separate from the installation) will need to update it with the one from the new distribution

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

[jira] Updated: (CONTINUUM-2414) need to document changes to wrapper.conf on upgrade

2009-11-29T16:45:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-2414:
------------------------------------

Fix Version/s: 1.3.5

> need to document changes to wrapper.conf on upgrade
> ---------------------------------------------------
>
> Key: CONTINUUM-2414
> URL: http://jira.codehaus.org/browse/CONTINUUM-2414
> Project: Continuum
> Issue Type: Task
> Components: Documentation
> Affects Versions: 1.3.5
> Reporter: Brett Porter
> Fix For: 1.3.5
>
>
> the new release moves to a new version of Jetty and changes the library contents listed in wrapper.conf. Anyone that has a copy of it in their $CONTINUUM_BASE directory (if separate from the installation) will need to update it with the one from the new distribution

From forum: Continuum - Issues

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

From forum: Continuum - Users

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.

From forum: Continuum - Users

Re: CONTINUUM-2391

2009-11-26T06:33:43Z

On Wed, Nov 25, 2009 at 10:57 PM, Gwen Harold Autencio
<gautencio@...> wrote:
> Build Env page.
> After setting the buildagentgroup of the profile. a list of buildagents of
> the buildagentgroup will be display under the installations area.
> And by clicking a buildagent from the list gives the user a list of the
> localRepositories of the buildagent. And the user can choose what localrepo
> will be used on that build env ?

How will it work when distributed builds is not enabled?

How will upgrades be handled? (The local repo selection is currently
done somewhere else, so there will be old data in the wrong place.)

--
Wendy

From forum: Continuum - Dev

[jira] Commented: (CONTINUUM-2413) Add Rest services

2009-11-26T03:06:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199562#action_199562 ]

Emmanuel Venisse commented on CONTINUUM-2413:
---------------------------------------------

I don't know yet how to implement it, but I'm looking actually at jersey+jaxb+jettison.

I wrote a "Hello world" app that support json and xml. I like it.

My test app is similar to http://weblog.plexobject.com/?p=1635

> Add Rest services
> -----------------
>
> Key: CONTINUUM-2413
> URL: http://jira.codehaus.org/browse/CONTINUUM-2413
> Project: Continuum
> Issue Type: New Feature
> Reporter: Emmanuel Venisse
> Fix For: Backlog
>
>
> All is in the summary :-)

From forum: Continuum - Issues

[jira] Commented: (CONTINUUM-2413) Add Rest services

2009-11-26T02:37:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199559#action_199559 ]

Brett Porter commented on CONTINUUM-2413:
-----------------------------------------

+1 :)

are you thinking JAX-RS sitting on top of the same layer as the XMLRPC, or something more foundational to the architecture?

From forum: Continuum - Issues

[jira] Updated: (CONTINUUM-2413) Add Rest services

2009-11-26T00:14:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated CONTINUUM-2413:
----------------------------------------

Fix Version/s: Backlog

From forum: Continuum - Issues

[jira] Created: (CONTINUUM-2413) Add Rest services

2009-11-26T00:14:55Z

Add Rest services
-----------------

Key: CONTINUUM-2413
URL: http://jira.codehaus.org/browse/CONTINUUM-2413
Project: Continuum
Issue Type: New Feature
Reporter: Emmanuel Venisse

All is in the summary :-)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Continuum - Issues

Re: Continuum 1.3.5

2009-11-26T00:08:04Z

I think too.

Maybe we can add CONTINUUM-2411 as it should be easy to fix

Emmanuel

On Thu, Nov 26, 2009 at 8:33 AM, Marica Tan <marica.tan@...> wrote:

> I think it's time to do another release for the 1.3.x branch and hopefully
> this will be the last :)
>
> There are 3 remaining issues in 1.3.5:
>
> CONTINUUM-2338 unable to export user db
> CONTINUUM-2380 clarify description of build agent attributes
> CONTINUUM-2394 current build result link is wrong with distributed build
> enabled
>
>
> I was thinking of dropping CONTINUUM-2338 from 1.3.5, but it seems like
> Brett moved it there for a reason so will leave it as is.
>
> Are there any more issues that should be fixed in 1.3.5 or issues that
> should not be in 1.3.5?
>
>
> Thanks,
> --
> Marica
>

From forum: Continuum - Dev

Continuum 1.3.5

2009-11-25T23:33:15Z

I think it's time to do another release for the 1.3.x branch and hopefully
this will be the last :)

There are 3 remaining issues in 1.3.5:

CONTINUUM-2338 unable to export user db
CONTINUUM-2380 clarify description of build agent attributes
CONTINUUM-2394 current build result link is wrong with distributed build
enabled

I was thinking of dropping CONTINUUM-2338 from 1.3.5, but it seems like
Brett moved it there for a reason so will leave it as is.

Are there any more issues that should be fixed in 1.3.5 or issues that
should not be in 1.3.5?

Thanks,
--
Marica

From forum: Continuum - Dev

[jira] Assigned: (CONTINUUM-2394) Current build result link is wrong with distributed build enabled

2009-11-25T22:42:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan reassigned CONTINUUM-2394:
----------------------------------------------

Assignee: Maria Catherine Tan

> Current build result link is wrong with distributed build enabled
> -----------------------------------------------------------------
>
> Key: CONTINUUM-2394
> URL: http://jira.codehaus.org/browse/CONTINUUM-2394
> Project: Continuum
> Issue Type: Bug
> Components: Web - UI
> Affects Versions: 1.3.5
> Reporter: Maria Catherine Tan
> Assignee: Maria Catherine Tan
> Fix For: 1.3.5
>
>

From forum: Continuum - Issues

Re: CONTINUUM-2391

2009-11-25T22:05:42Z

Yes, they are retrieved through xmlrpc.

Brett Porter wrote:

> Sounds ok to me... I guess getting the list will be interesting as you have to retrieve it over XMLRPC?
>
> On 26/11/2009, at 4:57 PM, Gwen Harold Autencio wrote:
>
>
>> Brett Porter wrote:
>>
>>> On 23/11/2009, at 3:53 PM, Gwen Harold Autencio wrote:
>>>
>>>
>>>
>>>> Build Agent
>>>> 1. Local repositories would be configured throught continuum-buildagent.xml
>>>>
>>>>
>>> ...
>>>
>>>
>>>> Master Agent
>>>> 1. Set the local repository in the build environments page that will be used by the build agent.
>>>>
>>>>
>>> What does this mean exactly? Can you paste how the config in continuum-buildagent.xml would look, and describe what fields / options would be added to the build env page for it?
>>>
>>> - Brett
>>>
>>>
>> In the config file of the build-agent maybe it will look something like this ?
>>
>> <continuum-buildagent-configuration>
>> <continuumServerUrl>http://localhost:8080/continuum/master-xmlrpc</continuumServerUrl>
>> <buildOutputDirectory>data/build-output-directory</buildOutputDirectory>
>> <workingDirectory>data/working-directory</workingDirectory>
>> <installations/>
>> <localRepositories>
>> <localRepository>
>> <name>test-one</name>
>> <location>/home/user/one</location>
>> <layout>default</layout> </localRepository>
>> <localRepository>
>> <name>test-two</name>
>> <location>/home/user/two</location>
>> <layout>default</layout> </localRepository>
>> </localRepositories>
>> </continuum-buildagent-configuration>
>>
>> Build Env page.
>> After setting the buildagentgroup of the profile. a list of buildagents of the buildagentgroup will be display under the installations area.
>> And by clicking a buildagent from the list gives the user a list of the localRepositories of the buildagent. And the user can choose what localrepo will be used on that build env ?
>>
>>
>
>
>

From forum: Continuum - Dev

Re: CONTINUUM-2391

2009-11-25T22:03:04Z

Sounds ok to me... I guess getting the list will be interesting as you have to retrieve it over XMLRPC?

On 26/11/2009, at 4:57 PM, Gwen Harold Autencio wrote:

> Brett Porter wrote:
>> On 23/11/2009, at 3:53 PM, Gwen Harold Autencio wrote:
>>
>>
>>> Build Agent
>>> 1. Local repositories would be configured throught continuum-buildagent.xml
>>>
>> ...
>>
>>> Master Agent
>>> 1. Set the local repository in the build environments page that will be used by the build agent.
>>>
>>
>> What does this mean exactly? Can you paste how the config in continuum-buildagent.xml would look, and describe what fields / options would be added to the build env page for it?
>>
>> - Brett
>>
> In the config file of the build-agent maybe it will look something like this ?
>
> <continuum-buildagent-configuration>
> <continuumServerUrl>http://localhost:8080/continuum/master-xmlrpc</continuumServerUrl>
> <buildOutputDirectory>data/build-output-directory</buildOutputDirectory>
> <workingDirectory>data/working-directory</workingDirectory>
> <installations/>
> <localRepositories>
> <localRepository>
> <name>test-one</name>
> <location>/home/user/one</location>
> <layout>default</layout> </localRepository>
> <localRepository>
> <name>test-two</name>
> <location>/home/user/two</location>
> <layout>default</layout> </localRepository>
> </localRepositories>
> </continuum-buildagent-configuration>
>
> Build Env page.
> After setting the buildagentgroup of the profile. a list of buildagents of the buildagentgroup will be display under the installations area.
> And by clicking a buildagent from the list gives the user a list of the localRepositories of the buildagent. And the user can choose what localrepo will be used on that build env ?
>

From forum: Continuum - Dev

[jira] Assigned: (CONTINUUM-2380) Clarify Description of Build Agent Attributes

2009-11-25T21:57:55Z

[ http://jira.codehaus.org/browse/CONTINUUM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Odea Ching reassigned CONTINUUM-2380:
-------------------------------------------

Assignee: Maria Odea Ching

> Clarify Description of Build Agent Attributes
> ---------------------------------------------
>
> Key: CONTINUUM-2380
> URL: http://jira.codehaus.org/browse/CONTINUUM-2380
> Project: Continuum
> Issue Type: Improvement
> Components: Distributed Builds, Documentation
> Affects Versions: 1.3.4
> Reporter: George Snyder
> Assignee: Maria Odea Ching
> Fix For: 1.3.5
>
>
> http://continuum.apache.org/docs/1.3.4/installation/build-agent.html says:
> "Note that all of your agents need to be identical, as there is no way to
> control which agent Continuum chooses.."
> This paragraph needs to be rewritten in the context of Build Agent Groups. Presumably, all the agents within a group must be identical. Or do they just need to be consistent? For example, if all are using JDK 1.6.0_11, is it OK for them to specify different locations in 'continuum-buildagent.xml' (e.g. /usr/jdk/1.6.0_11 on one, /usr/java/1.6.0_11 on another, and so on)?
> Also, please clarify the effects of a Build Environment's Installations on a distributed Build Agent. Are the Installation values passed to the Build Agent? If so, do they override values in the agent's 'continuum-buildagent.xml', or vice versa?

From forum: Continuum - Issues

Re: CONTINUUM-2391

2009-11-25T21:57:03Z

Brett Porter wrote:

> On 23/11/2009, at 3:53 PM, Gwen Harold Autencio wrote:
>
>
>> Build Agent
>> 1. Local repositories would be configured throught continuum-buildagent.xml
>>
> ...
>
>> Master Agent
>> 1. Set the local repository in the build environments page that will be used by the build agent.
>>
>
> What does this mean exactly? Can you paste how the config in continuum-buildagent.xml would look, and describe what fields / options would be added to the build env page for it?
>
> - Brett
>

In the config file of the build-agent maybe it will look something like this ?

<continuum-buildagent-configuration>
<continuumServerUrl>http://localhost:8080/continuum/master-xmlrpc</continuumServerUrl>
<buildOutputDirectory>data/build-output-directory</buildOutputDirectory>
<workingDirectory>data/working-directory</workingDirectory>
<installations/>
<localRepositories>
<localRepository>
<name>test-one</name>
<location>/home/user/one</location>
<layout>default</layout>
</localRepository>
<localRepository>
<name>test-two</name>
<location>/home/user/two</location>
<layout>default</layout>
</localRepository>
</localRepositories>
</continuum-buildagent-configuration>

Build Env page.
After setting the buildagentgroup of the profile. a list of buildagents of the buildagentgroup will be display under the installations area.
And by clicking a buildagent from the list gives the user a list of the localRepositories of the buildagent. And the user can choose what localrepo will be used on that build env ?

From forum: Continuum - Dev

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

From forum: Continuum - Users

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]

From forum: Continuum - Users