May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-490) Change the meaning of essential services / essential service restart

by Steven Hawkins (JIRA)

Change the meaning of essential services / essential service restart -------------------------------------------------------------------- Key: TEIID-490 URL: https://jira.jboss.org/jira/browse/TEIID-490 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 6.1.0 Reporter: Steven Hawkins Fix For: 6.1.0 Essential service should mean that the service cannot be stopped and must be enabled on each cluster member. Restarts should always be allowed, but we should make some attempt to ensure that the service does not leave state which would be inconsistent (such as sessions that are no longer valid). -- 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

15 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-497) Modify SOAP War to Allow for Multiple Connection Type Support

by Ted Jones (JIRA)

Modify SOAP War to Allow for Multiple Connection Type Support ------------------------------------------------------------- Key: TEIID-497 URL: https://jira.jboss.org/jira/browse/TEIID-497 Project: Teiid Issue Type: Feature Request Reporter: Ted Jones Assignee: Steven Hawkins Currently, the SOAP war can only connect to the MMDriver. This precludes connection to an embedded Teiid instance. The connection pool and VDB resource logic needs to change to specify which connection type to use (JDBC, JNDI, ?) and format the connection URL accordingly. A properties file would be ideal for specifying the connection type and URL format rather than storing the information in the web.xml as we have in the past. This Jira is a result of the following posting in the Teiid forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225928#4225928 -- 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

15 years

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-623) Updating Common Extension Classpath With New/Changed UDF JARs Does Not Make Those JARs Visible Even After A UDF Reload

by Dan Florian (JIRA)

Updating Common Extension Classpath With New/Changed UDF JARs Does Not Make Those JARs Visible Even After A UDF Reload ---------------------------------------------------------------------------------------------------------------------- Key: TEIID-623 URL: https://jira.jboss.org/jira/browse/TEIID-623 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 6.1.0 Reporter: Dan Florian Assignee: Steven Hawkins Priority: Blocker In Teiid Designer, after a new UDF JAR is added the following code is executed: EmbeddedAdmin admin = (EmbeddedAdmin)adminConnection.getAdminAPI(); admin.setSystemProperty(DQPEmbeddedProperties.COMMON_EXTENSION_CLASPATH, buildUDFClasspath()); admin.reloadUDF(); The buildUDFClasspath() method builds an extension jar classpath with just the UDF JARS. So it would look something like this: extensionjar:udfjar1.jar;extensionjar:udfjar2 When the Designer tries to query using Teiid embedded that new JAR is not found on the extension classpath. The reload should pick up the newly added or updated JARS on the extension classpath. -- 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

15 years

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-634) Missing message when password is null (MMAdmin)

by Paul Nittel (JIRA)

Missing message when password is null (MMAdmin) ----------------------------------------------- Key: TEIID-634 URL: https://jira.jboss.org/jira/browse/TEIID-634 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Environment: Fedora 10, Java 1.6.0_10-b33, JBEDSP server, etc. May 21, 2009 build Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor I was experimenting with security disabled. I tried logging into the Console without a password and received an error (Login failed - Unspecified error). The same thing with MMAdmin produces this: admin $ connectAsAdmin("foo","","mm://localhost:31000"); // Error: // Uncaught Exception: Method Invocation createAdmin : at Line: 99 : in file: URL: jar:file:/home/pnittel/jbedsp0521/server/lib/teiid-adminshell-6.1.0-SNAPSHOT.jar!/scripts/server.bsh : .createAdmin ( username , password .toCharArray ( ) , url ) Target exception: java.lang.IllegalArgumentException: <Missing message for key "ERR.014.001.00100" in: com.metamatrix.admin.i18n> On the bright side, omitting the username produces a meaningfule error: admin $ connectAsAdmin("","","mm://localhost:31000"); // Error: // Uncaught Exception: Method Invocation createAdmin : at Line: 99 : in file: URL: jar:file:/home/pnittel/jbedsp0521/server/lib/teiid-adminshell-6.1.0-SNAPSHOT.jar!/scripts/server.bsh : .createAdmin ( username , password .toCharArray ( ) , url ) Target exception: java.lang.IllegalArgumentException: The user parameter may not be null or empty. To set this up, 1 - Login to the Console as Admin 2 - Go to the Security Summary panel 3 - Uncheck "Enable Authorization and Authentication" 4 - Click Apply 5 - Enter the Admin password 6 - Click OK 7 - Restart the server You may now login as anything, but not nothing. :-) -- 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

15 years

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-632) Teiid Designer Integration Tasks

by Steven Hawkins (JIRA)

Teiid Designer Integration Tasks -------------------------------- Key: TEIID-632 URL: https://jira.jboss.org/jira/browse/TEIID-632 Project: Teiid Issue Type: Task Components: Common, Embedded Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Blocker Fix For: 6.1.0 -- 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

15 years

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-621) Remove beanshell from common-internal dependencies

by Steven Hawkins (JIRA)

Remove beanshell from common-internal dependencies -------------------------------------------------- Key: TEIID-621 URL: https://jira.jboss.org/jira/browse/TEIID-621 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Beanshell is needed by the cdk, mmadmin, and the console, so it should be an explicit dependency there rather than a dependency of common-internal -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-627) ExtensionModules for connectors should be detected from connector type classpath

by Steven Hawkins (JIRA)

ExtensionModules for connectors should be detected from connector type classpath -------------------------------------------------------------------------------- Key: TEIID-627 URL: https://jira.jboss.org/jira/browse/TEIID-627 Project: Teiid Issue Type: Bug Components: Common, Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 ExtensionModules for connectors are currently being picked up by the classpath entry. Also the ConnectorPropertyNames class should be moved out of the internal package, since it's usage doesn't need to be restricted. -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-622) Simplify configuration property metadata

by Steven Hawkins (JIRA)

Simplify configuration property metadata ---------------------------------------- Key: TEIID-622 URL: https://jira.jboss.org/jira/browse/TEIID-622 Project: Teiid Issue Type: Task Reporter: Steven Hawkins Assignee: Steven Hawkins In general we have too much property metadata: required from multiplicity 0..1, 1 (no others are currently used). hasDefault expert hidden preferred modifiable which gives us 64 possible state combinations. Proposed simplifications: 1. remove the use of multiplicity and just use a required attribute. 2. remove hidden and instead use modifiable=false. 3. remove preferred and instead use expert=false (the default). !modifiable would imply expert=true and required=false. That leaves us with only 8 states to consider based upon required/expert/hasDefault - but there's only 1 state we even care about the presence of a default value (other than for a display color). That leaves us with: required expert outcome t t 1) Valid only if there is a default value, then it's an Editable property that should only be shown in expert mode t f 2) Editable property that should always be shown f t 3) Editable optional property that should be shown only in expert f f 4) Editable optional property that should always be shown >From a display perspective we will by default show cases 2 and 4 and then show 1 and 3 if "show expert" is selected. Alternatively instead of show expert we could also use "show all". We should make provisions for old metadata to be read, such as still looking for the hidden and multiplicity attributes. -- 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

15 years

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-629) Blocked Exception thrown - BQT Query Testing

by Warren Gibson (JIRA)

Blocked Exception thrown - BQT Query Testing -------------------------------------------- Key: TEIID-629 URL: https://jira.jboss.org/jira/browse/TEIID-629 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Environment: BQT running on Windows server Reporter: Warren Gibson Assignee: Steven Hawkins The following two BQT queries are throwing Blocked Exception. Still reviewing query results but if I find more of these I will log them to this JIRA. SELECT stringkey, (SELECT intkey from BQT1.SmallA where Intnum > 22) FROM BQT1.SmallA order by stringkey SELECT INTKEY, (SELECT TIMESTAMPVALUE FROM BQT1.SMALLA WHERE DOUBLENUM < 25) FROM BQT1.SMALLA ORDER BY Intkey May 26, 2009 10:28:31.250 [Worker1_QueryProcessorQueue12|0] ERROR <DQP|0> Unexpected exception for request 2304.5 [MetaMatrixComponentException] 1 [BlockedException] at com.metamatrix.query.processor.relational.SubqueryAwareEvaluator.evaluateSubquery(SubqueryAwareEvaluator.java:133) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:651) at com.metamatrix.query.eval.Evaluator.internalEvaluate(Evaluator.java:556) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:514) at com.metamatrix.query.processor.relational.ProjectNode.updateTuple(ProjectNode.java:233) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:193) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.BatchCollector.collectTuples(BatchCollector.java:58) at com.metamatrix.query.processor.relational.BatchCollector.collectTuples(BatchCollector.java:52) at com.metamatrix.query.processor.relational.SortNode.collectionPhase(SortNode.java:117) at com.metamatrix.query.processor.relational.SortNode.nextBatchDirect(SortNode.java:102) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:110) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:160) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:264) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:210) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) 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:619) Caused by: [BlockedException] at com.metamatrix.common.buffer.BlockedException.<clinit>(BlockedException.java:34) at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:148) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89) at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:136) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:92) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:166) ... 15 more May 26, 2009 10:28:31.312 [Worker1_QueryProcessorQueue14|0] ERROR <DQP|0> Unexpected exception for request 2304.6 [MetaMatrixComponentException] 1 [BlockedException] at com.metamatrix.query.processor.relational.SubqueryAwareEvaluator.evaluateSubquery(SubqueryAwareEvaluator.java:133) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:651) at com.metamatrix.query.eval.Evaluator.internalEvaluate(Evaluator.java:556) at com.metamatrix.query.eval.Evaluator.evaluate(Evaluator.java:514) at com.metamatrix.query.processor.relational.ProjectNode.updateTuple(ProjectNode.java:233) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:193) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.BatchCollector.collectTuples(BatchCollector.java:58) at com.metamatrix.query.processor.relational.BatchCollector.collectTuples(BatchCollector.java:52) at com.metamatrix.query.processor.relational.SortNode.collectionPhase(SortNode.java:117) at com.metamatrix.query.processor.relational.SortNode.nextBatchDirect(SortNode.java:102) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:110) at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:160) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:264) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:210) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) 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:619) Caused by: [BlockedException] at com.metamatrix.common.buffer.BlockedException.<clinit>(BlockedException.java:34) at org.teiid.dqp.internal.process.DataTierTupleSource.switchBatch(DataTierTupleSource.java:148) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:89) at com.metamatrix.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:136) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:92) at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:257) at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:166) ... 15 more -- 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

15 years

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-635) Executed 5K+ queries against Teiid; got "cache not in started state" at end

by Paul Nittel (JIRA)

Executed 5K+ queries against Teiid; got "cache not in started state" at end --------------------------------------------------------------------------- Key: TEIID-635 URL: https://jira.jboss.org/jira/browse/TEIID-635 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Environment: Fedora 10, Java 1.6.0_10, Teiid 5/28/2009 (M3) Reporter: Paul Nittel Assignee: Steven Hawkins Priority: Minor Attachments: CacheNotStarted.zip, Eall.zip I executed my Teiid Testing Tool (executes BQT queries) and at the end of the run, received a bunch of errors which stated "cache not in started state". Steve Hawkins indicates this is not harmful, but is annoying. The attached Zip archives contains the logs and other files necessary to run this test. Eall.zip contains the expected results files. -- 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

15 years

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009