[jira] [Updated] (GEODE-10006) Do not configure Geode JTA transaction management by default
[ https://issues.apache.org/jira/browse/GEODE-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10006: -- Priority: Critical (was: Major) > Do not configure Geode JTA transaction management by default > > > Key: GEODE-10006 > URL: https://issues.apache.org/jira/browse/GEODE-10006 > Project: Geode > Issue Type: Improvement >Reporter: John Blum >Priority: Critical > > Geode's built-in JTA transaction management and JNDI context registrations > are unnecessary unless Apache Geode is being used in the context of JTA > transactions (along with other JTA transactional compliant resources that > must all be associated with the same logical transaction) in the first place. > JTA is an overly complex application architectural design, is error prone to > use correctly at best, and with the advent of Microservices, has become > increasingly unpopular for managing consistency across 2 or more > transactional resources. > Additionally, Apache Geode's transaction manager should never be used as the > JTA transaction manager implementation. > The logic to initiate JTA transactional logic in Apache Geode resides in the > [JNDIInvoker|https://github.com/apache/geode/blob/rel/v1.14.3/geode-core/src/main/java/org/apache/geode/internal/jndi/JNDIInvoker.java] > class and > [initiated|https://github.com/apache/geode/blob/rel/v1.14.3/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java#L875](specifically, > > [here|https://github.com/apache/geode/blob/rel/v1.14.3/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java#L964]) > during cache creation and initialization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-10006) Do not configure Geode JTA transaction management by default
[ https://issues.apache.org/jira/browse/GEODE-10006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-10006: -- Summary: Do not configure Geode JTA transaction management by default (was: Remove default configuration of Geode JTA transaction management) > Do not configure Geode JTA transaction management by default > > > Key: GEODE-10006 > URL: https://issues.apache.org/jira/browse/GEODE-10006 > Project: Geode > Issue Type: Improvement >Reporter: John Blum >Priority: Major > > Geode's built-in JTA transaction management and JNDI context registrations > are unnecessary unless Apache Geode is being used in the context of JTA > transactions (along with other JTA transactional compliant resources that > must all be associated with the same logical transaction) in the first place. > JTA is an overly complex application architectural design, is error prone to > use correctly at best, and with the advent of Microservices, has become > increasingly unpopular for managing consistency across 2 or more > transactional resources. > Additionally, Apache Geode's transaction manager should never be used as the > JTA transaction manager implementation. > The logic to initiate JTA transactional logic in Apache Geode resides in the > [JNDIInvoker|https://github.com/apache/geode/blob/rel/v1.14.3/geode-core/src/main/java/org/apache/geode/internal/jndi/JNDIInvoker.java] > class and > [initiated|https://github.com/apache/geode/blob/rel/v1.14.3/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java#L875](specifically, > > [here|https://github.com/apache/geode/blob/rel/v1.14.3/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java#L964]) > during cache creation and initialization. -- This message was sent by Atlassian Jira (v8.20.1#820001)
