Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-5192

Managed KIE Servers Don't Work with Latest EAP Jackson Security Patch

    XMLWordPrintable

Details

    • CR1
    • Hide

      Revert EAP to 6.4.19 and the issue doesn't exist

      Show
      Revert EAP to 6.4.19 and the issue doesn't exist
    • Hide

      1. Install EAP 6.4.20
      2. Install BPMS 6.4.10
      3. Uncomment managed kie server block in standalone.xml
      4. Start up EAP and see the errors in the logs and the kie server not appearing in the deploy section of business central

      Show
      1. Install EAP 6.4.20 2. Install BPMS 6.4.10 3. Uncomment managed kie server block in standalone.xml 4. Start up EAP and see the errors in the logs and the kie server not appearing in the deploy section of business central
    • 2018 Week 25-26

    Description

      Using latest EAP 6.4.20 and latest BPMS 6.4.10, if you turn on managed kie servers by uncommenting the block in the standalone.xml then you get lots of errors in the logs around jackson deserialization failures and the KIE server doesn't appear in the deploy section of business central. Its caused by one of these jackson "fixes" from EAP 6.4.20 patch: https://access.redhat.com/articles/3434081

      Attachments

        Issue Links

          is documented by

          Task - Represents a small unit of work that is not end-user facing. BXMSDOC-2868 Update BRMS and BPMS RN for 6.4 with the known issue in Managed KIE Servers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHBPMS-5205 Add jackson package whitelisting into domain.xml

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              rzhang+1@redhat.com Cheng Zhang (Inactive)
              ron.murhammer@amentra.com Ron Murhammer (Inactive)
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: