Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-884

2 split nodes one after the other causes an OutOfMemoryError in the document type xml parser


    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-3526Fix issue with Document Type XML parser where it isn't properly handling route paths that re-use a node definition
      KULRICE-3331Document Types with role nodes inside a branch node of a split node cannot be exported and re-ingested without causing DocumentType schema errors
      KULRICE-9386Issues with doctype xml ingestion
      KULRICE-3912if configured to route to a split or join, and that node is "requests" type, it silently fails
      KULRICE-766DocumentType versioning causes rare unique constraints on XML imports
      KULRICE-1130improve performance of xml ingestion
      KULRICE-2545introducting any split node in a document type sends document straight to final
      KULRICE-10874Application Document Status is not updated if the last route node is a simple node (not a join)
      KULRICE-5596Add support to Document Type XML schema to specify the krms integrating route node
      KULRICE-7038Rice Dev1: Document Type Inquiry Screen not Exporting Route Node Information
    • Rice Module:


      When there are 2 split nodes right after the other this can occur.


        There are no comments yet on this issue.


          • Assignee:
            Eric Westfall
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel