Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-2771

Ruleflow broken inside BusinessRulesProcessor

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 5.1.0.ER6, 5.1.0.ER7
    • Fix Version/s: 5.1.0.CR1, 5.1.0 GA
    • Component/s: JBossESB
    • Labels:
      None
    • Environment:

      Fedora 14, OpenJDK.

    • Affects Testing:
      Regression
    • Release Notes Text:
      Hide
      RuleFlow would sometimes not execute correctly inside of the BusinessRulesProcessor ESB action. This was because it was running in a stateless session instead of a stateful session as would be normally be expected. The stateless session handling code has been updated to handle this type of scenario better.
      Show
      RuleFlow would sometimes not execute correctly inside of the BusinessRulesProcessor ESB action. This was because it was running in a stateless session instead of a stateful session as would be normally be expected. The stateless session handling code has been updated to handle this type of scenario better.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      The following ruleflow (see attachment) doesn't execute properly inside BusinessRulesProcessor action. There are no exceptions in the log, just the following:

      2011-01-14 10:13:15,400 DEBUG [org.jboss.soa.esb.lifecycle.LifecycleResource] (pool-46-thread-1) Creating resource using factory: org.jboss.internal.soa.esb.services.rules.DroolsRuleService$LifecycleRuleBaseStateFactory@41be1cac with identity ID-14
      2011-01-14 10:13:15,413 DEBUG [org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseState] (pool-46-thread-1) created new stateless session [1639720667]
      2011-01-14 10:13:15,413 DEBUG [org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseState] (pool-46-thread-1) created new runtime logger [1524320920]
      2011-01-14 10:13:15,413 DEBUG [org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseState] (pool-46-thread-1) calling execute(Iterable) on stateless session [1639720667]
      2011-01-14 10:13:15,434 INFO [STDOUT] (pool-46-thread-1) startRuleFlow
      2011-01-14 10:13:15,435 INFO [STDOUT] (pool-46-thread-1) rfg1a
      2011-01-14 10:13:15,437 INFO [STDOUT] (pool-46-thread-1) rfg1b
      2011-01-14 10:13:15,437 DEBUG [org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseState] (pool-46-thread-1) calling close() on runtime logger [1524320920]
      2011-01-14 10:13:15,509 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] (pool-46-thread-1) executing processor 1 org.jboss.soa.esb.samples.quickstart.businessrules5jbqa1855.ReviewMessage@9e69443

      See that after the activation of rfg1b, the ruleflow simply exits while it should do a lot more stuff, mainly activate rfg2a and rfg4. When launched from Guvnor deployed into the very same SOA instance, it works fine.

      Attached is:
      1) A RuleFlow and a subflow that is supposed to be called.
      2) The DRL file containing all the ruleflow groups and their rules.
      3) Audit log from the Drools execution, showing that it simply ends after rfg1b.
      4) The ESB archive with the quickstart. Mmay need some tweaking - mainly to update the path to the audit log in jboss-esb.xml and to update agent.pkg.properties to point to the Drools package. (Also packaged inside the archive.)

        Gliffy Diagrams

          Attachments

          1. business_rules_service5_jbqa-1855.log
            9 kB
          2. business_rules_service5_qe.tar.bz2
            33 kB
          3. defaultPackage.pkg
            34 kB
          4. drools-core-5.1.0.BRMS.jar
            2.01 MB
          5. drools-core-5.1.0.BRMS.jar
            2.01 MB
          6. LATEST.drl
            1 kB
          7. Quickstart_business_rules_service5_jbqa-1855.esb
            12 kB
          8. repository_export.zip
            19 kB
          9. ruleflowIntg.rf
            3 kB
          10. subruleflowIntg.rf
            0.8 kB

            Issue Links

            is blocked by

            Bug - A problem which impairs or prevents the functions of the product. BRMS-542 Ruleflow broken inside BusinessRulesProcessor

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

            Task - A task that needs to be done. SOA-2841 Backport BRMS issues for inclusion in SOA

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  kconner Kevin Conner
                  Reporter:
                  lpetrovicky Lukáš Petrovický
                  Writer:
                  Dana Mison
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: