Back to bug 807674
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| mark yarborough | 2012-03-28 13:21:15 UTC | Target Release | 6.0.0.ER6 | 6.1.0.GA |
| Tristan Tarrant | 2012-03-28 13:43:21 UTC | CC | ttarrant | |
| Tristan Tarrant | 2012-04-03 05:44:59 UTC | Summary | Jdbc cache stores do not work with ManagedConnectionFactory in a transactional context | JDBC Cache Stores using a JTA Data Source do not participate in cache transactions |
| Misha H. Ali | 2012-04-04 22:27:17 UTC | Flags | needinfo?(ttarrant) | |
| Tristan Tarrant | 2012-04-05 11:32:43 UTC | Flags | needinfo?(ttarrant) | |
| Tristan Tarrant | 2012-04-20 11:48:58 UTC | Priority | unspecified | low |
| Severity | high | low | ||
| mark yarborough | 2012-08-15 14:44:56 UTC | Version | 6.0.0.GA | 6.0.0 |
| mark yarborough | 2012-09-11 22:16:21 UTC | Doc Type | Bug Fix | Known Issue |
| Red Hat Bugzilla | 2012-09-11 22:16:21 UTC | Doc Type | Known Issue | Bug Fix |
| mark yarborough | 2012-11-14 14:42:13 UTC | Blocks | 838946 | |
| Target Milestone | --- | ER4 | ||
| mark yarborough | 2012-12-05 18:03:42 UTC | Target Release | 6.1.0 | 7.0.0 |
| Target Milestone | ER4 | --- | ||
| mark yarborough | 2013-02-05 22:48:13 UTC | Doc Text | In JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. | __KNOWN ISSUE for JDG 6.1 BETA__ In JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. |
| Doc Type | Bug Fix | Known Issue | ||
| Tristan Tarrant | 2013-06-26 09:27:43 UTC | Doc Text | __KNOWN ISSUE for JDG 6.1 BETA__ In JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However operations performed on a cache backed by such a store during a JTA transaction | In JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However |
| Doc Text | will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. | operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations | ||
| Doc Text | are non-transactional. | |||
| Status | NEW | ASSIGNED | ||
| Misha H. Ali | 2013-10-14 01:04:59 UTC | Doc Text | In JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. |
| Misha H. Ali | 2014-09-15 05:58:03 UTC | Doc Text | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.3.1. |
| Misha H. Ali | 2014-09-16 05:55:17 UTC | Doc Text | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.3.1. | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.3.1. No workaround is currently available for this issue. |
| Misha H. Ali | 2014-11-10 06:32:36 UTC | Doc Text | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.3.1. No workaround is currently available for this issue. | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.4 Beta. No workaround is currently available for this issue. |
| Misha H. Ali | 2015-01-19 01:00:49 UTC | Doc Text | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.4 Beta. No workaround is currently available for this issue. | In Red Hat JBoss Data Grid's library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction's scope. This issue is not applicable to JBoss Data Grid's Remote Client-Server mode because all cache operations are non-transactional. This is a known issue in JBoss Data Grid 6.4 and no workaround is currently available for this issue. |
| Christian Huffman | 2015-04-02 12:48:48 UTC | CC | chuffman | |
| PnT Account Manager | 2018-09-12 22:19:48 UTC | CC | gsheldon | |
| PnT Account Manager | 2018-09-12 22:30:10 UTC | CC | mhusnain |
Back to bug 807674