Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-24962

Using REST methods with @FormParam causes misleading warnings in logs

XMLWordPrintable

      The REST api has a mismatch of Log Levels. The following debug (Level.FINE) log is displayed as a warning.

      [WARNING] [talledLocalContainer] WARNING: A servlet POST request, to the URI http://localhost:1990/confluence/rest/adhoclists/latest/boards/ds/addpage?type=LABEL&containerId=threat,&title=a%20threat&parentId=0, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

            [CONFSERVER-24962] Using REST methods with @FormParam causes misleading warnings in logs

            Stefan Hett added a comment -

            For the record: Retested in Confluence 5.3.4 and cannot reproduce there anymore either. Hence suspecting the issue was already resolved in that version.

            Stefan Hett added a comment - For the record: Retested in Confluence 5.3.4 and cannot reproduce there anymore either. Hence suspecting the issue was already resolved in that version.

            Vu Truong Vo (Inactive) added a comment -

            Hi All

            Thanks for taking the time to get in touch this issue. Regarding to https://confluence.atlassian.com/display/DOC/Bug+Fixing+Policy. The fixing will be archived into next release of Confluence. But in this case I will try to find a workaround if can this issue. We will update you guys shortly about our investigation .
            FYI : If you take time to upgrade, you should read https://confluence.atlassian.com/display/DOC/Confluence+Installation+and+Upgrade+Guide .

            Thanks and best regards,
            Vu Vo

            Vu Truong Vo (Inactive) added a comment - Hi All Thanks for taking the time to get in touch this issue. Regarding to https://confluence.atlassian.com/display/DOC/Bug+Fixing+Policy . The fixing will be archived into next release of Confluence. But in this case I will try to find a workaround if can this issue. We will update you guys shortly about our investigation . FYI : If you take time to upgrade, you should read https://confluence.atlassian.com/display/DOC/Confluence+Installation+and+Upgrade+Guide . Thanks and best regards, Vu Vo

            AndrewP added a comment -

            We are still seeing this issue. I believe that 4.3.2 is still supported so there should be a fix.

            AndrewP added a comment - We are still seeing this issue. I believe that 4.3.2 is still supported so there should be a fix.

            Francisco Villar Romasanta added a comment -

            Please fix this for 4.3.7 as we are unable to update to 5.x at the moment.

            Francisco Villar Romasanta added a comment - Please fix this for 4.3.7 as we are unable to update to 5.x at the moment.

            AndrewP added a comment -

            Upgrade is not a suficient answer for us because we do not have the resources to do this at the moment. Am I to believe that we just need o deal with an environment that tanks until we can upgrade???

            AndrewP added a comment - Upgrade is not a suficient answer for us because we do not have the resources to do this at the moment. Am I to believe that we just need o deal with an environment that tanks until we can upgrade???

            Angie Scott added a comment -

            Thanks for the resolution in 5.4, but I'm as high as I can go without an upgrade to SQL, which I'm investigating but not yet read to undertake. Is there no resolution for the rest of us until we upgrade?

            Angie Scott added a comment - Thanks for the resolution in 5.4, but I'm as high as I can go without an upgrade to SQL, which I'm investigating but not yet read to undertake. Is there no resolution for the rest of us until we upgrade?

            Steve Haffenden (Inactive) added a comment -

            Hi All

            Thanks for taking the time to report, comment and vote on this issue. This issue is resolved in Confluence 5.4 so upgrading to this version or higher should resolve this for you.

            Regards
            Steve Haffenden
            Confluence Bugmaster
            Atlassian

            Steve Haffenden (Inactive) added a comment - Hi All Thanks for taking the time to report, comment and vote on this issue. This issue is resolved in Confluence 5.4 so upgrading to this version or higher should resolve this for you. Regards Steve Haffenden Confluence Bugmaster Atlassian

            Maxfield B added a comment -

            I am also looking for a workaround or resolution. JIRA 5.1.3.

            Maxfield B added a comment - I am also looking for a workaround or resolution. JIRA 5.1.3.

            Angie Scott added a comment -

            Is there a work around or way to limit the logging? I have 5.2.5 installed, and I'm seeing this in my atlassian log.

            Angie Scott added a comment - Is there a work around or way to limit the logging? I have 5.2.5 installed, and I'm seeing this in my atlassian log.

            David Pierce added a comment -

            5.2.5

            David Pierce added a comment - 5.2.5

              vvo Vu Truong Vo (Inactive)
              f69cbac16f16 Ulrich Kuhnhardt
              Affected customers:
              60 This affects my team
              Watchers:
              60 Start watching this issue

                Created:
                Updated:
                Resolved: