2:27 p.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2086:
----------------------------------
Fix Version/s: 8.2
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:19 p.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2086:
---------------------------------------
If TEIID-2158 is worked, then this should be resolved. We don't really care about
transactionality with the preparedplan cache, so we could also see about relaxing
awareness.
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2086:
-------------------------------------
I believe you meant TEIID-2168 in the above comment
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:42 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2086:
----------------------------------
Attachment: txn_cache.patch
Ramesh, can you take a look at this patch? Am I doing something obviously wrong with the
AS configuration?
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2086:
-------------------------------------
Looks ok to me without running the server, were you having any issues when you use this?
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:29 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2086:
---------------------------------------
Yes, the integration test is failing. The rollback does not effectively purge the cache
entry.
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2086.
-----------------------------------
Resolution: Done
This was slightly more complicated than I had hoped. In the AS environment the caches are
treated as services, not just the cache container. So without an explicit dependency on
the cache service just getting a cache from the container would automatically start a
defaultly configured cache.
So now there are explicit service dependencies and we use the embedded manager to ensure
that we don't auto create an inappropriately configured cache.
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:47 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2086:
-------------------------------------
That is bad IMO, the CacheContainer interface does have a method to grab the named caches,
I do not know the reasons why it would return a default cache. CacheContainer is a
abstraction over the EmbeddedCacheManager, it may already have the dependency on it. This
does not make sense to me -:(
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:01 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2086:
---------------------------------------
There is a mismatch between the infinispan logic and the infinispan configuration logic in
the container. You can get a handle to the CacheContainer service prior to configuration
of the caches. That CacheContainer is unaware it will configured asynchly by other
container threads. So if you ask for a named cache before that particular cache service
is configured you get the default one instead. I gather from all of this that they expect
you to depend on the caches and not the CacheContainer.
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2086:
-------------------------------------
I guess in that case they should have had service extension available at Cache level not
CacheContainer. This definitely improper usage of cache.
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:17 a.m.
[
https://issues.jboss.org/browse/TEIID-2086?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-2086.
---------------------------------
Local result set cache is not transactionally consistent
--------------------------------------------------------
Key: TEIID-2086
URL: https://issues.jboss.org/browse/TEIID-2086
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.2
Attachments: txn_cache.patch
Local result set cache entries are stored in a DefaultCache instance, which has no notion
of on-going transactions. This makes session or less deterministic entries read
uncommitted and possibly invalid if populated during a roll-back scenario.
We should either add transaction aware logic or switch the local cache to a memory based
infinispan instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4199
days inactive
4346
days old
11 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Steven Hawkins (JIRA)