WildFly
  1. WildFly
  2. WFLY-974

"java.lang.IllegalStateException: Parameters processing failed" for IE browser only

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Out of Date Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Web (JBoss Web)
    • Security Level: Public (Everyone can see)
    • Labels:
    • Environment:
      Windows 7 Enterprise Service Pack 1, JDK-1.7.0_05, jboss-as-7.1.1.Final/jboss-eap-6.0.0(Evaluation)
    • Bugzilla Update:
      Perform
    • Similar Issues:
      Show 10 results 

      Description

      Application throws an exception for IE browser only with "JBoss-as-7.1.1.Final" & "JBoss-eap-6.0.0(Evaluation version)" only, but it is working correctly for Firefox browser.

      Note : It is working fine with "jboss-as-7.1.0.Final" version for all browsers.

      Exception details :
      Unhandled Exception / Error:

      Internal Error (757457307) at :: Exception (Parameters processing failed.)
      java.lang.IllegalStateException: Parameters processing failed.
      at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:407)
      at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:229)
      at org.apache.catalina.connector.Request.parseParameters(Request.java:2874)
      at org.apache.catalina.connector.Request.getParameterNames(Request.java:1333)
      at org.apache.catalina.connector.RequestFacade.getParameterNames(RequestFacade.java:379).........................

        Issue Links

          Activity

          Hide
          Melloware Inc
          added a comment -

          We have the exact same issue on JBoss EAP 6 Final (7.1.2 under the covers).

          Show
          Melloware Inc
          added a comment - We have the exact same issue on JBoss EAP 6 Final (7.1.2 under the covers).
          Hide
          Melloware Inc
          added a comment -

          The issue with parsing parameters can be found on line 333 of jbossweb 7.0.16:

          parseFailed = true;
          continue;
          // invalid chunk – it’s better to ignore

          So you can see they even had a comment saying its better to ignore, but flag the parsing as failed which later translates to an exception being thrown.

          Older code even had this (which is exactly what we are seeing):

          // No name eg ..&=xx&… will trigger this

          msg.append(“ignored.”);
          log.warn(msg);
          continue;
          // invalid chunk – it’s better to ignore

          So you can see it was added and the comment remains.

          Show
          Melloware Inc
          added a comment - The issue with parsing parameters can be found on line 333 of jbossweb 7.0.16: parseFailed = true; continue; // invalid chunk – it’s better to ignore So you can see they even had a comment saying its better to ignore, but flag the parsing as failed which later translates to an exception being thrown. Older code even had this (which is exactly what we are seeing): // No name eg ..&=xx&… will trigger this … msg.append(“ignored.”); log.warn(msg); continue; // invalid chunk – it’s better to ignore So you can see it was added and the comment remains.
          Hide
          jaikiran pai
          added a comment -

          Updated the component and the forum discussion fields.

          Show
          jaikiran pai
          added a comment - Updated the component and the forum discussion fields.
          Hide
          Jean-Frederic Clere
          added a comment -

          It is a regression of AS7-3898

          Show
          Jean-Frederic Clere
          added a comment - It is a regression of AS7-3898
          Hide
          Migore S
          added a comment -

          It also happens on Chrome Version 25.0.1364.97 m. Running on Windows 7.

          Show
          Migore S
          added a comment - It also happens on Chrome Version 25.0.1364.97 m. Running on Windows 7.
          Hide
          Tomaz Cerar
          added a comment -

          JbossWeb is no longer used in WildFly8.
          If same issue still occurs with Undertow, please create new issue.

          Show
          Tomaz Cerar
          added a comment - JbossWeb is no longer used in WildFly8. If same issue still occurs with Undertow, please create new issue.

            People

            • Assignee:
              Remy Maucherat
              Reporter:
              Vaibhav N
            • Votes:
              7 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: