May 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2505) MultiArrayOutputStream computes count incorrectly

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2505: ------------------------------------- Summary: MultiArrayOutputStream computes count incorrectly Key: TEIID-2505 URL: https://issues.jboss.org/browse/TEIID-2505 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 8.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Blocker Fix For: 8.4 The count computed may not be correct when the bytes written exceeds the primary array size. This impacts teiid in client to server messaging when the client message exceeds 1 < 15 bytes - which is uncommon, but can happen with extremely large sql, large directly bound (not stream) values, etc. The exception produced will be shown as "Connection reset". The server will log the exception as an EOFException - but at a detail level since we assume that IOExceptions can be logged at a lower level. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2502: --------------------------------------- Can you run with detail logging enabled to see if you are getting a stack trace associated with a message such as "Unhandled exception, closing client instance"? > org.teiid.net.socket.SingleInstanceCommunicationException > --------------------------------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Critical > > I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial. > I'm getting the following error in SquirrelSQL > Error: org.teiid.net.socket.SingleInstanceCommunicationException > SQLState: 08S01 > ErrorCode: 0 > Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get: > Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed > SQLState: TEIID20013 > ErrorCode: 0 > I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type. > Probably it doesn't like it too much. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2503) XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2503?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2503: ---------------------------------- Priority: Minor (was: Critical) Dropping to minor priority as recursive xml documents to my knowledge have not been used in years. > XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error" > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2503 > URL: https://issues.jboss.org/browse/TEIID-2503 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: EAP6.1Alpha and Teiid8.4Alpha > Reporter: Warren Gibson > Assignee: Steven Hawkins > Priority: Minor > Attachments: SERVER.log > > > The following queries are producing TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error. > The queries were returning expected query results in SOA-P5.3.1 release. However, when testing them with EAP 6.1Alpha and > Teiid 8.4Alpha they are returning the "Unable to evaluate "INPUT".nextKey" message. This is occuring on Postgres91, Oracle10,11,11RAC, Mysql55, Teradata, and Greenplum data sources. > I isolated "SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key" and ran a test to produce a log entry which > is attached. If you need other testing artifacts such as VDB please let me know. > SELECT * FROM XQTNestedDoc.testBoundTempTable > SELECT * FROM XQTNestedDoc.testExcludeFromDoc ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testOptimizableTempTable ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testRootTempTable ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testNested2Document ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testNestedDocument ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testSimpleDocument ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testSimpleTempTable ORDER BY recursiveroot.key -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2504) Improve socket results processing

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2504: ------------------------------------- Summary: Improve socket results processing Key: TEIID-2504 URL: https://issues.jboss.org/browse/TEIID-2504 Project: Teiid Issue Type: Enhancement Components: JDBC Driver, Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4 To increase large result transfer performance we can: 1. use a prefetch (which ideally will be performed before full deserialization) 2. allow for the client to fetch multiple server batches (although this has quite a few implementation considerations -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2503) XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error"

by Warren Gibson (JIRA)

[ https://issues.jboss.org/browse/TEIID-2503?page=com.atlassian.jira.plugin... ] Warren Gibson updated TEIID-2503: --------------------------------- Attachment: SERVER.log > XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error" > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2503 > URL: https://issues.jboss.org/browse/TEIID-2503 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: EAP6.1Alpha and Teiid8.4Alpha > Reporter: Warren Gibson > Assignee: Steven Hawkins > Priority: Critical > Attachments: SERVER.log > > > The following queries are producing TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error. > The queries were returning expected query results in SOA-P5.3.1 release. However, when testing them with EAP 6.1Alpha and > Teiid 8.4Alpha they are returning the "Unable to evaluate "INPUT".nextKey" message. This is occuring on Postgres91, Oracle10,11,11RAC, Mysql55, Teradata, and Greenplum data sources. > I isolated "SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key" and ran a test to produce a log entry which > is attached. If you need other testing artifacts such as VDB please let me know. > SELECT * FROM XQTNestedDoc.testBoundTempTable > SELECT * FROM XQTNestedDoc.testExcludeFromDoc ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testOptimizableTempTable ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testRootTempTable ORDER BY recursiveroot.key > SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testNested2Document ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testNestedDocument ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testSimpleDocument ORDER BY recursiveroot.key > SELECT * FROM XQTRecursiveDoc.testSimpleTempTable ORDER BY recursiveroot.key -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2503) XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error"

by Warren Gibson (JIRA)

Warren Gibson created TEIID-2503: ------------------------------------ Summary: XML Recursive and Nested Doc queries are producing "TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error" Key: TEIID-2503 URL: https://issues.jboss.org/browse/TEIID-2503 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Environment: EAP6.1Alpha and Teiid8.4Alpha Reporter: Warren Gibson Assignee: Steven Hawkins Priority: Critical The following queries are producing TEIID30328 Unable to evaluate "INPUT".nextKey: No value was available error. The queries were returning expected query results in SOA-P5.3.1 release. However, when testing them with EAP 6.1Alpha and Teiid 8.4Alpha they are returning the "Unable to evaluate "INPUT".nextKey" message. This is occuring on Postgres91, Oracle10,11,11RAC, Mysql55, Teradata, and Greenplum data sources. I isolated "SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key" and ran a test to produce a log entry which is attached. If you need other testing artifacts such as VDB please let me know. SELECT * FROM XQTNestedDoc.testBoundTempTable SELECT * FROM XQTNestedDoc.testExcludeFromDoc ORDER BY recursiveroot.key SELECT * FROM XQTNestedDoc.testOptimizableTempTable ORDER BY recursiveroot.key SELECT * FROM XQTNestedDoc.testRootTempTable ORDER BY recursiveroot.key SELECT * FROM XQTNestedDoc.testSimpleNested ORDER BY recursiveroot.key SELECT * FROM XQTRecursiveDoc.testNested2Document ORDER BY recursiveroot.key SELECT * FROM XQTRecursiveDoc.testNestedDocument ORDER BY recursiveroot.key SELECT * FROM XQTRecursiveDoc.testSimpleDocument ORDER BY recursiveroot.key SELECT * FROM XQTRecursiveDoc.testSimpleTempTable ORDER BY recursiveroot.key -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2502?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2502: --------------------------------------- That exception is happening on the client's next attempt to send something to the server. By itself it will likely just indicate that the connection has been closed. There should be a corresponding error on the server side indicating why the connection was terminated. > org.teiid.net.socket.SingleInstanceCommunicationException > --------------------------------------------------------- > > Key: TEIID-2502 > URL: https://issues.jboss.org/browse/TEIID-2502 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Environment: centos 6.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Critical > > I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial. > I'm getting the following error in SquirrelSQL > Error: org.teiid.net.socket.SingleInstanceCommunicationException > SQLState: 08S01 > ErrorCode: 0 > Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get: > Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed > SQLState: TEIID20013 > ErrorCode: 0 > I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type. > Probably it doesn't like it too much. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2502) org.teiid.net.socket.SingleInstanceCommunicationException

by luca gioppo (JIRA)

luca gioppo created TEIID-2502: ---------------------------------- Summary: org.teiid.net.socket.SingleInstanceCommunicationException Key: TEIID-2502 URL: https://issues.jboss.org/browse/TEIID-2502 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.2 Environment: centos 6.3 Reporter: luca gioppo Assignee: Steven Hawkins Priority: Critical I'm issuing a query (a simple select * from table) on a VDB's table that contains a geometric column from oracle spatial. I'm getting the following error in SquirrelSQL Error: org.teiid.net.socket.SingleInstanceCommunicationException SQLState: 08S01 ErrorCode: 0 Afterwards the connection is broken and I cannot access any other table and have to reconnect since I get: Error: Error Code:TEIID20013 Message:Error Code:TEIID20013 Message:java.net.SocketException: Socket closed SQLState: TEIID20013 ErrorCode: 0 I'm trying to access a SDO table and a geometry type column, but hoped that TEIID could read it as a BLOB without caring about the real type. Probably it doesn't like it too much. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2406) Quickstart to demonstrate custom database appender logger

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2406?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2406: ------------------------------------ This is a test, jira has seemed to have locked me out of creating jira's. > Quickstart to demonstrate custom database appender logger > --------------------------------------------------------- > > Key: TEIID-2406 > URL: https://issues.jboss.org/browse/TEIID-2406 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Van Halbert > -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2406) Quickstart to demonstrate custom database appender logger

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2406?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-2406: ------------------------------- Comment: was deleted (was: This is a test, jira has seemed to have locked me out of creating jira's.) > Quickstart to demonstrate custom database appender logger > --------------------------------------------------------- > > Key: TEIID-2406 > URL: https://issues.jboss.org/browse/TEIID-2406 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Van Halbert > -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2013