[CONTINUUM-2369] Many warnings in logfile due to unknown struts actions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.4 (Beta)
• Fix Version/s: 1.5.0
• Labels: backlog-to-cleanup
• Environment: running in webapp on tomcat (.war file), SCM: Bazaar
• Assignee: Brent Atkinson
• Reporter: Martin Sudmann
• Created: 24/Sep/09 07:18
• Updated: 23/Feb/15 09:32
• Resolved: 23/Feb/15 09:32

Description

When I build a project, it gets stuck in the queue of ongoing builds on the build queue page. It never moves on and all other waiting builds are blocked as well.
When I restart tomcat, the build queue is empty, but the project still shows the button "cancel build" on the project group page.

Strange thing is, 3 builds succeeded earlier. Then one get stuck, and from there on every project stays in the ongoing build queue.

In the logs I see warnings about missing actions:

2009-09-24 09:53:49,508 [http-9090-1] WARN  org.apache.struts2.components.Form  - No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting to 'action' attribute's literal value.
2009-09-24 09:53:49,509 [http-9090-1] WARN  org.apache.struts2.components.Form  - No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting to 'action' attribute's literal value.
2009-09-24 09:53:49,512 [http-9090-1] WARN  org.apache.struts2.components.Form  - No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting to 'action' attribute's literal value.
2009-09-24 09:53:49,512 [http-9090-1] WARN  org.apache.struts2.components.Form  - No configuration found for the specified action: 'removePrepareBuildEntries.action' in namespace: ''. Form action defaulting to 'action' attribute's literal value.
2009-09-24 09:53:49,513 [http-9090-1] WARN  org.apache.struts2.components.Form  - No configuration found for the specified action: 'removePrepareBuildEntries.action' in namespace: ''. Form action defaulting to 'action' attribute's literal value.

I also have a lot of SCM errors, that seem to be due to the command "bzr log --verbose", whose results doesn't seem to interpreted correctly.

I attach the continuum.log file that starts when I restarted tomcat with 2 projects blocked in the build queue.

Issue Links

• is related to: CONTINUUM-2737 Projects using bazaar mayclog the prepare queue