Skip to main content
D
dpstucson
Known Participant
March 15, 2012
Question

APSB12-06 and errors

  • March 15, 2012
  • 7 replies
  • 13123 views

Since applying the latest security patch I am receiving the below events and it has broken two of our apps.

03/15 11:54:38 error ROOT CAUSE:

coldfusion.filter.FormScope$PostParametersLimitExceededException: POST parameters exceeds the maximum limit specified in the server.

    at coldfusion.filter.FormScope.parseQueryString(FormScope.java:397)

    at coldfusion.filter.FormScope.parsePostData(FormScope.java:346)

    at coldfusion.filter.FormScope.fillForm(FormScope.java:296)

    at coldfusion.filter.FusionContext.SymTab_initForRequest(FusionContext.java:377)

    at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:33)

    at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)

    at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)

    at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:126)

    at coldfusion.CfmServlet.service(CfmServlet.java:200)

    at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)

    at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)

    at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)

    at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)

    at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)

    at jrun.servlet.FilterChain.service(FilterChain.java:101)

    at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)

    at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)

    at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)

    at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)

    at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)

    at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)

    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

javax.servlet.ServletException: ROOT CAUSE:

coldfusion.filter.FormScope$PostParametersLimitExceededException: POST parameters exceeds the maximum limit specified in the server.

    at coldfusion.filter.FormScope.parseQueryString(FormScope.java:397)

    at coldfusion.filter.FormScope.parsePostData(FormScope.java:346)

    at coldfusion.filter.FormScope.fillForm(FormScope.java:296)

    at coldfusion.filter.FusionContext.SymTab_initForRequest(FusionContext.java:377)

    at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:33)

    at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)

    at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)

    at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:126)

    at coldfusion.CfmServlet.service(CfmServlet.java:200)

    at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)

    at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)

    at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)

    at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)

    at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)

    at jrun.servlet.FilterChain.service(FilterChain.java:101)

    at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)

    at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)

    at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)

    at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)

    at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)

    at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)

    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

    at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:70)

    at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)

    at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)

    at jrun.servlet.FilterChain.service(FilterChain.java:101)

    at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)

    at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)

    at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)

    at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)

    at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)

    at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)

    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

03/15 11:54:38 error (JRun Service: ProxyService [jrun.servlet.jrpp.JRunProxyService@4c27d5bc]) JRunPRoxyServer.invokeRunnable:

java.lang.IllegalStateException

    at jrun.servlet.JRunResponse.getWriter(JRunResponse.java:205)

    at jrun.servlet.JRunResponse.sendError(JRunResponse.java:597)

    at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:328)

    at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)

    at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)

    at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)

    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

    This topic has been closed for replies.

    7 replies

    T
    tmessier
    Inspiring
    March 28, 2012

    I got it working, it was totally my fault. I searched my neo-runtime.xml file for postParametersLimit and found nothing so I added it after postSizeLimit per the instructions. Turns out my file did have a postParametersLimit in it, but it didn't come right after postSizeLimit so I didn't notice it and I must have searched for the wrong thing (probably forgot the "s" in "Parameters"). So after removing the duplicate entry, everything worked fine. Felt stupid wasting an hour on this, but it could have been worse if I hadn't spotted the duplicate!

    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    March 29, 2012

    Good to hear you resolved it. But you should now remove those CHF1 and 2 jar files you added (per your note in this thread at http://forums.adobe.com/message/4297879#4297879), when you had CHF 3 already. They are cumulative. You do not need the earlier ones if you install the later ones. And in that you also said in another message that you added CHF 4, you should remove the CHF 3 jar. But be careful to ONLY remove those that start with chf (for 1, 2, and 3), not any for HF (individual hotfixes) unless a technote tells you to remove them.

    /charlie

    /Charlie (troubleshooter, carehart. org)
    A
    Anonymous
    March 28, 2012

    tmessier - Do you get the "POST parameters exceeds the maximum limit" on every web page?

             The defaut size is 100 input parameters.  You can view the source of your page, right click on page - view source, and see how many "<input" parameters are on the page.  Remember you should have two "post" variables in the neo-runtime.xml file.  One specifies the size in MB of the page (or file being uploaded) and the other specifies the number of parameters that can be posted.  Make the "postParametersLimit" variable very big "9999.0" and see if this corrects the problem.  

              As a side not can someone tell me how to "paste" text into this forum reply box.  My "paste" button is grayed out.

    T
    tmessier
    Inspiring
    March 28, 2012

    Noticed the server I was working on didn't have either CHF 1 or 2 installed, so installed those as well. Still didn't solve the problem. Not feeling very lucky today.

    T
    tmessier
    Inspiring
    March 28, 2012

    Just tried installing Cumulative Hotfix 4 to see if it fixed it, it didn't.

    T
    tmessier
    Inspiring
    March 28, 2012

    Still no luck for me. I modified the neo-runtime.xml file as instructed. I also did as Charlie suggested and made sure I had Cummulative Hotfix 3 installed, which actually fixed some other problems I had, but I still have the "POST parameters exceeds the maximum limit specified in the server" error.

    A
    Anonymous
    March 22, 2012

    JR/"Bob" - is right.  You need to modify the "post parameters limit" variable in the neo-runtime.xml file:

            <var name='postParametersLimit'><number>100.0</number></var>

          But increase it from 100.0 to something "much" bigger.  I increased mine to 5000 due to my form processing requirements.

           This is the "number" of input parameters being posted from the form not the size.

          The post "size" variable is also in the neo-runtime.xml file as:

         <var name='postSizeLimit'><number>100.0<number></var>

          The post Size limit variable can be set from the Coldfusion Admin GUI but the post  Parameters limit has to be change in the xml and Coldfusion restarted.

           It appears that the APSB12-06 patch started enforcing the post Paramters limit setting.

           This corrected my problem but I am also probably going to redesign my page to use JQuery to reduce the number of input parameters on the form.

    pete_freitag
    pete_freitag
    Participating Frequently
    March 15, 2012

    Two things to check:  1) make sure that you followed the installation instructions properly, there are a few jar files that you need to delete from the updates dir - if you missed that step you might see that error.  2) Is the page where you get this the result of a large form post, eg over 100mb or over 100 form fields? If so then you need to adjust settings, this is described in the KB article associated with the hotfix.  Hope that helps

    --

    Pete Freitag

    http://hackmycf.com/ - Is your ColdFusion Server Secure?

      D
      dpstucsonAuthor
      Known Participant
      March 15, 2012

      Followed the installation to the letter.  I am very careful of that.  The error is from the logs folder cfusion-event.log.

      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert
      Community Expert
      March 16, 2012

      But the key question was: is the page that’s failing doing a post? And does the size exceed the limits? That’s the change that fix introduces.

      /charlie

      /Charlie (troubleshooter, carehart. org)
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices