Uploaded image for project: 'BxMS Documentation'
  1. BxMS Documentation
  2. BXMSDOC-2611

(6.4) Remove doc about org.kie.tx.lock.enabled

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.4
    • 6.4
    • JBPM Core

    Description

      Remove these 2 sections about "org.kie.tx.lock.enabled" because this property is no longer useful and is just risky (See https://access.redhat.com/solutions/1610723).

      https://access.redhat.com/documentation/en-us/red_hat_jboss_bpm_suite/6.4/html-single/administration_and_configuration_guide/index#list_of_system_properties

      org.kie.tx.lock.enabled
When enabled, Red Hat JBoss BPM Suite uses an interceptor that locks the KieSession to a single thread for the duration of a transaction, which prevents concurrency errors in Container Managed Transaction (CMT) environments.

Values	Default
true or false false

      https://access.redhat.com/documentation/en-us/red_hat_jboss_bpm_suite/6.4/html-single/development_guide/index#sect_kiesession

      WARNING
In cases when the Red Hat JBoss BPM Suite engine is managed within a Container-Managed Transaction (CMT) environment and the transactions are out of control of the engine, concurrent access to the same session instance may lead to errors. To handle this situation, an interceptor that locks KieSession for a single thread until the transaction completes is provided. This enables you to safely use knowledge sessions in a CMT environment.

To enable this interceptor, set both the org.kie.tx.lock.enabled system property and the TRANSACTION_LOCK_ENABLED environment entry to true. The default value of these properties is false.

      Attachments

        Activity

          People

            kaldesai Kalyani Desai
            rhn-support-tkobayas Toshiya Kobayashi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: