September 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4477) LDAP connector disconnects intermittently with error "TEIID12002"

by Rafael Coutinho (JIRA)

Rafael Coutinho created TEIID-4477: -------------------------------------- Summary: LDAP connector disconnects intermittently with error "TEIID12002" Key: TEIID-4477 URL: https://issues.jboss.org/browse/TEIID-4477 Project: Teiid Issue Type: Bug Components: LDAP Connector Affects Versions: 8.12.5 Environment: Red Hat JBoss Data Virtualization - Version 6.3.0 Reporter: Rafael Coutinho Assignee: Steven Hawkins We are using LDAP connector for virtualizing the ldap employee directory data. For some reason every 3 to 4 hours we get a connection error between JDV and LDAP. The exception says it could not find the context name, but after restarting it it works again. Here is the exception: 11:21:12,868 WARN [org.teiid.CONNECTOR] (Worker62_QueryProcessorQueue108177) Connector worker process failed for atomic-request=6S71mw5pkfvo.106.3.19906: org.teiid.translator.TranslatorException: TEIID12002 Failed to create LDAP search context from the specified context name ou=users,dc=redhat,dc=com. Check the table/group name in source to ensure the context exists. at org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext(LDAPSyncQueryExecution.java:148) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] at org.teiid.translator.ldap.LDAPSyncQueryExecution.execute(LDAPSyncQueryExecution.java:130) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source) [:1.8.0-internal] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [rt.jar:1.8.0-internal] at java.lang.reflect.Method.invoke(Method.java:508) [rt.jar:2.6 (07-19-2016)] at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) at com.sun.proxy.$Proxy80.execute(Unknown Source) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) at java.util.concurrent.FutureTask.run(FutureTask.java:277) [rt.jar:1.8.0-internal] at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0-internal] at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0-internal] Caused by: javax.naming.CommunicationException: connection closed [Root exception is java.io.IOException: connection closed]; remaining name 'ou=users,dc=redhat,dc=com' at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2014) [rt.jar:1.8.0-internal] at com.sun.jndi.ldap.LdapCtx.doSearchOnce(LdapCtx.java:1945) [rt.jar:1.8.0-internal] at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1039) [rt.jar:1.8.0-internal] at com.sun.jndi.toolkit.ctx.ComponentContext.p_lookup(ComponentContext.java:554) [rt.jar:1.8.0-internal] at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(PartialCompositeContext.java:189) [rt.jar:1.8.0-internal] at com.sun.jndi.toolkit.ctx.PartialCompositeContext.lookup(PartialCompositeContext.java:178) [rt.jar:1.8.0-internal] at javax.naming.InitialContext.lookup(InitialContext.java:428) [rt.jar:1.8.0-internal] at javax.naming.InitialContext.lookup(InitialContext.java:428) [rt.jar:1.8.0-internal] at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.lookup(LDAPConnectionImpl.java:193) at org.teiid.translator.ldap.LDAPSyncQueryExecution.createSearchContext(LDAPSyncQueryExecution.java:146) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] ... 18 more Caused by: java.io.IOException: connection closed at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1604) [rt.jar:1.8.0-internal] at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:542) [rt.jar:1.8.0-internal] at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1997) [rt.jar:1.8.0-internal] ... 27 more 11:21:12,871 ERROR [org.teiid.CONNECTOR] (Worker63_QueryProcessorQueue108178) null: java.lang.NullPointerException at org.teiid.translator.ldap.LDAPSyncQueryExecution.close(LDAPSyncQueryExecution.java:186) [translator-ldap-8.12.5.redhat-8.jar:8.12.5.redhat-8] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.close(ConnectorWorkItem.java:255) at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) [:1.8.0-internal] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) [rt.jar:1.8.0-internal] at java.lang.reflect.Method.invoke(Method.java:508) [rt.jar:2.6 (07-19-2016)] at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) at com.sun.proxy.$Proxy80.close(Unknown Source) at org.teiid.dqp.internal.process.DataTierTupleSource.fullyCloseSource(DataTierTupleSource.java:338) at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:394) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:104) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) at org.teiid.query.processor.relational.DupRemoveNode.nextBatchDirect(DupRemoveNode.java:62) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153) [rt.jar:1.8.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [rt.jar:1.8.0-internal] at java.lang.Thread.run(Thread.java:785) [vm.jar:1.8.0-internal] 11:21:12,874 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Worker63_QueryProcessorQueue108178) LDAPSource: returnConnection(6306ef86, false) [1/20] 11:21:12,874 WARN [org.teiid.PROCESSOR] (Worker63_QueryProcessorQueue108178) TEIID30020 Processing exception for request 6S71mw5pkfvo.106 'TEIID30504 local: TEIID12002 Failed to create LDAP search context from the specified context name ou=users,dc=redhat,dc=com. Check the table/group name in source to ensure the context exists.'. Originally TeiidProcessingException 'connection closed' LdapClient.java:1604. Enable more detailed logging to see the entire stacktrace. 11:21:16,120 DEBUG [org.apache.catalina.session] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions StandardManager at 1474903276120 sessioncount 0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4234) Gradle blueprint

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4234?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4234: ------------------------------------- Unless there is more input as to what is expected, I propose we close this as Won't Fix/ Differed > Gradle blueprint > ---------------- > > Key: TEIID-4234 > URL: https://issues.jboss.org/browse/TEIID-4234 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Reporter: jay vyas > Fix For: 9.1 > > Attachments: build.gradle > > > As a app developer, I'd like to spin up a teiid/JDV application with all client-side dependencies > without needing to use an IDE. > Currently, most of the TEiid resources and videos are based on IDE features, bootstrapping teiid on the local machine. > Ideally, we might host a simple Teiid server that can run in a dockerfile with sample data, along side a gradle runnable file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4051: ------------------------------------- The current method of exposing the service as Swagger needs to be revamped based on more extension metadata. What we have for the purpose of Swagger is not adequate. The extension properties are defined as part of the Swagger translator, which need to be elevated at the engine level for construction of swagger file, to complete whole round trip. > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Fix For: 9.2 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4051: -------------------------------- Fix Version/s: 9.2 (was: 9.1) > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Fix For: 9.2 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4476) Upgrade Cassandra Client library

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4476?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4476: ------------------------------------- It looks it has been long time since Teiid's translator written for Cassandra, lot more CQL support is available. This need a much more deeper look. Pushing to 9.2 > Upgrade Cassandra Client library > -------------------------------- > > Key: TEIID-4476 > URL: https://issues.jboss.org/browse/TEIID-4476 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Cassandra client version of the library is 2.1, this needs to be upgraded to the latest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4476) Upgrade Cassandra Client library

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4476?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4476: ----------------------------------- Assignee: (was: Ramesh Reddy) > Upgrade Cassandra Client library > -------------------------------- > > Key: TEIID-4476 > URL: https://issues.jboss.org/browse/TEIID-4476 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Fix For: 9.2 > > > Cassandra client version of the library is 2.1, this needs to be upgraded to the latest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4476) Upgrade Cassandra Client library

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4476?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4476: -------------------------------- Fix Version/s: 9.2 (was: 9.1) > Upgrade Cassandra Client library > -------------------------------- > > Key: TEIID-4476 > URL: https://issues.jboss.org/browse/TEIID-4476 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Cassandra client version of the library is 2.1, this needs to be upgraded to the latest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3329) Rationalize older spatial support with the new

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3329?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3329. --------------------------------- Resolution: Done > Rationalize older spatial support with the new > ---------------------------------------------- > > Key: TEIID-3329 > URL: https://issues.jboss.org/browse/TEIID-3329 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.1 > > > MongoDB and Oracle had existing spatial support that should be updated to account for the new support if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4213) Cassandra translator: enable pushdown of aggregate functions

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4213?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4213: ------------------------------------- Added TEIID-4476 for Cassandra version, will take look at the version detection logic then > Cassandra translator: enable pushdown of aggregate functions > ------------------------------------------------------------ > > Key: TEIID-4213 > URL: https://issues.jboss.org/browse/TEIID-4213 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 9.1 > > > Cassandra supports basic aggregate functions: > MIN(),MAX(),SUM() and AVG() > Currently Teiid doesn't push such queries. > NOTE:In case of AVG() there is difference between the values returned from Teiid vs. Cassandra for an integer column. Cassandra returns only whole part of the number as integer, Teiid returns bigdecimal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4476) Upgrade Cassandra Client library

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-4476: ----------------------------------- Summary: Upgrade Cassandra Client library Key: TEIID-4476 URL: https://issues.jboss.org/browse/TEIID-4476 Project: Teiid Issue Type: Task Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 9.1 Cassandra client version of the library is 2.1, this needs to be upgraded to the latest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2016