Home Forums Business Model BI Models Too many instances of "ReportDefinitionHierarchicalAttribute"

Viewing 3 reply threads
  • Author
    Posts
    • #486
      Wyuwyu
      Participant

      Too many instances of “ReportDefinitionHierarchicalAttribute” returned by a query: limit the count to 4,096 or use a cursor.

      When creating a new Ad-hoc report, if the custom field type number is more than 4096 (4k) and if I click the edit pen next to “Fields and Filters”, the following error will show in the console:

      Server invocation exception
      nexj.core.runtime.DataVolumeException: Too many instances of “ReportDefinitionHierarchicalAttribute” returned by a query: limit the count to 4,096 or use a cursor. (err.persistence.instanceCount)

      The error message seems to be straightforward and suggests us to implement paging for ReportDefinitionHierchicalAttribute read() method. The truth is paging is already there but the problem still exists.

      0
    • #488
      Vassiliy Iordanovvi
      Participant

      If paging is used, the count argument will be way under the read limit. You can find out the read argument values with the debugger, or, as we usually do, leaving the Generic RPC request/response logging permanently on during development.

      e.g. in NexJ Studio, add to VM args -Dlog4j.logger.nexj.core.rpc.GenericServer=ALL

      1
    • #490
      Wyuwyu
      Participant

      Thanks a lot vi,

      We partially solved the problem. The actual problem is there is a parent-children relationship in the ReportDefinitionHierarchicalAttribute class and the child nodes were queried through the object relationship by passing the read event.

      After we exlicitly set the childNodes attribute through a paged reading, the original issue fixed but there comes a new problem: when we choose one of the custom fields far down the node list of the custom field type, then click add, a new error shows something like: java.lang.NumberFormatException: Value out of range. Value:”68425″ Radix:10.

      Looks like the index is out of range for the destination list to hold. Is there is a way to solve this problem?

      Thanks a lot,

      Wen

      0
    • #492
      Vassiliy Iordanovvi
      Participant

      Have you got a stack trace?

      0
Viewing 3 reply threads
  • You must be logged in to reply to this topic.