[JBoss JIRA] (TEIID-3400) Oracle connection not consistently usable after cancel
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3400?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3400:
---------------------------------------
Added a hook so that a cancelled oracle statement will have connection isvalid called on the statement close. This seems to clear whatever the issue is that causes later statements to fail. Will do more testing to ensure things look good.
> Oracle connection not consistently usable after cancel
> ------------------------------------------------------
>
> Key: TEIID-3400
> URL: https://issues.jboss.org/browse/TEIID-3400
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 8.10
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> With TEIID-3275 we made use of cancel calls more to ensure that cleanup was happening as quickly as possible. However Oracle JDBC has a bug (independently reproducible outside Teiid) where if the cancelled statement does not reach the point of thrown an exception related to the cancel, then the next statement from that connection will throw the exception.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIID-3400) Oracle connection not consistently usable after cancel
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3400:
-------------------------------------
Summary: Oracle connection not consistently usable after cancel
Key: TEIID-3400
URL: https://issues.jboss.org/browse/TEIID-3400
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Affects Versions: 8.10
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
With TEIID-3275 we made use of cancel calls more to ensure that cleanup was happening as quickly as possible. However Oracle JDBC has a bug (independently reproducible outside Teiid) where if the cancelled statement does not reach the point of thrown an exception related to the cancel, then the next statement from that connection will throw the exception.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIID-3398) Use Weka algorithm to caculate serializing, deserializing linear regression rate
by Kylin Soong (JIRA)
Kylin Soong created TEIID-3398:
----------------------------------
Summary: Use Weka algorithm to caculate serializing, deserializing linear regression rate
Key: TEIID-3398
URL: https://issues.jboss.org/browse/TEIID-3398
Project: Teiid
Issue Type: Feature Request
Components: Sizing Application
Reporter: Kylin Soong
Assignee: Kylin Soong
We have lots of data points {(size i, time i), i = 1, ..., n}, the goal is to find the equation of the straight line like
time = K * size
The key is to find the linear regression rate K, current we do not use any algorithm, Weka(http://sourceforge.net/projects/weka/) have algorithm to fine the K, we may use the Weka to enhance Sizing application
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3371:
---------------------------------------
We'll go ahead and issue an alpha1 this week regardless of the 6.4 alpha status.
> Upgrade Teiid with EAP 6.4 Alpha
> --------------------------------
>
> Key: TEIID-3371
> URL: https://issues.jboss.org/browse/TEIID-3371
> Project: Teiid
> Issue Type: Enhancement
> Components: Build/Kits
> Affects Versions: 8.11
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 8.11
>
> Attachments: diff.txt, status.txt
>
>
> Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years