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

RouteManagerException: PostProcessor failed to process document

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.1.3
    • Fix Version/s: 2.1.4, 2.2.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-862Allow for PostProcessor to dictate retry and exception routing behavior
      KULRICE-2116WorkflowDocument.logDocumentAction should not contact PostProcessor
      KULRICE-4312documents are not getting successfully requeued and processed on a rule change
      KULRICE-8559When routing a doc with no route path defined, document goes FINAL but PostProcessor is never called
      KULRICE-13539Document IT Failure analysis processes
      KULRICE-4109StandardWorkflowEngine::process() throws optimistic lock exceptions
      KULRICE-7640Custom Action List processing throws NPE when processing KFS CustomActionListAttribute
      KULRICE-9383Update wiki page on documentation processes
      KULRICE-13783Document AFT Failure analysis processes
      KULRICE-4936define process to assign work when tests start failing
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Upon MySQLIntegrityConstraintViolationException: Duplicate entry document is not able to successfully perform placeInExceptionRouting. Document is left in Route Status ENROUTE.

        Issue Links

          Activity

          Hide
          Corey Pedersen (Inactive) added a comment -

          corey pedersen: @Matt: functional question. Currently if you use a maintenance docuement to make a change(such as create a permission). Rice will create a document and use workflow processing when you submit. The issue is if you have an error in the document(such as duplicate permission name) the message being processed by the workflow has it's status code change to exception, BUT the document still shows ENROUTE. It looks hung in processing. It seems like the doument should be set to Exception.

          corey pedersen: KULRICE-8674 & KULRICE-8644

          Matt Sargent: Yeah, the doc should be set to exception. Is there anything in there with locks that aren't released due to the doc being left ENROUTE as well? That may not be the case here, but in most apps if the doc is ENROUTE there are subject locks in place that aren't released until the status is FINAL, PROCESSED, CANCELED, or EXCEPTION. Seems like this would help out in those cases as well.

          Show
          Corey Pedersen (Inactive) added a comment - corey pedersen: @Matt: functional question. Currently if you use a maintenance docuement to make a change(such as create a permission). Rice will create a document and use workflow processing when you submit. The issue is if you have an error in the document(such as duplicate permission name) the message being processed by the workflow has it's status code change to exception, BUT the document still shows ENROUTE. It looks hung in processing. It seems like the doument should be set to Exception. corey pedersen: KULRICE-8674 & KULRICE-8644 Matt Sargent: Yeah, the doc should be set to exception. Is there anything in there with locks that aren't released due to the doc being left ENROUTE as well? That may not be the case here, but in most apps if the doc is ENROUTE there are subject locks in place that aren't released until the status is FINAL, PROCESSED, CANCELED, or EXCEPTION. Seems like this would help out in those cases as well.
          Hide
          Corey Pedersen (Inactive) added a comment -

          Replacing RiceRuntimeException in ExceptionRoutingServiceImpl.placeInExceptionRouting method with LOG.warn(...) to allow document to be placed in Exception status and allowing inException document to be unlocked in MaintenanceDocumentBase.doRouteStatusChange method.

          Show
          Corey Pedersen (Inactive) added a comment - Replacing RiceRuntimeException in ExceptionRoutingServiceImpl.placeInExceptionRouting method with LOG.warn(...) to allow document to be placed in Exception status and allowing inException document to be unlocked in MaintenanceDocumentBase.doRouteStatusChange method.
          Hide
          Corey Pedersen (Inactive) added a comment -

          Committed revision 37474. Fixed

          Show
          Corey Pedersen (Inactive) added a comment - Committed revision 37474. Fixed

            People

            • Assignee:
              Corey Pedersen (Inactive)
              Reporter:
              Corey Pedersen (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel