LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Index out of bounds: 0/0

    Employee
    Posted 03-21-2014 10:03

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: zon

    Hi,

    While running node Cross-Ref, I'm getting this error:

    -- Errors for Sort_2
    ERROR performing sort:
    index out of bounds: 0 / 0

    Installing log (03/21/2014 16:56:45) ...
    2014-03-21 16:57:02; Level: 2; Type: 0; Desc: "index out of bounds: 0 / 0"; File: "..\..\..\..\include\jigsaw\JtArray.h"; Line: 323; Context: "JtArray<>::GetAt()"
    2014-03-21 16:57:02; Level: 2; Type: 0; Desc: "...exception seen"; File: ".\BrainSort.cpp"; Line: 273; Context: "writeTempFile()"
    Uninstalling log (03/21/2014 16:57:02) ...


    Can you tell me what these means?
    The sort found some "sort" of strange charater that is enable to sort?

    Cheers,

    ZONOptimus


  • 2.  RE: Index out of bounds: 0/0

    Employee
    Posted 03-21-2014 11:46

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: DanRosenblatt

    This might indicate a configuration issue with the sort node.

    What version of LAE are you using, and how many records are in the input for the Sort node producing the error?


  • 3.  RE: Index out of bounds: 0/0

    Employee
    Posted 03-24-2014 08:50

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: zon

    BRE 4.5.1.0 Build 318 / LAE 4.5

    One input has 563.678, and the other one has 376.051.


  • 4.  RE: Index out of bounds: 0/0

    Employee
    Posted 03-24-2014 10:50

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: DanRosenblatt

    Thanks zon. It looks like you have encountered a defect in the way that the node handles buffered data when that data is close to the maximum size of the buffer (or a multiple thereof) that we resolved in version 4.5.4.

    However, you can still work around it in version 4.5.1.

    First, exit the LAE Server and BRE if either are running. Then open <LAE Installation Folder>\conf\brain\ls_brain_node.prop with a text editor, navigate to the Sort section, and either increase or decrease the value of the ls.brain.node.sort.maxBufferSize property in the file by a small number (to keep the same performance metrics) of about 10 or so record sizes (in bytes). For instance, the default setting is 30,000,000 bytes, so 30,020,000 will probably work in most cases. Then save the file, open BRE and the LAE Server and attempt to run the node. Note that this may take a bit of trial and error.

    If this does not resolve the issue, please see the guide to requesting Technical Support so we may investigate further.



  • 5.  RE: Index out of bounds: 0/0

    Employee
    Posted 04-09-2014 04:41

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: techm_aritra

    Hi
    I am getting the same error with version 4.6.1 while using Deep X-ref node


  • 6.  RE: Index out of bounds: 0/0

    Employee
    Posted 04-09-2014 08:34

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: DanRosenblatt

    Hi techm_aritra, I haven't been able to reproduce this error in 4.6.1 with the conditions from the documented cases we've seen with LAE 4.5 versions, so what you are seeing might be a separate issue. Please select the failing node in BRE, go to Help => Report Problem With a Node... and follow the instructions for creating a problem report. Then send a zip file of the files created by this process and to Technical Support so we may investigate further.