ICEfaces
  1. ICEfaces
  2. ICE-10564

Multi-part server warning logged when application deployed onto WebLogic 12.1.3.0.0

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: EE-4.0.0.GA
    • Fix Version/s: EE-4.0.0.GA
    • Component/s: Sample Apps
    • Labels:
      None
    • Environment:
      ICEfaces EE-4.0.0 r41137 (all browsers), Weblogic 12.1.3.0.0, showcase and auction applications
    • Assignee Priority:
      P1
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

      Description

      When deploying showcase application to WebLogic 12.1.3.0.0 and upon every submit there is a server warning. This warning can be reproduced whether or not using the multipart config param in the web.xml file. Application demos do not appear to be affected.

      ####<Mar 11, 2015 2:20:51 PM EDT> <Warning> <HTTP> <ip-10-252-159-29.us-west-2.compute.internal> <ICEsoft_Administration_Server> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1426098051353> <BEA-101394> <The exception "The request content-type is not a multipart/form-data" occurred when processing getParameter or getParameterValues from a multipart value of a ServletRequest.>

        Activity

        Hide
        Mircea Toma added a comment - - edited

        Removing this

                <multipart-config>
                    <max-file-size>52428800</max-file-size>
                    <max-request-size>52428800</max-request-size>
                    <file-size-threshold>0</file-size-threshold>
                </multipart-config>
        

        from web.xml in showcase application gets rid of the warnings. I'm assuming that Weblogic expects all requests to be multipart/form-data.

        Show
        Mircea Toma added a comment - - edited Removing this <multipart-config> <max-file-size>52428800</max-file-size> <max-request-size>52428800</max-request-size> <file-size-threshold>0</file-size-threshold> </multipart-config> from web.xml in showcase application gets rid of the warnings. I'm assuming that Weblogic expects all requests to be multipart/form-data .
        Hide
        Liana Munroe added a comment - - edited

        The warnings were also visible when the multipart-config was removed from the web.xml

        Show
        Liana Munroe added a comment - - edited The warnings were also visible when the multipart-config was removed from the web.xml
        Hide
        Mircea Toma added a comment -

        I did re-test, once I removed the multipart-config and re-deployed I could not see the warnings anymore. Please make sure you indeed re-deployed the modified showcase app.

        Show
        Mircea Toma added a comment - I did re-test, once I removed the multipart-config and re-deployed I could not see the warnings anymore. Please make sure you indeed re-deployed the modified showcase app.
        Hide
        Liana Munroe added a comment -

        Tested using the auction application that does not use multipart-config in the web.xml and still had server warnings as listed in the description. Found that this server warning is a known issue on the latest version of WebLogic 12 (12.1.3.0.0). Testing the showcase application with the multipart-config in the web.xml using WebLogic 12.1.2.1 this warning is not seen.
        See here: http://stackoverflow.com/questions/27533105/application-logging-in-weblogic-12c-messed-up-after-upgrading-jdeveloper-from-12

        Show
        Liana Munroe added a comment - Tested using the auction application that does not use multipart-config in the web.xml and still had server warnings as listed in the description. Found that this server warning is a known issue on the latest version of WebLogic 12 (12.1.3.0.0). Testing the showcase application with the multipart-config in the web.xml using WebLogic 12.1.2.1 this warning is not seen. See here: http://stackoverflow.com/questions/27533105/application-logging-in-weblogic-12c-messed-up-after-upgrading-jdeveloper-from-12
        Hide
        Ken Fyten added a comment -

        As this is clearly an issue with the WebLogic 12.1.3.0.0 server, marking this won't fix. Work-around is to use an earlier WebLogic release, or a later one should become available that resolves this issue.

        Show
        Ken Fyten added a comment - As this is clearly an issue with the WebLogic 12.1.3.0.0 server, marking this won't fix. Work-around is to use an earlier WebLogic release, or a later one should become available that resolves this issue.

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Liana Munroe
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: