...
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
| UI Text Box |
|---|
type | warning| Note |
|---|
The steps below provide a workaround for the described problem. However, it is strongly discouraged to use this workaround in production as it can negatively impact the performance 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 |
|---|
|
To be able to handle more than 1000 aggregates, the following steps need to be performed: | Numbered Headings |
|---|
| Increase the stack size available to Java for both the Runtime and the customerdata serviceTo increase the default stack size available to Java, the following JVM parameter can be used. 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. Standalone jarIn the configuration of the customerdata service blueriq-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 |
JBoss EAPNewer 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 |
|---|
| language | xml |
|---|
| title | standalone.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 |
|---|
| language | xml |
|---|
| title | standalone.xml |
|---|
| <system-properties>
...
<property name="org.apache.coyote.http11.Http11Protocol.MAX_HEADER_SIZE" value="256000"/>
</system-properties> |
TomcatIn 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 |
|
| UI Expand |
|---|
|
| Content by Label |
|---|
|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | BKB |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ("customerdata","aggregatelist","aggregates") and type = "page" and space = "BKB" |
|---|
labels | customerdata aggregatelist aggregates