April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4171) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl message

by Steve Tran (JIRA)

Steve Tran created TEIID-4171: --------------------------------- Summary: TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl message Key: TEIID-4171 URL: https://issues.jboss.org/browse/TEIID-4171 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Steve Tran Assignee: Ramesh Reddy Priority: Critical Fix For: 8.7.1.6_2, 8.12, 8.11.1 Can't reload VDB in domain mode, get the following error: Server throws the following exception: [Server:server-one] 12:26:45,678 ERROR [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl@4e6c9a30: java.lang.IllegalStateException: cluster 'ModeShape.1' is already connected to singleton transport: [dummy-1435055090515, loopback.1, ModeShape.1, loopback-dynamic.1, $TEIID_BM$, dummy-1435055090188, dummy-1435055205654, $TEIID_ED$, teiid-cache, ddl2-vdb.1] [Server:server-one] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] [Server:server-one] at org.jgroups.JChannel.startStack(JChannel.java:827) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] [Server:server-one] at org.jgroups.JChannel._preConnect(JChannel.java:525) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:268) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] [Server:server-one] at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.jboss.VDBService.access$1100(VDBService.java:85) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.jboss.VDBService$6.run(VDBService.java:411) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] [Server:server-one] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122) VDB reload works fine in standalone mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4171) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl message

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4171?page=com.atlassian.jira.plugin... ] Steve Tran updated TEIID-4171: ------------------------------ Affects Version/s: (was: 8.0) > TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl message > ------------------------------------------------------------------------------------------- > > Key: TEIID-4171 > URL: https://issues.jboss.org/browse/TEIID-4171 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Steve Tran > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4151) AssertionError: Delete failed

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4151?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4151. ----------------------------------- Resolution: Done Added a check on row deletion to see if the page needs removed from consideration by the TupleBrowser. > AssertionError: Delete failed > ----------------------------- > > Key: TEIID-4151 > URL: https://issues.jboss.org/browse/TEIID-4151 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.11.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.0, 8.13.4 > > > When using a query like > insert into #CaresequencesDaily > some large select; > delete > from #CaresequencesDaily > where datum < (select cast(startime as date) from #period); > delete > from #CaresequencesDaily > where datum > (select cast(endtime as date) from #period); > We get the following exception on the execution of the second delete query. It seems it does not matter in what order the delete queries are executed. > Unexpected exception for request lMZm1kGe28/C.24: java.lang.AssertionError: Delete failed > at org.teiid.query.tempdata.TempTable.deleteTuple(TempTable.java:801) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable.access$500(TempTable.java:83) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable$2.tuplePassed(TempTable.java:775) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable$UpdateProcessor.process(TempTable.java:257) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable.delete(TempTable.java:783) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTableDataManager$1.createTupleSource(TempTableDataManager.java:242) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:109) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.11.3.jar:8.11.3] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60] > I've tried to create a reproducable example but this doesn't throw the exception. It might be helpfull to understand what is goiing on. > insert into #tmp_params > select parsetimestamp('2016-04-01','yyyy-MM-dd') as starttime, parsetimestamp('2016-04-15','yyyy-MM-dd') as endtime; > insert into #tmp_dates > select cast(parsetimestamp('2016-03-20','yyyy-MM-dd') as date) as datum, 'somevalue' as somevalue > UNION select cast(parsetimestamp('2016-04-02','yyyy-MM-dd') as date) as datum, 'somevalue' as somevalue > UNION select cast(parsetimestamp('2016-04-20','yyyy-MM-dd') as date) as datum, 'somevalue' as somevalue; > delete > from #tmp_dates > where datum > (select cast(endtime as date) from #tmp_params); > --error is thrown when executing this second statement > delete > from #tmp_dates > where datum < (select cast(starttime as date) from #tmp_params); > select * > from #tmp_dates -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4170) Correct documentation on materialized view indexes

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4170: ------------------------------------- Summary: Correct documentation on materialized view indexes Key: TEIID-4170 URL: https://issues.jboss.org/browse/TEIID-4170 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 The documentation covering materialized view indexing is out of date and should be made more precise. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4168) Odd resolving error with implicit temp groups

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4168?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4168: ---------------------------------- Fix Version/s: 8.13.4 Actually this does introduce the possibility of an issue whereby we are misinterpretting an implicit insert: create temporary table #x (x string, y string) insert into #x select 'x' as y, 'y' as x would result in an y,x row - rather than the expected x,y row. So this will be needed in older branches as well. > Odd resolving error with implicit temp groups > --------------------------------------------- > > Key: TEIID-4168 > URL: https://issues.jboss.org/browse/TEIID-4168 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.13.4 > > > If a query expression is used to insert into an implicit temporary table and no columns are specified the resolver will complain when the query column names do not match those defined on the implicit table. For example: > insert into #tmp_dates ... defines the temp table ... > insert into #tmp_dates select <some expression> > Will complain that 'expr1' is not defined by #tmp_dates. Rather the column definitions should be assumed from the earlier statement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4169) Deployment/start sequence issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4169?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4169. ----------------------------------- Resolution: Done Updated the logic to use a specific timeout to check where state exists. Also made a small change to the zip filesystem to allow for concurrent in vm deployment (which didn't end up being needed by the unit test). > Deployment/start sequence issue > ------------------------------- > > Key: TEIID-4169 > URL: https://issues.jboss.org/browse/TEIID-4169 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.13.4 > > > For embedded the start/deployment sequence can cause a large 5 minute timeout to be hit which can excessively delay vdb deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4169) Deployment/start sequence issue

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4169: ------------------------------------- Summary: Deployment/start sequence issue Key: TEIID-4169 URL: https://issues.jboss.org/browse/TEIID-4169 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.13.4 For embedded the start/deployment sequence can cause a large 5 minute timeout to be hit which can excessively delay vdb deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3035: ------------------------------------- The link you provided is with Aync libraries, not sure that is applicable. Since you are trying to access over JAX-WS, we need support there. The relevant connection class in Teiid is https://github.com/teiid/teiid/blob/master/connectors/connector-ws/src/ma... see "configureWsSecurity" method. Couple links https://dmdaa.wordpress.com/2012/10/10/ntlm-v2-support-for-java-web-servi... http://www.coderanch.com/t/430458/Web-Services/java/JAX-WS-Authentication... see if these are any helpful? > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4168) Odd resolving error with implicit temp groups

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4168?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4168. ----------------------------------- Resolution: Done Added an attempt to resolve the group prior to assuming the statement defines the implicit temp table. > Odd resolving error with implicit temp groups > --------------------------------------------- > > Key: TEIID-4168 > URL: https://issues.jboss.org/browse/TEIID-4168 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > If a query expression is used to insert into an implicit temporary table and no columns are specified the resolver will complain when the query column names do not match those defined on the implicit table. For example: > insert into #tmp_dates ... defines the temp table ... > insert into #tmp_dates select <some expression> > Will complain that 'expr1' is not defined by #tmp_dates. Rather the column definitions should be assumed from the earlier statement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4168) Odd resolving error with implicit temp groups

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4168: ------------------------------------- Summary: Odd resolving error with implicit temp groups Key: TEIID-4168 URL: https://issues.jboss.org/browse/TEIID-4168 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 If a query expression is used to insert into an implicit temporary table and no columns are specified the resolver will complain when the query column names do not match those defined on the implicit table. For example: insert into #tmp_dates ... defines the temp table ... insert into #tmp_dates select <some expression> Will complain that 'expr1' is not defined by #tmp_dates. Rather the column definitions should be assumed from the earlier statement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016