February 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1608) TeiidComponentException from generated web service

by Scott Dawson (JIRA)

TeiidComponentException from generated web service -------------------------------------------------- Key: TEIID-1608 URL: https://issues.jboss.org/browse/TEIID-1608 Project: Teiid Issue Type: Bug Components: SOAP Services Affects Versions: 7.3 Environment: Runtime environment: JBoss AS 5.1, Teiid 7.3, JBossWS-CXF 3.2.1, MySQL 5, mysql-connector-java-5.1.10-bin.jar Development environment: Teiid Designer 7.3 installed into Eclipse Helios 3.6.2; SoapUI 2.5 as a test client Reporter: Scott Dawson Assignee: Steven Hawkins I'm using the 'Generate JBossWS-CXF War' feature of Teiid Designer to expose a MySQL table as a web service. Everything deploys normally and about half the time the web service works correctly, however, I often get the exception shown below when I call the service. It seems to be fairly random as to whether or not it works or throws the exception. Everything is running on one laptop including the client and the database. I'm attaching my Eclipse project, warfile and a more complete stack trace. See 'Steps to Reproduce' below for my development process and a description of the DB table. 17:46:20,833 SEVERE [org.teiid.soap] Exception in executeDataservice: {0} java.lang.Throwable: java.sql.SQLException: Unable to read data from the stream: [TeiidComponentException]Wrong type of data found or no data found; expecting streamable object from the buffer manager. at org.teiid.soap.provider.TeiidWSProvider.execute(TeiidWSProvider.java:194) at org.teiid.soap.provider.TeiidWSProvider.invoke(TeiidWSProvider.java:316) at org.teiid.soap.provider.MySQL_local_user.invoke(MySQL_local_user.java:22) at org.teiid.soap.provider.MySQL_local_user.invoke(MySQL_local_user.java:15) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:166) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:82) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:55) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:68) at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] (TEIID-1880) Support UNION ALL in multi source models

by Mark Addleman (Created) (JIRA)

Support UNION ALL in multi source models ---------------------------------------- Key: TEIID-1880 URL: https://issues.jboss.org/browse/TEIID-1880 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins We have physical data sources that can have many millions of rows. We are currently using Teiid's multi-source feature to union them together but, I believe Teiid is doing a proper UNION of the tables as opposed to a UNION ALL. The implied distinct operation in the UNION slows down our queries a lot because many operations cannot be pushed down to the underlying data sources and must be resolved in Teiid. We would like the option of performing a UNION ALL on multi source models -- 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

14 years

5
4
0 / 0

[JBoss JIRA] Created: (TEIID-1746) Documentation for ENV & COMMANDPAYLOAD is missing some details

by Paul Nittel (JIRA)

Documentation for ENV & COMMANDPAYLOAD is missing some details -------------------------------------------------------------- Key: TEIID-1746 URL: https://issues.jboss.org/browse/TEIID-1746 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.5 Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor Here are a couple of documentation clarifications for the Teiid Reference Document ENV Function The documentation states: The only key specific to the current session is 'sessionid'. However the preferred mechanism for getting the session id is with the session_id() function. To prevent untrusted access to system properties, the use of this function must be specifically enabled in the <jboss-install>/server/<profile>/deploy/teiid/teiid-jboss-beans.xml file. It's actually in teiid-deployer-jboss-beans.xml and it's called allowEnvFunction COMMANDPAYLOAD Function The documentation states: Retrieve a string from the command payload or null if no command payload was specified. The command payload is set by a method on the Teiid JDBC API extensions on a per-query basis. Rather than make the user hunt for it, the method in question is: TeiidStatement.setPayload -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1730) File resource adpater ra.xml is not valid

by Steven Hawkins (JIRA)

File resource adpater ra.xml is not valid ----------------------------------------- Key: TEIID-1730 URL: https://issues.jboss.org/browse/TEIID-1730 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 7.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 7.6 The file resource adapter is using the java.lang.Boolean type for allowparentpaths, which cannot be auto converted to the primitive type. If we use a non schema compliant xml, then we can specify the type as boolean. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-1637) In the Reference guide - Query Timeouts section - add a reference to the Client Developers guide

by Van Halbert (JIRA)

In the Reference guide - Query Timeouts section - add a reference to the Client Developers guide ------------------------------------------------------------------------------------------------ Key: TEIID-1637 URL: https://issues.jboss.org/browse/TEIID-1637 Project: Teiid Issue Type: Enhancement Components: Documentation Affects Versions: 7.4 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor In the Reference guide - Query Timeouts section - add a reference to the Client Developers guide section of the URL Connection properties that talks about setting the QueryTimeOut. It talks about it, but just doesn't point you to where/how to do it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1618) Designer (JBDS 4.1 CR1) not able to preview: NPE

by Paul Nittel (JIRA)

Designer (JBDS 4.1 CR1) not able to preview: NPE ------------------------------------------------ Key: TEIID-1618 URL: https://issues.jboss.org/browse/TEIID-1618 Project: Teiid Issue Type: Bug Components: Query Engine Environment: Fedora 14 x86_64, JBDS 4.1 CR1, Teiid 7.4 Final Reporter: Paul Nittel Assignee: Steven Hawkins I created a project and imported PartsSupplier from Oracle. I selected the PARTS table in the Model Explorer tree and clicked the Preview button. In return, I received exceptions: [AdminComponentException]Remote org.teiid.adminapi.AdminComponentException: Failed to process template. 1 [AdminComponentException]Remote org.teiid.adminapi.AdminComponentException: Failed to process template. 2 [AdminComponentException]Remote org.teiid.adminapi.AdminComponentException: Failed to process template. 3 [RuntimeException]Remote java.lang.RuntimeException: Failed to process template. 4 [RuntimeException]Remote java.lang.RuntimeException: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error ... and ... org.teiid.jdbc.TeiidSQLException: Remote org.teiid.client.security.LogonException: VDB "PREVIEW_f74d4e6a-9fdb-4b99-8539-27819cf6130d_SeaAreWon_project" version "latest" does not exist. at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69) at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:56) at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107) The whole Designer and server logs are attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
19
0 / 0

[JBoss JIRA] Created: (TEIID-1634) For file connector-based queries, please provide a DEBUG warning if no files are found

by Paul Nittel (JIRA)

For file connector-based queries, please provide a DEBUG warning if no files are found -------------------------------------------------------------------------------------- Key: TEIID-1634 URL: https://issues.jboss.org/browse/TEIID-1634 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Paul Nittel Assignee: Steven Hawkins I am writing a query against an XML file. I have a file connector referenced by a dynamic VDB. As luck would have it, I used an incorrect directory when the data source was defined. When the query is executed, it appears as though I have no results. (I actually have no data!) After fiddling with the XML for a while, I realized the error, corrected it, and went merrily on my way. Had there been some kind of notification that there were no files to process, I could have saved a half-hour. So, if a DEBUG message were put in the log file, it may help someone else (or me again) down the road. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
10
0 / 0

[JBoss JIRA] Created: (TEIID-1703) Allow for the parsing of fixed width files that don't use delimiters.

by Steven Hawkins (JIRA)

Allow for the parsing of fixed width files that don't use delimiters. --------------------------------------------------------------------- Key: TEIID-1703 URL: https://issues.jboss.org/browse/TEIID-1703 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Parsing a fixed width file that does not use a delimiter, or uses a newline for wrapping, is not currently possible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1716) Fix minor ODBC documentation

by Ramesh Reddy (JIRA)

Fix minor ODBC documentation ---------------------------- Key: TEIID-1716 URL: https://issues.jboss.org/browse/TEIID-1716 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.4 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.4.1, 7.6 Couple of properties in ODBC.INI file missing from UseDeclareFetch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (TEIID-1659) Support pagination of LDAP results when retrieving from Active Directory

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1659?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1659. --------------------------------- > Support pagination of LDAP results when retrieving from Active Directory > ------------------------------------------------------------------------ > > Key: TEIID-1659 > URL: https://issues.jboss.org/browse/TEIID-1659 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 7.1.1 > Environment: EDS 5.1. LDAP connection factory/translator. Active Directory as LDAP provider. > Reporter: Ken Johnson > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > Active Directory has a setting MaxPageSize that limits the number of records of query results returned in a batch. The EDS LDAP connector/translator should support this setting so it can page through the results and retrieve all results. Not just up to MaxPageSize. Ideally this would be a configurable parameter that the user must set to match the MaxPageSize value on the AD server. For more info: http://support.microsoft.com/kb/315071. -- 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

14 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012