Versions Compared

Old Version 2

changes.mady.by.user Unknown User (m.woudstra)

Saved on

compared with

New Version Current

changes.mady.by.user Tijmen Daatselaar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrate text boxes

...

It is possible to construct filters on the aggregate list that result in a large number of aggregates (> 1000). To display these aggregates on the aggregate list, they need to be retrieved from the customerdata service. This is achieved by sending an OData compliant message to the customerdata service, which consists of a filter looking like this:

 

Code Block
http://<host>:<port>/customerdata/api/v1/Aggregates?$filter=(aggregateId = <...>) or (aggregateId = <...>) or ...)

...

When there are many aggregates (> 1000) this results in a very large call. The construction of this call, and the processing on the customerdata service side crashes when the number is larger than 1000 (it depends on the operating system and Java installation on what number exactly).
...
Please reconsider the modelling of the aggregate list and its filters to see if is possible to further limit the number of aggregates for that list. In most cases it does not make sense to model an aggregate list that displays so many records and if it does, it is likely to negatively impact the performance. When in doubt, please contact Blueriq support for help or discussing alternatives.
Workaround
 Note
 UI Text Box
typewarning
The steps below provide a workaround for the described problem. However, it is strongly discouraged to use this workaround in production as it will deteriorate performancecan negatively impact the performance of the whole Blueriq Runtime. You are advised to measure the (increased) memory usage of the Blueriq Runtime and Customerdata service and (re)size the RAM of the system accordingly. Blueriq cannot and will not guarantee acceptable performance with this workaround.
 UI Text Box
type
 Info
 The values for the parameters described below are established with a test for 6000 aggregates, on a Windows machine with the latest Java 8 version. The values specific to your environment may need additional tuning. In case they don't suffice, start by doubling them and try again.
...
 Panel
bgColor#fff
To be able to handle more than 1000 aggregates, the following steps need to be performed:
 Numbered Headings
start-numbering-ath3
Increase the stack size available to Java for both the Runtime and the customerdata service
To increase the default stack size available to Java, the following JVM parameter can be used.
 Code Block
-Xss16M
In this case, the stack size is set to 16 MB. This parameter needs be set for both the Runtime and the customerdata service. Please consult the documentation of your application server how to set this parameter on startup.
Increase the max http header size of the customerdata service
 Standalone jar
In the configuration of the customerdata service applicationblueriq-customerdata-odata-service-v1.yml, located in the 
 Include Page
DOC:_ConfigLocation
DOC:_ConfigLocation
, set the following property:
 Code Block
server:
 max-http-header-size: 256000
 
 
 
 
 
 UI Expand
titleRelated articles
 Content by Label
showLabelsfalse
max5
spacesBKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("customerdata","aggregatelist","aggregates") and type = "page" and space = "BKB"
labelscustomerdata aggregatelist aggregates
 
...
JBoss EAP
Newer versions (JBoss EAP 7.0 and newer), with Undertow as servlet container can use the code below. Note that the default value for the max header size is 1 MB in Undertow.
 Code Block
languagexml
titlestandalone.xml
<subsystem xmlns="urn:jboss:domain:undertow:1.2">
  ...
  <server name="default-server">
    <http-listener name="default" ... max-header-size="256000"/>
    ...
  </server>
  ...
</subsystem>

Older versions (until JBoss EAP 6.4.0), with Tomcat as Servlet container, can use the code below. Note that the default value for the max header size is 8 KB in Tomcat.
 Code Block
languagexml
titlestandalone.xml
<system-properties>
  ...
  <property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="256000"/>
</system-properties>
Tomcat
In server.xml, you can add an attribute maxHttpHeaderSize=256000 to the Connector that is used for the CDS. Note that the default value for this is 8 KB in Tomcat.
More information: https://tomcat.apache.org/tomcat-9.0-doc/config/http.html, https://tomcat.apache.org/tomcat-10.1-doc/config/http.html
...