[JBoss JIRA] Created: (TEIID-1663) Local Transactions not working
by Ramesh Reddy (JIRA)
Local Transactions not working
------------------------------
Key: TEIID-1663
URL: https://issues.jboss.org/browse/TEIID-1663
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4.1, 7.5
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 7.4.1, 7.5
while turning off the verbose comment of the suspend call, legitimate suspend call was also ignored to call, thus leading to
23:44:10,573 ERROR [PROCESSOR] Unexpected exception for request iQcf7D9ZVQ8h.0
java.lang.IllegalStateException: BaseTransaction.checkTransactionState - [com.arjuna.ats.internal.jta.transaction.arjunacore.alreadyassociated] [com.arjuna.ats.internal.jta.transaction.arjunacore.alreadyassociated] thread is already associated with a transaction!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (TEIID-1609) Delay required when get connection to admin deployed VDB
by Andriy Rokhmanov (JIRA)
Delay required when get connection to admin deployed VDB
--------------------------------------------------------
Key: TEIID-1609
URL: https://issues.jboss.org/browse/TEIID-1609
Project: Teiid
Issue Type: Bug
Affects Versions: 7.4
Environment: Windows 7, JBoss 5.1.0
Reporter: Andriy Rokhmanov
Assignee: Steven Hawkins
Priority: Minor
//Steps to reproduce (pseudo-code):
final AdminFactory adminFactory = AdminFactory.getInstance();
final Admin teiidAdmin = adminFactory.createAdmin("####",
"####".toCharArray(),"mms://127.0.0.1:31443"));
teiidAdmin.deployVDB("test-vdb.xml", ByteStreams.newInputStreamSupplier(vdbString.getBytes()).getInput());
teiidAdmin.close();
// Thread.sleep(500);
final TeiidDataSource teiidDataSource = new TeiidDataSource();
teiidDataSource.setDatabaseName("Chorus");
teiidDataSource.setUser("****");
teiidDataSource.setPassword("****");
// The next line causes exception:
Connection conn = teiidDataSource.getConnection();
CDT SEVERE [org.teiid.jdbc] (pool-6-thread-1) Could not create connection
org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69)
at org.teiid.jdbc.EmbeddedProfile.connect(EmbeddedProfile.java:58)
at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:105)
at org.teiid.jdbc.TeiidDataSource.getConnection(TeiidDataSource.java:234)
at org.teiid.jdbc.TeiidDataSource.getConnection(TeiidDataSource.java:215)
...
// Please note that the same code works fine in Teiid 7.3
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (TEIID-1599) Event based cache invalidation
by Mark Addleman (JIRA)
Event based cache invalidation
------------------------------
Key: TEIID-1599
URL: https://issues.jboss.org/browse/TEIID-1599
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
In addition to invalidating cached results by time, I'd like the ability to invalidate cache based on an event. I think this is the moral equivalent of the existing functionality to reset a materialized view. I would like to scope the invalidation to particular tables or sets of tables. For example, suppose I cached the results of the following statements:
SELECT * FROM A
SELECT * FROM B
SELECT * FROM A,B
A call to invalidate A would invalidate the cached result sets from the first and third statements.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (TEIID-1592) EventDeistributor is not initialized correctly
by Steven Hawkins (JIRA)
EventDeistributor is not initialized correctly
----------------------------------------------
Key: TEIID-1592
URL: https://issues.jboss.org/browse/TEIID-1592
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 7.4.1
In diagnosing TEIID-1591 the JNDI registration of the EventDistributor was prevented due to the proxy invocation handler not being serializable. This means that in a cluster mat view updates (just as prior to 7.4) and ddl modifications will not be distributed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month