November 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2751) Add safer passthrough behavior wrt cancel/close

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2751?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2751. ----------------------------------- Resolution: Done Refined the reauth to: not be performed is there is no current session not be performed if it's a cancel call log an info message and logoff the old session if a new identity is associated with the thread If connection pooling is used with passthough and the info log is to be avoided, then explicit reauth handling would be required. > Add safer passthrough behavior wrt cancel/close > ----------------------------------------------- > > Key: TEIID-2751 > URL: https://issues.jboss.org/browse/TEIID-2751 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > In pass through authentication mode if another thread uses the connection another session is created without closing the previous. This may lead to unexpected behavior if attempting to use another thread to call close and creates an unnecessary session for cancel. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2751) Add safer passthrough behavior wrt cancel/close

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2751: ------------------------------------- Summary: Add safer passthrough behavior wrt cancel/close Key: TEIID-2751 URL: https://issues.jboss.org/browse/TEIID-2751 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.6 In pass through authentication mode if another thread uses the connection another session is created without closing the previous. This may lead to unexpected behavior if attempting to use another thread to call close and creates an unnecessary session for cancel. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2749) Dead links on About Teiid page

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2749?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2749. ----------------------------------- Resolution: Done Corrected all broken links I could find on that page. They all seemed to have an extra about path in them. I'm not sure why. It also doesn't look like magnolia will give you any indication of a broken link or a warning if you change stuff that would introduce a broken link (confluence is better in that regard). Will see if there is a link checker that we can run against the site. > Dead links on About Teiid page > ------------------------------ > > Key: TEIID-2749 > URL: https://issues.jboss.org/browse/TEIID-2749 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Radim Hopp > Assignee: Steven Hawkins > > Many links on About Teiid page (http://www.jboss.org/teiid/about.html) are dead. Mainly in Teiid Components section. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2750) Improve handling of messages that are too large

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2750?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2750. ----------------------------------- Resolution: Done Ensured proper server side logging (which means adding the message for detail/warning level). Increased the default max message size to 2 mb. Added a system property and documented it in the admin guide - org.teiid.maxMessageSize can adjust the max message size in bytes. And probably most important allows for these type of exceptions to be communicated to the client (8.6.0.Beta3/CR1+) without causing the connection to be dropped. > Improve handling of messages that are too large > ----------------------------------------------- > > Key: TEIID-2750 > URL: https://issues.jboss.org/browse/TEIID-2750 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > It is often unclear when a client message is too large. There is also no mechanism to allow for larger messages. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2749) Dead links on About Teiid page

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2749?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-2749: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) Sorry, nope don't have one. > Dead links on About Teiid page > ------------------------------ > > Key: TEIID-2749 > URL: https://issues.jboss.org/browse/TEIID-2749 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Radim Hopp > Assignee: Steven Hawkins > > Many links on About Teiid page (http://www.jboss.org/teiid/about.html) are dead. Mainly in Teiid Components section. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2747) Wrong results with merge join SORT_DISTINCT with a full sort that is distinct beyond the join columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2747?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2747: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1033056|https://bugzilla.redhat.com/show_bug.cgi?id=1033056] from ASSIGNED to MODIFIED > Wrong results with merge join SORT_DISTINCT with a full sort that is distinct beyond the join columns > ----------------------------------------------------------------------------------------------------- > > Key: TEIID-2747 > URL: https://issues.jboss.org/browse/TEIID-2747 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4.1, 8.6 > > > To speed up processing of a sort merge join we attempt to eliminate extra comparisons by detecting if the equi-join column values are distinct. In plans where the sorted values are distinct beyond the equi-join values such that the equi-join column values are non-distinct, then incorrect results can be returned. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2749) Dead links on About Teiid page

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2749?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2749: --------------------------------------- Van do you have a magnolia login to address this? > Dead links on About Teiid page > ------------------------------ > > Key: TEIID-2749 > URL: https://issues.jboss.org/browse/TEIID-2749 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Radim Hopp > Assignee: Van Halbert > > Many links on About Teiid page (http://www.jboss.org/teiid/about.html) are dead. Mainly in Teiid Components section. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2750) Improve handling of messages that are too large

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2750: ------------------------------------- Summary: Improve handling of messages that are too large Key: TEIID-2750 URL: https://issues.jboss.org/browse/TEIID-2750 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.6 It is often unclear when a client message is too large. There is also no mechanism to allow for larger messages. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2749) Dead links on About Teiid page

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2749?page=com.atlassian.jira.plugin... ] Van Halbert moved TEIIDDSHB-3 to TEIID-2749: -------------------------------------------- Project: Teiid (was: Teiid Dashboard) Key: TEIID-2749 (was: TEIIDDSHB-3) Component/s: Documentation (was: Documentation) > Dead links on About Teiid page > ------------------------------ > > Key: TEIID-2749 > URL: https://issues.jboss.org/browse/TEIID-2749 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Radim Hopp > Assignee: Van Halbert > > Many links on About Teiid page (http://www.jboss.org/teiid/about.html) are dead. Mainly in Teiid Components section. -- 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 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2730: ------------------------------------------------ belong(a)redhat.com made a comment on [bug 1028380|https://bugzilla.redhat.com/show_bug.cgi?id=1028380] Assigning this to Nilam, as it concerns the User Guide. > Cannot query Sybase database with jconn3.jar > -------------------------------------------- > > Key: TEIID-2730 > URL: https://issues.jboss.org/browse/TEIID-2730 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.4 > Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 8.6 > > Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar > > > In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar. > I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message: > TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0] > Console: > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0 > ============================================================================ > 10:55:07,362 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31 1:05:35 2009;IsolationLevel=2 > 10:55:07,555 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45] > at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'. > at com.sybase.jdbc3.tds.Tds.a(Unknown Source) > at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source) > at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) > at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) > at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) > at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source) > at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source) > at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84) > ... 13 more > 10:55:07,568 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'. > ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace. -- 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 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2013