Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-1755

Debugging of rules with MVEL dialect not working in multithreaded environment

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.3.0.Final
    • Fix Version/s: None
    • Component/s: eclipse plugin
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      SEE attached sample application

      • Create a simple rule file with an MVEL dialect set
      • Configure a breakpoint inside the rule file
      • Execute the rules inside an extra thread (not main thread) in Eclipse
      • The execution does not stop on the breakpoint
      • when the rules are executed in the main thread, the execution stops on breakpoint
      • when the dialect is JAVA, the execution stops on breakpoint when executed in the extra thread too
      Show
      SEE attached sample application Create a simple rule file with an MVEL dialect set Configure a breakpoint inside the rule file Execute the rules inside an extra thread (not main thread) in Eclipse The execution does not stop on the breakpoint when the rules are executed in the main thread, the execution stops on breakpoint when the dialect is JAVA, the execution stops on breakpoint when executed in the extra thread too
    • Affects:
      User Experience
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Run the rules in the main thread only when debugging

      Show
      Run the rules in the main thread only when debugging
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      The debugger does not stop on the breakpoint within a rule consequence when the dialect MVEL is used and the rule execution is done in an extra thread. The debugging is done in Eclipse using drools plugin installed. The project is a drools project and is debugged as drools application. See the attached application (drools-module.zip) to reproduce.

      When the rule execution is done in the main thread, the debugger stops on the breakpoint (workaround)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                bbrodt Robert (Bob) Brodt
                Reporter:
                pdurica Peter Durica
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: