This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
  • RSA.com
  • Home
  • Advisories
    • SecurID
    • SecurID Governance & Lifecycle
  • Documentation
    • SecurID
      • Authentication Agents
        • API / SDK
        • Apache Web Server
        • Citrix StoreFront
        • IIS Web Server
        • MFA Agent for macOS
        • MFA Agent for Windows
        • Microsoft AD FS
        • Microsoft Windows
        • PAM
      • Authentication Engine
      • Authentication Manager
      • Cloud Authentication Service
      • Hardware Appliance
        Component Updates
      • Hardware Tokens
      • Integrations
      • SecurID App
      • SecurID Authenticator for macOS
      • SecurID SDK
      • Software Tokens
        • Android
        • iOS
        • macOS
        • Token Converter
        • Windows
    • SecurID Governance & Lifecycle
    • Technology Partners
  • Downloads
    • SecurID
      • Authentication Agents
        • API / SDK
        • Apache Web Server
        • Citrix StoreFront
        • IIS Web Server
        • MFA Agent for macOS
        • MFA Agent for Windows
        • Microsoft AD FS
        • Microsoft Windows
        • PAM
      • Authentication Engine
      • Authentication Manager
      • Cloud Authentication Service
      • Hardware Appliance
        Component Updates
      • Hardware Tokens
      • Integrations
      • SecurID Authenticator for macOS
      • Software Tokens
        • Android
        • iOS
        • macOS
        • Token Converter
        • Windows
    • SecurID Governance & Lifecycle
  • Community
    • SecurID
      • Blog
      • Discussions
      • Events
      • Idea Exchange
      • Knowledge Base
    • SecurID Governance & Lifecycle
      • Blog
      • Discussions
      • Events
      • Idea Exchange
      • Knowledge Base
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Ideas & Suggestions
      • Community Support Articles
      • Community Support Forum
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Education
    • Blog
    • Browse Courses
      • SecurID
      • SecurID Governance & Lifecycle
    • Certification Program
    • New Product Readiness
    • Student Resources
Sign In Register Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SecurID® Governance & Lifecycle Knowledge Base

Find answers to your questions and identify resolutions for known issues with knowledge base articles written by SecurID Governance & Lifecycle experts.
  • SecurID Community
  • :
  • Products
  • :
  • SecurID Governance & Lifecycle
  • :
  • Knowledge Base
  • :
  • 'UT000047: The number of parameters exceeded the maximum of 1000' error when scheduling collectors i...
  • Options
    • Subscribe to RSS Feed
    • Bookmark
    • Subscribe
    • Email to a Friend
    • Printer Friendly Page
    • Report Inappropriate Content

'UT000047: The number of parameters exceeded the maximum of 1000' error when scheduling collectors in RSA Identity Governance & Lifecycle

Article Number

000032577

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle 
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.x
Platform (Other):  WildFly
 

Issue

When scheduling multiple collectors via Collectors > Scheduling in RSA Identity Governance & Lifecycle, the page does not respond properly and the following error is thrown in the aveksaServer.log:
 
06/14/2017 21:21:40.958 ERROR (default task-355) [com.aveksa.gui.core.filters.LoginFilter] java.lang.IllegalStateException: UT000047: The number of parameters exceeded the maximum of 1000 at io.undertow.server.handlers.form.FormData.add(FormData.java:77) at io.undertow.server.handlers.form.FormData.add(FormData.java:67) at io.undertow.server.handlers.form.FormEncodedDataDefinition$FormEncodedDataParser.doParse(FormEncodedDataDefinition.java:172) at io.undertow.server.handlers.form.FormEncodedDataDefinition$FormEncodedDataParser.parseBlocking(FormEncodedDataDefinition.java:251) at io.undertow.servlet.spec.HttpServletRequestImpl.parseFormData(HttpServletRequestImpl.java:752) at io.undertow.servlet.spec.HttpServletRequestImpl.getParameter(HttpServletRequestImpl.java:626) at javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194) at com.aveksa.gui.util.security.XSSRequestWrapper.getParameter(XSSRequestWrapper.java:65)

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment.
 

Cause

The issue occurs if you have more than 100 collectors of the same collector type. Each collector holds approximately ten parameters and having more than 100 collectors for any collector type may exceed the WildFly application server default maximum parameters threshold of 1000 (100 x 10).

This is a known issue reported in engineering ticket ACM-65063.
 

Resolution

This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
  • RSA Identity Governance & Lifecycle 7.0.0 P05
  • RSA Identity Governance & Lifecycle 7.0.1 P01
  • RSA Identity Governance & Lifecycle 7.0.2

Workaround

As a workaround, the WildFly application server default maximum parameter setting of 1000 may be increased. To determine the correct value to use, multiply the number of collectors of the same type by ten. For example, if you have 300 collectors for a given collector type, set the maximum parameter value to 3000.

Please refer to RSA Knowledge Base Article 000038261 -- How to modify the WildFly application server default maximum parameter setting of 1000 in RSA Identity Governance & Lifecycle for instructions on how to modify this value.
 
Tags (58)
  • 7
  • 7.0
  • 7.0 P1
  • 7.0 P2
  • 7.0 Patch 1
  • 7.0 Patch 2
  • 7.0.0
  • 7.0.0.x
  • 7.0.1
  • 7.0.1.x
  • 7.0.2
  • 7.0.2.x
  • 7.0.x
  • 7.x
  • Aveksa
  • Break Fix
  • Break Fix Issue
  • Broken
  • Collection
  • Collector
  • Config
  • Configuration
  • Configuration Help
  • Configuration Issue
  • Configuration Problem
  • Configuring Issue
  • Configuring Problem
  • Customer Support Article
  • Data Collection
  • Data Collector
  • Identity
  • Identity G&L
  • Identity Governance & Lifecycle
  • Identity Governance and Lifecycle
  • IG&L
  • IGL
  • Issue
  • Issue Configuring
  • Issues
  • KB Article
  • Knowledge Article
  • Knowledge Base
  • Problem
  • RSA Identity
  • RSA Identity G&L
  • RSA Identity Governance & Lifecycle
  • RSA Identity Governance and Lifecycle
  • Setup Issue
  • Version 7
  • Version 7.0
  • Version 7.0.0
  • Version 7.0.0.x
  • Version 7.0.1
  • Version 7.0.1.x
  • Version 7.0.2
  • Version 7.0.2.x
  • Version 7.0.x
  • Version 7.x
0 Likes
Was this article helpful? Yes No
Share
No ratings

In this article

Version history
Last update:
‎2020-12-12 12:48 PM
Updated by:
Administrator RSA-KB-Sync Administrator

Related Content

Powered by Khoros
  • Blog
  • Events
  • Discussions
  • Idea Exchange
  • Knowledge Base
  • Case Portal
  • Community Support
  • Product Life Cycle
  • Support Information
  • Customer Success
  • About the Community
  • Terms & Conditions
  • Privacy Statement
  • Provide Feedback
  • Employee Login
© 2022 RSA Security LLC or its affiliates. All rights reserved.