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

eval() with 'or'ed facts causes serialization errors in org.drools.core.rule.EvalCondition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • 7.55.0.Final
    • None
    • None
    • 2021 Week 25-27 (from Jun 21)
    • Hide

      I have created a minimal reproduction here:

      https://github.com/fbraun4358/drools-serialization-bug-2

      Without serialization, the network works, with serialization we get an NPE.

      There are two tests. If switching to 6.5.0.Final then both will pass. If using 7.55.0.Final then the one with serialization will fail.

      Show
      I have created a minimal reproduction here: https://github.com/fbraun4358/drools-serialization-bug-2 Without serialization, the network works, with serialization we get an NPE. There are two tests. If switching to 6.5.0.Final then both will pass. If using 7.55.0.Final then the one with serialization will fail.
    • Undefined
    • NEW
    • NEW

      We are trying to move to drools 7 from drools 6.5.0.Final.

      When a rule contains an 'or' of multiple facts, and those we bind on a property of those facts, and then use that property in an eval(); the serialization and subsequent deserialization causes an NPE when trying to run the network.

      I was looking at the drools 7 docs and it does not look like there have been changes to what can and can't be done with eval() statements. We have stopped using them but we have a lot of legacy rules from a long time ago.

      I feel like I am logging a lot of bugs, 2 (sort of 3, a long time ago) for this move. We are probably not using drools in a very standard way. Let me know if these is a better way or if I should log these issues differently. I am also not sure if this should be critical, but it does cause "loss of data" in that it makes it impossible to serialize and then deseiralize the networks, i.e. data.

              mfusco@redhat.com Mario Fusco
              fbraun4358 Florian Braun (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: