May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-503) startHost( badHostName ) causes MMProcess to loop, trying to ping bad host name

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-503?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-503. ---------------------------------- Resolution: Out of Date Host resolution has changed significantly and also the specification of an invalid vmname will result in an error. > startHost( badHostName ) causes MMProcess to loop, trying to ping bad host name > ------------------------------------------------------------------------------- > > Key: TEIID-503 > URL: https://jira.jboss.org/jira/browse/TEIID-503 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0 > Environment: fedora 10, 553GA > Reporter: Paul Nittel > Fix For: 6.1.1 > > > Persistence is a virtue, but not when it comes to computers. ;-) > I created a test for mmadmin which tried to start a host with a bad name. (I figured it would give me an error and the test could proceed from there.) What happened was the test didn't end in a reasonable time, but the server's process log was growing. Turns out it was filling with these: > Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR <com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest > Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR <com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest > Mar 13, 2009 09:34:00.650 [SocketWorkerQueue_Worker_357|0] ERROR <com.metamatrix.platform|0> Unable to ping bindaddress: CCEtest > Offhand, I'd say one would be sufficient. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-482) Web Services Tab not Displaying in Console

by Ted Jones (JIRA)

Web Services Tab not Displaying in Console ------------------------------------------ Key: TEIID-482 URL: https://jira.jboss.org/jira/browse/TEIID-482 Project: Teiid Issue Type: Bug Components: Console Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.1.0 The tab used for publishing the WSDL URL for a Web Services VDB to a UDDI Registry is not displaying in the Console. -- 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 month

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-591) Remove optional parenthesis for joins

by Li Liang (JIRA)

Remove optional parenthesis for joins ------------------------------------- Key: TEIID-591 URL: https://jira.jboss.org/jira/browse/TEIID-591 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Li Liang Assignee: Li Liang Fix For: 6.1.0 Parenthesis are added to joins when translating queries in connector. Some parenthesis are optional, but caused problem for Oracle 9 (case 270389). However, MySql does still need those parenthesis (case 289582). -- 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 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-589) NoClassDefFoundError issues when importing JDBC data source

by Ben Truitt (JIRA)

NoClassDefFoundError issues when importing JDBC data source ------------------------------------------------------------ Key: TEIID-589 URL: https://jira.jboss.org/jira/browse/TEIID-589 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 6.0.0 Environment: eclipse.buildId=I20090430-2300 java.version=1.6.0_07 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/btruitt/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/btruitt/.eclipse_keyring -showlocation This is a continuation of log file /Users/btruitt/workspace/.metadata/.bak_0.log Created Time: 2009-05-12 15:43:45.985 teiid_designer_6.0.0.v20090427_SNAPSHOT Reporter: Ben Truitt Assignee: Steven Hawkins When I try to import from a Postgresql 8.2 database using postgresql-8.3-604.jdbc4.jar on eclipse 3.5 M7, teiid_designer_6.0.0.v20090427_SNAPSHOT, on mac os x with java 1.6 64-bit, I get the attached stack traces. Several NoClassDefFoundError errors occur. After that, the generated model is reported as being in error. Note, when I import a view from the same database, I do not get this problem. Based on the errors that are reported in the generated model, it seems to be caused by references to foriegn keys and indices, etc. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-588) Errors opening with Model Editor in Eclipse 3.5 M7 on Mac OS X

by Ben Truitt (JIRA)

Errors opening with Model Editor in Eclipse 3.5 M7 on Mac OS X -------------------------------------------------------------- Key: TEIID-588 URL: https://jira.jboss.org/jira/browse/TEIID-588 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 6.0.0 Environment: eclipse.buildId=I20090430-2300 java.version=1.6.0_07 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/btruitt/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/btruitt/.eclipse_keyring -showlocation Reporter: Ben Truitt Assignee: Steven Hawkins Hi - Running on Eclipse 3.5 M7 with the most recent designer snapshot (6.0.0), I am experiencing a couple of errors when I open an "xmi" model file by right-clicking in the model explorer view and choosing "open with", "model editor." I get two separate error dialog boxes, then the Diagram editor appears with a blank canvas and no buttons in the left-side of the pane. The error messages are: Quote: Error attempting to load a Model Object Editor Page plugin ID = com.metamatrix.modeler.webservice.ui.editor.OperationObjectEditorPage Quote: Error attempting to load a Model Object Editor Page plugin ID = com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage I am using the most recent SNAPSHOT version of the Designer on Eclipse Version: 3.5.0 M7 (Build id: I20090430-2300), java.runtime.version=1.6.0_07-b06-153, on mac os x version 10.5.6. In addition to the above error messages, I see the following errors logged in the Eclipse Error View (they appear in this chronological order): Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.connectorBindingLabelProvider" Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.udfModelJarsLabelProvider" Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.connectorBindingLabelProvider" Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.udfModelJarsLabelProvider" Error attempting to load a Model Object Editor Page plugin ID = com.metamatrix.modeler.webservice.ui.editor.OperationObjectEditorPage Error attempting to load a Model Object Editor Page plugin ID = com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.connectorBindingLabelProvider" Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.udfModelJarsLabelProvider" Unhandled event loop exception I will attach stack traces for each of these exceptions to the Jira issue. -Ben Truitt -- 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 month

1
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-203) Make connector capabilites more granular.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-203?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-203. ---------------------------------- Resolution: Done Implemented the capabilities changes listed above, will open follow up defects on the remaining issues. > Make connector capabilites more granular. > ----------------------------------------- > > Key: TEIID-203 > URL: https://jira.jboss.org/jira/browse/TEIID-203 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Some connector capabilites are only available in combination with others. For example, if you wish to support the SupportsAggregatesCount capability, you have to also support the SupportsAggregates capability(GROUP BY and HAVING). This requirement creates additional requirements for a connector where the source syustem cabilities do not correspond with the relationships we have defined between capabilites. > For instance, the SQL supported by salesforce can include the count(*) function, but it does not support GROUP BY or HAVING. Because we require c connector to support SupportsAggregates befrore it can support count(*), the connector is required to implement those functions if it wishes to pus down count(*). -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-585) Temp table handling issues

by Steven Hawkins (JIRA)

Temp table handling issues -------------------------- Key: TEIID-585 URL: https://jira.jboss.org/jira/browse/TEIID-585 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0, 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Session level temp tables are not handled correctly by prepared statements if the table has been removed. The same is true for explicit temp tables in procedures that have been explicitly removed - ideally there would be a resolver error, but instead we should at least have a processing time exception. Finally the clone method for query does not include the clone of the into group. -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-578) Having max pool connections and max threads as connector properties is confusing

by Steven Hawkins (JIRA)

Having max pool connections and max threads as connector properties is confusing -------------------------------------------------------------------------------- Key: TEIID-578 URL: https://jira.jboss.org/jira/browse/TEIID-578 Project: Teiid Issue Type: Quality Risk Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 After talking over connection pool monitoring, it was desirable to make connector configuration easier to understand. A simple change that will alleviate much confusion is to remove the max pool connections property and to change ConnectorMaxThreads to be "Connector Max Concurrent Connections". If it's a synch connector "Connector Max Concurrent Connections" is the max number of connections in the pool (if pooled) and is also the max number of threads allowed. If asynch (and thus not pooled), "Connector Max Concurrent Connections" still acts as the max threads setting, which limits the number of connections that can be concurrently used. The absolute max number of connections may grow higher than max concurrent connections depending on the number of asynch operations performed. -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-584) Criteria pushed across frame can be pushed too far

by Steven Hawkins (JIRA)

Criteria pushed across frame can be pushed too far -------------------------------------------------- Key: TEIID-584 URL: https://jira.jboss.org/jira/browse/TEIID-584 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 When pushing across a frame (union or just source) we push the criteria below the root project node - this may be too far however if an access node has been raise above the project node. -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-582) Aggregate pushdown recursion error

by Steven Hawkins (JIRA)

Aggregate pushdown recursion error ---------------------------------- Key: TEIID-582 URL: https://jira.jboss.org/jira/browse/TEIID-582 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.1.0 we are not careful about ensuring that that every symbol is unique in a plan, there's a chance mapping the expression in an aggregate (i.e. sum(x) -> sum(sum(x))) in a project node will cause the same symbol to be updated in a sort node. Then mapping the sort node would create a recursive aggregate symbol. -- 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 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009