[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
13 years, 1 month
[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
13 years, 1 month
[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
13 years, 1 month
[JBoss JIRA] Created: (TEIID-1070) Create Amazon SimpleDB Connector
by John Doyle (JIRA)
Create Amazon SimpleDB Connector
---------------------------------
Key: TEIID-1070
URL: https://jira.jboss.org/jira/browse/TEIID-1070
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: John Doyle
Assignee: John Doyle
Fix For: 7.1
We need connectivity to Amazon SimpleDB. This should be accomplished through a dedicated connector.
Simple DB presents a few challenges as a Teiid source as it is more like a spreadsheet than a database. Simple DB "Domains' are like individual worksheets and contain any number of items. Items however can have any number of attributes, and the attributes do not have to be the same for ever item. So in a single Domain you can have an item with the attributes Size and Color, and another item with the attributes Color and ExpirationDate. This presents both modeling issues and SQL execution issues. None of them are insurmountable, but users will have to understand the issues and design their integration around them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (TEIID-1646) NPE deploying vdb as a data source for Top-Down WSDL test WAR file use
by Paul Nittel (JIRA)
NPE deploying vdb as a data source for Top-Down WSDL test WAR file use
----------------------------------------------------------------------
Key: TEIID-1646
URL: https://issues.jboss.org/browse/TEIID-1646
Project: Teiid
Issue Type: Bug
Affects Versions: 7.5
Environment: 64-bit Fedora, Teiid 7.5 alpha1
Reporter: Paul Nittel
Assignee: Steven Hawkins
I am in the process of executing the E2E Top-Down WSDL test. It calls for using Jopr to create a local tx data source (the VDB) which is then used by the WAR file created during the test. As I saved the DS in Jopr, Jopr reported this error:
Failed to add Resource (see app server log for additional details): java.lang.RuntimeException:Failed to process template. -> java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml DEPLOYMENTS IN ERROR: Deployment "vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml" is in error due to the following reason(s): java.lang.NullPointerException -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml DEPLOYMENTS IN ERROR: Deployment "vfsfile:/home/pnittel/T75a1/jboss-5.1.0.GA/server/default/deploy/cosjndi-ds.xml" is in error due to the following reason(s): java.lang.NullPointerException
I'll be attaching the server log, Designer Model Project Set, and test script.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months