Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8748

Insert into ExecutionErrorInfo table fails when the message is longer than 255 characters, but the RESTServiceException (and its long message) was created by RESTWorkItemHandler.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 7.24.0.Final
    • KieServer
    • None
    • NEW
    • NEW
    • Hide

      This error will happen for many use cases. Here is just one example:
      When RESTWorkItemHandler is configured to HandleResponseErrors and it tries to access a Rest Service with a wrong URL, it creates RESTServiceException with a message that is too long for the ERROR_MSG VARCHAR(255) column inside ExecutionErrorInfo table.

      Show
      This error will happen for many use cases. Here is just one example: When RESTWorkItemHandler is configured to HandleResponseErrors and it tries to access a Rest Service with a wrong URL, it creates RESTServiceException with a message that is too long for the ERROR_MSG VARCHAR(255) column inside ExecutionErrorInfo table.

      The message on the RESTServiceException thrown by RESTWorkItemHandler is useful but doesn't fit into ExecutionErrorInfo table. The error breaks the transaction.
      Here the end user doesn't have control on the lenght of the error message.
      Can you truncate long messages before trying to persist them?

        1. ErrorLogs.txt
          7 kB

            swiderski.maciej Maciej Swiderski (Inactive)
            jimwest362 Jim West (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: