[JBoss JIRA] (TEIID-3104) ArrayImpl toString not correct
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3104?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3104.
-----------------------------------
Resolution: Done
Updated the sql string visitor.
> ArrayImpl toString not correct
> ------------------------------
>
> Key: TEIID-3104
> URL: https://issues.jboss.org/browse/TEIID-3104
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> The arrayimpl tostring is not correct for multi-dimensional arrays and does not follow the convention of appending a trailing comma for arrays of less than 2 elements. Typically this tostring is not seen as there is the Array expression class, but source sql can contain ArrayImpl values.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3019) Change SYSADMIN.refreshMatViewRow to support a list of rows instead of just one
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3019?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3019.
-----------------------------------
Resolution: Done
Added sysadmin.refreshMatViewRows that takes a two dimensional array of values as the list of possibly composite key values to update. The logic still updates a single row at a time though - it may be more efficient in the future to allow more direct incremental update facilities such as access to the underlying materialization table or the ability to specify predicates that control which portions of the table are updated.
> Change SYSADMIN.refreshMatViewRow to support a list of rows instead of just one
> -------------------------------------------------------------------------------
>
> Key: TEIID-3019
> URL: https://issues.jboss.org/browse/TEIID-3019
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Server
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> Currently SYSADMIN.refreshMatViewRow supports only passing one key value so it will be nice to be able to pass multiple values or array of values for bulk updates.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3105) Can we add allowDuplicateDomains in Infinispan global configuration
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3105?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3105:
---------------------------------------
We have seen this behavior, but hadn't yet addressed it. I'm good with allowing multiple embedded instances per vm by default.
> Can we add allowDuplicateDomains in Infinispan global configuration
> -------------------------------------------------------------------
>
> Key: TEIID-3105
> URL: https://issues.jboss.org/browse/TEIID-3105
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Embedded
> Affects Versions: 9.x
> Environment: Teiid Embedded with Infinispan local cache
> Reporter: Kylin Soong
>
> I have run Teiid Embedded on top of Infinispan local cache meet the the following exception:
> org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan when trying to register: type=CacheManager,name="DefaultCacheManager"
> The "DefaultCacheManager" be register to MBeanServer 2 times cause the issue:
> 1. EmbeddedServer load infinispan cache via [1], this cause "DefaultCacheManager" register to MBean Server
> 2. Infinispan Translator connection load VDB refrred cache, this also cause "DefaultCacheManager" register again
> If we add allowDuplicateDomains in Infinispan configuration [1], this will avoid the issue.
> [1] https://github.com/teiid/teiid/blob/master/runtime/src/main/resources/inf...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3106) BufferManager Cleaner consuming 90% of total CPU time
by Devesh Mishra (JIRA)
Devesh Mishra created TEIID-3106:
------------------------------------
Summary: BufferManager Cleaner consuming 90% of total CPU time
Key: TEIID-3106
URL: https://issues.jboss.org/browse/TEIID-3106
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Query Engine
Affects Versions: 8.7
Environment: zOS
Reporter: Devesh Mishra
Assignee: Steven Hawkins
BufferManager Cleaner thread is consuming almost all of the CPU utilized by the jboss process. Thread dump shows following information.
3XMTHREADINFO "BufferManager Cleaner" J9VMThread:0x0000004C41CFEB00, j9thread_t:0x0000004C52B85AE0, java/lang/Thread:0x000000481C036E20, state:CW, prio=5
3XMJAVALTHREAD (java/lang/Thread getId:0x76, isDaemon:true)
3XMTHREADINFO1 (native thread ID:0x3AEC2600, native priority:0x5, native policy:UNKNOWN)
3XMHEAPALLOC Heap bytes allocated since last GC cycle=2609184 (0x27D020)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.doRemove(ConcurrentSkipListMap.java:1070(Compiled Code))
4XESTACKTRACE at java/util/concurrent/ConcurrentSkipListMap.remove(ConcurrentSkipListMap.java:1659(Compiled Code))
4XESTACKTRACE at org/teiid/common/buffer/impl/LrfuEvictionQueue.remove(LrfuEvictionQueue.java:60(Compiled Code))
4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl.doEvictions(BufferManagerImpl.java:854(Compiled Code))
5XESTACKTRACE (entered lock: org/teiid/common/buffer/CacheEntry@0x00000048393C2598, entry count: 1)
4XESTACKTRACE at org/teiid/common/buffer/impl/BufferManagerImpl$Cleaner.run(BufferManagerImpl.java:108)
4XESTACKTRACE at java/util/TimerThread.mainLoop(Timer.java:555)
4XESTACKTRACE at java/util/TimerThread.run(Timer.java:505)
When we added log statements around the BufferManagerImpl.doEvictions() it loops through the remove and firstEntry loop.
Forum discussion link : https://community.jboss.org/message/901792
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3105) Can we add allowDuplicateDomains in Infinispan global configuration
by Kylin Soong (JIRA)
Kylin Soong created TEIID-3105:
----------------------------------
Summary: Can we add allowDuplicateDomains in Infinispan global configuration
Key: TEIID-3105
URL: https://issues.jboss.org/browse/TEIID-3105
Project: Teiid
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Embedded
Affects Versions: 9.x
Environment: Teiid Embedded with Infinispan local cache
Reporter: Kylin Soong
I have run Teiid Embedded on top of Infinispan local cache meet the the following exception:
org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan when trying to register: type=CacheManager,name="DefaultCacheManager"
The "DefaultCacheManager" be register to MBeanServer 2 times cause the issue:
1. EmbeddedServer load infinispan cache via [1], this cause "DefaultCacheManager" register to MBean Server
2. Infinispan Translator connection load VDB refrred cache, this also cause "DefaultCacheManager" register again
If we add allowDuplicateDomains in Infinispan configuration [1], this will avoid the issue.
[1] https://github.com/teiid/teiid/blob/master/runtime/src/main/resources/inf...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-2615) Teiid 8.5 TEIID30238 Duplicate key on #MAT_PG_CATALOG.MATPG_RELATT
by Cristiano Nicolai (JIRA)
[ https://issues.jboss.org/browse/TEIID-2615?page=com.atlassian.jira.plugin... ]
Cristiano Nicolai commented on TEIID-2615:
------------------------------------------
I'm seeing the exact same error on 8.8.1.
For the first query I getting the same problem:
{noformat}
ERROR: TEIID30238 Duplicate key on #MAT_PG_CATALOG.MATPG_RELATT
DETAIL: org.teiid.jdbc.TeiidSQLException: TEIID30238 Duplicate key on #MAT_PG_CATALOG.MATPG_RELATT
{noformat}
Results for the second query:
{noformat}
elect count(*) from pg_catalog.pg_attribute, pg_catalog.pg_class, pg_catalog.pg_namespace, SYS.Columns where pg_attribute.attrelid = pg_class.oid and pg_namespace.oid = relnamespace and SchemaName = nspname and TableName = relname and Name = attname group by attname, relname, nspname having count(*) > 1;
expr1
-------
2
2
2
(3 rows)
{noformat}
> Teiid 8.5 TEIID30238 Duplicate key on #MAT_PG_CATALOG.MATPG_RELATT
> ------------------------------------------------------------------
>
> Key: TEIID-2615
> URL: https://issues.jboss.org/browse/TEIID-2615
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.2
> Environment: Teiid 8.5 from git master, running on jboss eap 6.1 using java 7 openjdk
> Reporter: Graeme Gillies
> Assignee: Steven Hawkins
> Fix For: 8.4.1, 8.5
>
>
> Hi,
> We are deploying a few dynamic vbs into our teiid environment and when we've deployed current versions of teiid from git master, we get the following error
> {noformat}
> 09:44:31,467 ERROR [org.teiid.PROCESSOR.MATVIEWS] (New I/O worker #1) TEIID30015 Failed to load materialized view table #MAT_PG_CATALOG.MATPG_RELATT.: org.teiid.core.TeiidProcessingException: TEIID30238 Duplicate key on #MAT_PG_CATALOG.MATPG_RELATT
> at org.teiid.query.tempdata.TempTable.insertTuple(TempTable.java:788) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTable.access$500(TempTable.java:83) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTable$InsertUpdateProcessor.tuplePassed(TempTable.java:150) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTable$UpdateProcessor.process(TempTable.java:257) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTable$InsertUpdateProcessor.process(TempTable.java:102) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTable.insert(TempTable.java:682) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTableDataManager$7.createTupleSource(TempTableDataManager.java:627) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:106) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTableDataManager$4.load(TempTableDataManager.java:526) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTableDataManager$4.createTupleSource(TempTableDataManager.java:497) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:106) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:376) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:153) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:307) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) [:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121) [teiid-api-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.jboss.TransportService$3.invoke(TransportService.java:254) [teiid-jboss-integration-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy20.executeRequest(Unknown Source)
> at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) [:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:135) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:133) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy20.executeRequest(Unknown Source)
> at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) [:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:135) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:133) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at com.sun.proxy.$Proxy20.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:633) [teiid-client-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:509) [teiid-client-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:258) [teiid-client-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.odbc.ODBCServerRemoteImpl.getPgColInfo(ODBCServerRemoteImpl.java:1012) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.odbc.ODBCServerRemoteImpl.prepare(ODBCServerRemoteImpl.java:432) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source) [:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:201) [teiid-runtime-8.5.0.Beta2-SNAPSHOT.jar:8.5.0.Beta2-SNAPSHOT]
> at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty.jar:3.6.2.Final-redhat-1]
> at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty.jar:3.6.2.Final-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {noformat}
> When we try and run queries against it. Sometimes it happens once and goes away, other times it happens over and over.
> I can supply the vdbs themselves if needed to help debug.
> Regards,
> Graeme
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3104) ArrayImpl toString not correct
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3104:
-------------------------------------
Summary: ArrayImpl toString not correct
Key: TEIID-3104
URL: https://issues.jboss.org/browse/TEIID-3104
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Query Engine
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
The arrayimpl tostring is not correct for multi-dimensional arrays and does not follow the convention of appending a trailing comma for arrays of less than 2 elements. Typically this tostring is not seen as there is the Array expression class, but source sql can contain ArrayImpl values.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-3103) ODBC fetch fails to send command complete
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3103:
-------------------------------------
Summary: ODBC fetch fails to send command complete
Key: TEIID-3103
URL: https://issues.jboss.org/browse/TEIID-3103
Project: Teiid
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ODBC
Affects Versions: 8.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.9
If a fetch statement hits the fetch limit before the end of the results it fails to send a command complete.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated TEIID-2930:
---------------------------------
Fix Version/s: 7.7.11
(was: 7.7.10)
> SCROLL keyword for DECLARE CURSOR not being parsed correctly
> ------------------------------------------------------------
>
> Key: TEIID-2930
> URL: https://issues.jboss.org/browse/TEIID-2930
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ODBC
> Affects Versions: 7.7.8
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1, 7.7.11
>
>
> The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1]
> [1]
> http://www.postgresql.org/docs/8.4/static/sql-declare.html
> [2]
> https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii...
> Example of error:
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"]
> DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0]
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8]
> FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully.
> DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ]
Johnathon Lee reopened TEIID-2930:
----------------------------------
fix fix version
> SCROLL keyword for DECLARE CURSOR not being parsed correctly
> ------------------------------------------------------------
>
> Key: TEIID-2930
> URL: https://issues.jboss.org/browse/TEIID-2930
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ODBC
> Affects Versions: 7.7.8
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 7.7.10, 8.8, 8.7.1
>
>
> The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1]
> [1]
> http://www.postgresql.org/docs/8.4/static/sql-declare.html
> [2]
> https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii...
> Example of error:
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"]
> DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0]
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement
> FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0
> TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8]
> FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully.
> DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months