Uploaded image for project: 'Continuum'
  1. Continuum
  2. CONTINUUM-2369

Many warnings in logfile due to unknown struts actions

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.3.4 (Beta)
    • 1.5.0
    • None
    • running in webapp on tomcat (.war file), SCM: Bazaar

    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.

      Attachments

        1. continuum.log
          193 kB
          Martin Sudmann

        Issue Links

          Activity

            People

              batkinson Brent Atkinson
              sudmannm Martin Sudmann
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: