July 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-683) Connector fails to start due to JDBC Connector ClassNotFound Exception

by Van Halbert (JIRA)

Connector fails to start due to JDBC Connector ClassNotFound Exception ---------------------------------------------------------------------- Key: TEIID-683 URL: https://jira.jboss.org/jira/browse/TEIID-683 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.1.0, 6.2.0 Environment: Embedded 6.2 kit Reporter: Van Halbert Assignee: Steven Hawkins Using a VDB that was created using 6.0 version. The connector type in the Configuration.def in the vdb has the ConnectorTypeClasspath value points to connector-jdbc-6.0.0.jar. The configuration.xml in the embedded kit has the connectortype classpath set to: extensionjar:connector_patch.jar;extensionjar:connector-jdbc-6.2.0-SNAPSHOT.jar. The embedded extensions directory contains connector-jdbc-6.2.0-SNAPSHOT.jar. In order to get the connector to start, the extension jar has to be renamed to connector-jdbc-6.0.0.jar. -- 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

16 years, 8 months

2
7
0 / 0

[JBoss JIRA] Closed: (TEIID-30) Wrong file in the file descriptor field causes weird error

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-30?page=com.atlassian.jira.plugi... ] Steven Hawkins closed TEIID-30. ------------------------------- > Wrong file in the file descriptor field causes weird error > ---------------------------------------------------------- > > Key: TEIID-30 > URL: https://jira.jboss.org/jira/browse/TEIID-30 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > > Defect Tracker #23789: When an non-descriptor file was entered into the text connector file descriptor field, the detail error shown on startup of the connector was: com.metamatrix.common.application.exception.ApplicationLifecycleException[0]: ConnectorException: com.metamatrix.core.MetaMatrixCoreException$StatusHolder@1c93217 > which provides no information as to what went wrong. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-577) Getting a major JDBC Error in the console (from the server), but don't see the exception in the process log

by Van Halbert (JIRA)

Getting a major JDBC Error in the console (from the server), but don't see the exception in the process log ----------------------------------------------------------------------------------------------------------- Key: TEIID-577 URL: https://jira.jboss.org/jira/browse/TEIID-577 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Steven Hawkins Trying to look at the extension modules in the console and receive a server SQLException when it''s accessing the CS_EXT_FILES. Unfortunately, the major exception isn't seen in the process log. I would have thought any major sql exception shown up when the console log setting is set to information. Error: Details Error Code:ERR.014.004.0047 Message:Retrieve extension modulesExternalException: [ExternalException] ERR.014.004.0047: Error Code:ERR.014.004.0047 Message:Retrieve extension modules 1 [MetaMatrixComponentException] ERR.014.004.0047: Error Code:ERR.014.004.0047 Message:Error retrieving all extension module names:SELECT FILE_NAME, FILE_DESC, FILE_TYPE, SEARCH_POS, IS_ENABLED, CREATED_BY, CREATION_DATE, UPDATED_BY, UPDATE_DATE, CHKSUM FROM CS_EXT_FILES 2 [SQLException][MetaMatrix][Oracle JDBC Driver]Exception generated during deferred local transaction handling. See next exception via SQLException.getNextException for details. 3 [SQLException][MetaMatrix][Oracle JDBC Driver]Broken pipe at com.metamatrix.console.models.ExtensionSourceManager.getModules(ExtensionSourceManager.java:217) at com.metamatrix.console.ui.views.extensionsource.ExtensionSourcesPanel.populateTable(ExtensionSourcesPanel.java:194) at com.metamatrix.console.ui.views.extensionsource.ExtensionSourcesPanel.init(ExtensionSourcesPanel.java:139) at com.metamatrix.console.ui.views.extensionsource.ExtensionSourcesPanel.<init>(ExtensionSourcesPanel.java:91) at com.metamatrix.console.ui.layout.WorkspaceController.createExtensionSourcesPanel(WorkspaceController.java:532) at com.metamatrix.console.ui.layout.WorkspaceController.createPanelOfClass(WorkspaceController.java:359) at com.metamatrix.console.ui.layout.WorkspaceController.doChangePanel(WorkspaceController.java:200) at com.metamatrix.console.ui.layout.WorkspaceControllerWorkItem.run(WorkspaceControllerWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:637) Caused by: [MetaMatrixComponentException] ERR.014.004.0047: Error Code:ERR.014.004.0047 Message:Error retrieving all extension module names:SELECT FILE_NAME, FILE_DESC, FILE_TYPE, SEARCH_POS, IS_ENABLED, CREATED_BY, CREATION_DATE, UPDATED_BY, UPDATE_DATE, CHKSUM FROM CS_EXT_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

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-339) Push down aggragate and distinct through union

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-339?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-339. ---------------------------------- Resolution: Done The pushing of distinct (union) is handled in RuleCollapseSource. RulePushAggregates was expanded to cover decomposing over aggregates using nested inline view queries. See TestAggregatePushdown and TestAggregateProcessing > Push down aggragate and distinct through union > ---------------------------------------------- > > Key: TEIID-339 > URL: https://jira.jboss.org/jira/browse/TEIID-339 > Project: Teiid > Issue Type: Task > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Li Liang > Assignee: Steven Hawkins > Fix For: 6.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This is related to case 6652 and case 6653. It improves performance to push down aggragate and distinct through union. If this is done before 5.5.3 release, we will consider pulling the logics back to 5.5.3. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-607) Connectors with invalid connection properties should show Source Unavailable at startup

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-607?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-607: ------------------------------------ Looks like in the current code base we are doing the blocking testConnection. Status check will happen when first time request comes in, Teiid currently not doing any proactive status checks on the Connectors status either, should this resurrected? > Connectors with invalid connection properties should show Source Unavailable at startup > --------------------------------------------------------------------------------------- > > Key: TEIID-607 > URL: https://jira.jboss.org/jira/browse/TEIID-607 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0 > Environment: MMServer: Fedora 8 Kernel 2.6.26.6-49.fc8 > Connector: Oracle JDBC Connector > Reporter: Larry O'Leary > Fix For: 6.2.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > If invalid connection properties are used in a connector binding the connector status shows "Running" at startup of the connector. When the first query is executed against the MMSystem that needs this connector an exception is thrown indicating that the connector wasn't found. This is due to the connector state changing to "Data Source Unavailable". > Although this is the expected behavior it is very mis-leading to the administrator after creating/adding a new connector or bouncing the system. The MMConsole gives the appearance that everything is okay until users actually start running queries. > What should be occurring is the current behavior and if Data Source Monitoring is enabled on the connector we should then check the data source available during connector startup. In other words, start the monitor thread with a timer of 0 instead a timer of monitoring interval. The idea is to show the connector as "Data Source Unavailable" at connector startup if the source isn't can't be reached due to invalid connection properties. > TEST: > To test this issue you simply need to have a connector deployed to a running MMSystem and verify that it is actually starting correctly with correct properties (ie verify you can run queries using this connector). > Now, change the password on the connector to something that is invalid. Stop and then start the connector. The connector will show a "Running" state yet as soon as you execute the query the query will fail and the status of the connector will change to "Source Unavailable". > EXPECTED RESULT: > When you start a connector using an invalid password (or other connection type property like SID, DatabaseName, etc) the connector state should immediately reflect "Data Source Unavailable". -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-722) Determining the Teiid runtime instace identity could be error prone

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-722?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-722. -------------------------------- Resolution: Done Identity of the runtime is now solely based on the "processName" supplied in the deploy.properties. If processName is not supplied "embedded" is chosen as the name. It is requirement from TEIID-66 that there needs to only one instance of Teiid in a given JVM. > Determining the Teiid runtime instace identity could be error prone > ------------------------------------------------------------------- > > Key: TEIID-722 > URL: https://jira.jboss.org/jira/browse/TEIID-722 > Project: Teiid > Issue Type: Bug > Components: Embedded, Server > Affects Versions: 6.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.2.0 > > > The current way instance id generated for the uniquely identifying the runtime engine could be wrong. Now that "processname" is available in the property, that name should be used as the identifier instead of int identifier now. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-173) ProductAdmin role can deploy a vdb but cannot create connector bindings

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-173?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-173: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3. > ProductAdmin role can deploy a vdb but cannot create connector bindings > ----------------------------------------------------------------------- > > Key: TEIID-173 > URL: https://jira.jboss.org/jira/browse/TEIID-173 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.x > Reporter: Steve Jacobs > Fix For: 6.3.0 > > > Defect Tracker #24544: Seems like if I have authorization to deploy a VDB, I should have authorization to create connector bindings. This should be re-evaluated. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-211) subquery optimization

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-211?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-211: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3 > subquery optimization > --------------------- > > Key: TEIID-211 > URL: https://jira.jboss.org/jira/browse/TEIID-211 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.3.0 > > > Implement rewriter (and planner) optimizations for subqueries based upon semi and anti semi join capabilities. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-168) Remove resultset caching

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-168?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-168: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3 > Remove resultset caching > ------------------------ > > Key: TEIID-168 > URL: https://jira.jboss.org/jira/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.3.0 > > > Resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-219?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-219: --------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Pushing to 6.3 > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://jira.jboss.org/jira/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 6.3.0 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- 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

16 years, 8 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 July 2009