[JBoss JIRA] Created: (TEIID-1621) Unexpected grouping for SELECT queries on views that include a GROUP BY
by Claudio Venturini (JIRA)
Unexpected grouping for SELECT queries on views that include a GROUP BY
-----------------------------------------------------------------------
Key: TEIID-1621
URL: https://issues.jboss.org/browse/TEIID-1621
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Environment: Teiid 7.4 (with patch) deployed on JBoss AS 5.1, installed on Ubuntu Server 10.04 LTS. Four source models, two of which in MySQL 5.1.51 (on the same machine of JBoss), one on SQLServer 2000 (on another machine), and one on SQL Server 2005 (on another machine). All sources participate in XA transactions.
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Attachments: server.log
I've a set of models like the one that I've already explained in https://issues.jboss.org/browse/TEIID-1562. In addition I've a physical model, named sole_rugiada_phy, which extracts data from a SQL Server 2005 database. On top of it there's a view model, named sole_rugiada_log, which transform some fields and does some joins grouping.
In particular the base table named 'vendita_referenza' is defined as follows:
{code:sql}
SELECT
SR_op.codop, CAST(SR_v.n_bolla AS VARCHAR) AS codice, SUP_ro.codref, SR_v.data, CAST(SR_v.n_prog AS INTEGER) AS n_prog, CAST(SUM(SR_v.quantita) AS INTEGER) AS quantita, SUM((((SUP_r.quantita / SUP_ro.quantita_reale) * SR_v.quantita) * SR_v.prezzo)) AS fatturato, COUNT(*) AS groupdim
FROM
((sole_rugiada_phy.MISURA124.dbo.VENDITA_REFERENZA AS SR_v INNER JOIN support_log.mediator.referenza_op AS SUP_ro ON RTRIM(LTRIM(CAST(SR_v.codref AS VARCHAR))) = SUP_ro.codice) INNER JOIN support_log.mediator.referenza AS SUP_r ON SUP_ro.codref = SUP_r.codref) INNER JOIN sole_rugiada_log.misura124.solerugiada.op AS SR_op ON SUP_ro.codop = SR_op.codop
WHERE
SR_v.data >= PARSEDATE('20090701', 'yyyyMMdd')
GROUP BY SR_op.codop, SR_v.data, SR_v.n_bolla, SR_v.n_prog, SUP_ro.codref
{code}
If I run the following query, that is a simple SELECT statement, everything works fine:
{code:sql}
SELECT
codop,
codice,
codref,
data,
n_prog,
quantita,
fatturato,
groupdim
FROM
sole_rugiada_log.misura124.solerugiada.vendita_referenza
{code}
The query above retrieves 18717 records. But if I remove some fields from the SELECT statements something goes wrong. Take for example the following query:
{code:sql}
SELECT
codop,
codref,
data,
quantita,
fatturato
FROM
sole_rugiada_log.misura124.solerugiada.vendita_referenza
{code}
The above query gets only one record, which is a grouping over all the record, even if it doesn't include a GROUP BY clause. It's not clear what type of aggregation it does. It seems to be a sum of all records, but the result is not totally exact. The value of 'fatturato' is near the real sum (5043502.561000000 instead of 5046687.249000000), but the value of 'quantita' is much different from the real sum (489566 instead of 5537638).
I noticed that removing the GROUP BY from the definition of the base table the problem disappears, but, of course, most of times this cannot be used as a workaround.
Attached there are the project of the VDB and a log of the execution of the query that produces the wrong result.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (TEIID-1653) Support Cursoring over ODBC protocol ( support UseDeclareFetch = 1)
by Ramesh Reddy (JIRA)
Support Cursoring over ODBC protocol ( support UseDeclareFetch = 1)
-------------------------------------------------------------------
Key: TEIID-1653
URL: https://issues.jboss.org/browse/TEIID-1653
Project: Teiid
Issue Type: Feature Request
Components: ODBC
Affects Versions: 7.1.1
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.4.1, 7.5, 7.1.1
Postgres ODBC driver, retrieves all the rows from server for "select" request before it passes a single row to the calling client. This requires additional memory overhead for the client applications that dealing with very large resultset, which can lead to OOM issues. Postgres ODBC driver supports a couple properties
UseDeclareFetch = 1
Fetch=1000
using which, ODBC driver will form the queries using postgres "cursor" functionality, and only fetch number of rows that are defined with variable "Fetch". This will result in faster initial response time to the user (especially UI based apps) because the driver is not fetching all rows, it is only fetching the first batch. Also, minimal memory foot print as it can clear the results as they are delivered to the client application, especially with FORWARD only cursor. Teiid will only support for FORWARD ONLY cursor.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (TEIID-1668) Exception trying to preview data or execute VDB against SYBASE BQT2 table containing clob column
by Barry LaFond (JIRA)
Exception trying to preview data or execute VDB against SYBASE BQT2 table containing clob column
------------------------------------------------------------------------------------------------
Key: TEIID-1668
URL: https://issues.jboss.org/browse/TEIID-1668
Project: Teiid
Issue Type: Bug
Reporter: Barry LaFond
Assignee: Steven Hawkins
Testing various BQT2 DB's including Sybase.
1) Imported SMALLA & SMALLB tables, added to VDB and deployed
2) Able to query SELECT IntKey FROM SMALLA and get results
2) Try to perform SELECT * FROM SMALLA and get the following
16:49:28,338 WARN [PROCESSOR] Processing exception 'BQT2_2: Unexpected exception while translating results: Error' for request rLu0N1TlGtw/.6. Exception type org.teiid.core.TeiidProcessingException thrown from org.jboss.resource.adapter.jdbc.WrappedConnection.checkException(WrappedConnection.java:873). Enable more detailed logging to see the entire stacktrace.
16:49:42,992 WARN [TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@1005083[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@b0818a handles=1 lastUse=1309988982862 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@1b6e768 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@11261d3 xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@89ede txSync=null]
java.lang.UnsupportedOperationException: The method com.sybase.jdbc3.jdbc.SybCursorResultSet.getClob(int) is not supported and should not be called.
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseRuntimeException(Unknown Source)
at com.sybase.jdbc3.utils.Debug.notSupported(Unknown Source)
at com.sybase.jdbc3.jdbc.SybResultSet.getClob(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.getClob(WrappedResultSet.java:503)
at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:929)
at org.teiid.translator.jdbc.sybase.SybaseExecutionFactory.retrieveValue(SybaseExecutionFactory.java:358)
at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:103)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:282)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:267)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:197)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
16:49:43,050 WARN [CONNECTOR] Connector worker process failed for atomic-request=A1ZwTKKSzuDt.0.1.22
[TranslatorException]Unexpected exception while translating results: Error
1 [NestedSQLException]Error
at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:110)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:282)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:267)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338)
at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:197)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.util.NestedSQLException: Error
at org.jboss.resource.adapter.jdbc.WrappedConnection.checkException(WrappedConnection.java:873)
at org.jboss.resource.adapter.jdbc.WrappedStatement.checkException(WrappedStatement.java:852)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.checkException(WrappedResultSet.java:1947)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.next(WrappedResultSet.java:1200)
at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:97)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (TEIID-1563) Refresh a Materialized View without parameters from admin console
by Stephen Brooks (JIRA)
Refresh a Materialized View without parameters from admin console
-----------------------------------------------------------------
Key: TEIID-1563
URL: https://issues.jboss.org/browse/TEIID-1563
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Environment: EDS on RHEL 5, Admin Console with Firefox 4.0
Reporter: Stephen Brooks
Assignee: Steven Hawkins
Priority: Minor
Found an EDS bug in the admin console where it tries to refresh without parameters.
Steps to reproduce:
1. Go to the 'Control' tab for a VDB
2. Click 'Refresh a Materialized View'
3. Don't enter information, just click 'Cancel'
4. Click 'Refresh a Materialized View' again
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (TEIID-1596) Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
by Graeme Gillies (JIRA)
Document queryThresholdInSecs and allow functionality to ensure user queries take no longer than a specified interval
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-1596
URL: https://issues.jboss.org/browse/TEIID-1596
Project: Teiid
Issue Type: Feature Request
Reporter: Graeme Gillies
Assignee: Steven Hawkins
In the teiid documentation there is no mention (from what I can find) of exactly what the option queryThresholdInSecs does. The xml file states "Long running query threshold, after which a alert can be generated by tooling if configured", what tooling is this exactly? Does it alert and stop the query, or just alert?
On the same token, there is the configuration item maxSourceRows which is configured per instance. Unfortunately this isn't flexible enough sometimes, and it would be better if this option could be configured per VDB and per data role as well (some people can get more data than others).
I would expect the determination of what maxSourceRows is for a query should be as follows
1) If maxSourceRows is set for the data role the user has, use that (in the case of two data roles with different values, use the largest value)
2) If maxSourceRows is not set on any of the users data role, but set on the vdb, use that value
3) If maxSourceRows is not set on the vdb or any data roles the user has, use the instance setting.
Likewise, the setting maxSourceRows should not only be configurable per data role, vdb, instance, but also the setting queryThresholdInSecs, and either that option or another option should be put in place that allows us to hard limit the length of time a query can run. This is because in teiid we want to be able to say users cannot write a big huge query that will take more than X amount of seconds to execute, to stop someone in teiid giving it a huge query and hammering all the backend databases. Configuring this option by vdb and data role (as some people are more trusted and can run longer queries) would be fantastic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (TEIID-1699) odbc connection fails and crashes vdb that it doesn't respond to
by Michal Harish (JIRA)
odbc connection fails and crashes vdb that it doesn't respond to
-----------------------------------------------------------------
Key: TEIID-1699
URL: https://issues.jboss.org/browse/TEIID-1699
Project: Teiid
Issue Type: Bug
Components: ODBC
Affects Versions: 7.4
Environment: Windows 7 on VMWare
JBoss SA 5.1.0.GA
Teiid Runtime 7.4.0.Final + a_teiid-patch-7.4.0.Final
PostgreSQL 8.04 ODBC driver
Reporter: Michal Harish
Assignee: Steven Hawkins
Priority: Blocker
I have succesfully created and deployed vdb through Teiid Designer into the local JBoss server.
I can execute the vdb as well and access it via JDBC but when I try to configure it through ODBC
PostgreSQL 8.04 driver it crashes the ODBC Manager as well as the vdb server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (TEIID-1685) NullPointerException in ResultsMessage
by RAKESH BALGURI (JIRA)
NullPointerException in ResultsMessage
--------------------------------------
Key: TEIID-1685
URL: https://issues.jboss.org/browse/TEIID-1685
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.3
Environment: Windows7, Teiid 7.3
Reporter: RAKESH BALGURI
Assignee: Steven Hawkins
I am getting a NullPointerException when we execute queries in parallel.
The following is the stack trace
java.util.concurrent.ExecutionException: java.lang.Exception: Exception org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException occurred on statement SELECT subType, objectInstance, propertyName, propertyValue FROM chorus_metadata.property WHERE objectName=?
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl.getFilterTree(ObjectsServiceImpl.java:178)
at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl.getTreeForSection(ObjectsServiceImpl.java:2366)
at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl.getTreeNodeChildren(ObjectsServiceImpl.java:2622)
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 com.ca.mfui.chorusR2.servlet.ChorusGWTServlet.processCall(ChorusGWTServlet.java:224)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:224)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)
at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)
at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.ca.mfui.chorusR2.servlet.TransactionFilter$1.call(TransactionFilter.java:40)
at com.ca.mfui.chorusR2.servlet.TransactionFilter$1.call(TransactionFilter.java:35)
at com.ca.chorus.server.transaction.TransactionRunner.invoke(TransactionRunner.java:19)
at com.ca.chorus.server.transaction.TransactionRunner$$EnhancerByGuice$$c492b72.CGLIB$invoke$0(<generated>)
at com.ca.chorus.server.transaction.TransactionRunner$$EnhancerByGuice$$c492b72$$FastClassByGuice$$4cd78c09.invoke(<generated>)
at com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.ca.chorus.server.transaction.TransactionalMethodInterceptor.invoke(TransactionalMethodInterceptor.java:23)
at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at com.ca.chorus.server.transaction.TransactionRunner$$EnhancerByGuice$$c492b72.invoke(<generated>)
at com.ca.mfui.chorusR2.servlet.TransactionFilter.doFilter(TransactionFilter.java:34)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
Caused by: java.lang.Exception: Exception org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException occurred on statement SELECT subType, objectInstance, propertyName, propertyValue FROM chorus_metadata.property WHERE objectName=?
at com.ca.chorus.db.DbExecutor.handleSqlException(DbExecutor.java:285)
at com.ca.chorus.db.DbExecutor.withResultSet(DbExecutor.java:264)
at com.ca.chorus.db.DbExecutor.gatherResults(DbExecutor.java:416)
at com.ca.chorus.db.DbExecutor.gatherResults(DbExecutor.java:410)
at com.ca.mfui.chorusR2.server.service.MetadataServiceImpl.getMetadataForObjectNameFromTeiid(MetadataServiceImpl.java:82)
at com.ca.mfui.chorusR2.server.service.MetadataServiceImpl.getMetadataFor(MetadataServiceImpl.java:66)
at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl$1.call(ObjectsServiceImpl.java:170)
at com.ca.mfui.chorusR2.server.service.ObjectsServiceImpl$1.call(ObjectsServiceImpl.java:1)
at com.google.inject.servlet.ServletScopes$3.call(ServletScopes.java:194)
at com.ca.chorus.server.transaction.TransactionRunner.invoke(TransactionRunner.java:19)
at com.ca.chorus.server.transaction.TransactionalMethodInterceptor.invoke(TransactionalMethodInterceptor.java:23)
at com.ca.mfui.chorusR2.server.service.RequestScopedThreadPoolCallableDecorator.call(RequestScopedThreadPoolCallableDecorator.java:38)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:109)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:69)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:497)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:214)
at com.ca.chorus.db.LeakDetectingPreparedStatement.executeQuery(LeakDetectingPreparedStatement.java:46)
at com.ca.chorus.db.DbExecutor.withResultSet(DbExecutor.java:231)
... 15 more
Caused by: [TeiidException]
1 [NullPointerException]
at org.teiid.client.ResultsMessage.setException(ResultsMessage.java:177)
at org.teiid.dqp.internal.process.RequestWorkItem.sendError(RequestWorkItem.java:557)
at org.teiid.dqp.internal.process.RequestWorkItem.attemptClose(RequestWorkItem.java:335)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:218)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290)
... 3 more
Caused by: java.lang.NullPointerException
at org.teiid.common.buffer.impl.BufferManagerImpl$ManagedBatchImpl.getBatch(BufferManagerImpl.java:282)
at org.teiid.common.buffer.SPage.getValues(SPage.java:161)
at org.teiid.common.buffer.SPage.search(SPage.java:78)
at org.teiid.common.buffer.STree.find(STree.java:145)
at org.teiid.common.buffer.TupleBrowser.init(TupleBrowser.java:102)
at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:168)
at org.teiid.query.tempdata.TempTable$QueryTupleSource.nextTuple(TempTable.java:155)
at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:214)
at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:168)
at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:417)
at org.teiid.query.tempdata.TempTable.createTupleSource(TempTable.java:398)
at org.teiid.query.tempdata.TempTableDataManager.registerQuery(TempTableDataManager.java:437)
at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:182)
at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:170)
at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:197)
at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:118)
at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:152)
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:134)
at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105)
at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:115)
at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:250)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:184)
... 7 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months