continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brent N Atkinson (JIRA)" <j...@codehaus.org>
Subject [jira] (CONTINUUM-2369) warnings in logfile because of unknown actions
Date Mon, 23 Feb 2015 15:08:18 GMT

    [ https://jira.codehaus.org/browse/CONTINUUM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=363782#comment-363782
] 

Brent N Atkinson commented on CONTINUUM-2369:
---------------------------------------------

Thank you for the report. 

I believe you have reported multiple unrelated issues here. The warnings are unlikely to be
related to the project build blocking or the bzr scm operation. They are caused by problems
in Continuum's JSP pages. However, the volume of those messages makes it much more difficult
to comprehend what is in the log, which naturally makes it difficult to reason about what
might be happening.

I'm going to split this issue and address this one as titled. It may require more information
to address the blocked build.


> warnings in logfile because of unknown actions
> ----------------------------------------------
>
>                 Key: CONTINUUM-2369
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2369
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.3.4 (Beta)
>         Environment: running in webapp on tomcat (.war file), SCM: Bazaar
>            Reporter: Martin Sudmann
>            Assignee: Brent N Atkinson
>              Labels: backlog-to-cleanup
>             Fix For: 1.5.0
>
>         Attachments: continuum.log
>
>
> 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:
> {code}
> 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.
> {code}
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message