Bug 807674
Summary: | JDBC Cache Stores using a JTA Data Source do not participate in cache transactions | ||
---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | mark yarborough <myarboro> |
Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.0.0 | CC: | chuffman, jdg-bugs, mgencur, pjha, ttarrant |
Target Milestone: | --- | ||
Target Release: | 7.0.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
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 and no workaround is currently available for this issue.
|
Story Points: | --- |
Clone Of: | 758178 | Environment: | |
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 758178 | ||
Bug Blocks: | 838946 |
Description
mark yarborough
2012-03-28 13:19:34 UTC
*** Bug 807675 has been marked as a duplicate of this bug. *** Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: When the JDBC Cache Store is configured without specifying connnectionFactoryClass, the ManagedConnectionFactory is selected by default. Consequence: ManagedConnectionFactory is unable to connect to the database. Fix: None Result: None Deleted Technical Notes Contents. Old Contents: Cause: When the JDBC Cache Store is configured without specifying connnectionFactoryClass, the ManagedConnectionFactory is selected by default. Consequence: ManagedConnectionFactory is unable to connect to the database. Fix: None Result: None Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: CCFR - Tristan Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -CCFR - Tristan+This issue does not apply to JDG Server since all cache operations are non-transactional. For library mode, the user should be aware that persistence to a JTA-aware cache store (JDBC) does not participate in the overall JTA transaction. Need clarification, tristan. It is not clear from the text what exactly is persisted and yet does not participate in the transaction. Can you clarify the blanks: Despite being made persistent to a JTA-aware cache store, ____ does not participate in the overall JTA transaction. Actually it's best to reword it as follows: 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. Is that clearer ? Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,2 @@ -This issue does not apply to JDG Server since all cache operations are non-transactional. For library mode, the user should be aware that persistence to a JTA-aware cache store (JDBC) does not participate in the overall JTA transaction.+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. This bug is nominated for JDG 6 GA Release Notes as a known issue. Given no further comments have occurred since Beta on this bug, I'm assuming that the current technical note outlining the problem remains valid. ttarrant will add jira links as appropriate. Per 2012-12-05 triage session with ttarrant, mgencur and company, this fix will break backward compatibility so must be moved to the next major release, JDG 7.0. In the meantime, it should continue to be noted in the release notes for JDG 6.1, etc... Setting flag in case we want to document this as a known issue for 6.2 release notes. |