Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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).

...

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

In the configuration of the customerdata service application.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

 

...