August 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-764) Error message not found for missing lob tuplesource

by Steven Hawkins (JIRA)

Error message not found for missing lob tuplesource --------------------------------------------------- Key: TEIID-764 URL: https://jira.jboss.org/jira/browse/TEIID-764 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 The error message not found for missing a missing lob tuplesource in LobWorkItem -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-580) Add ability to monitor Connector Connection Pool

by Van Halbert (JIRA)

Add ability to monitor Connector Connection Pool ------------------------------------------------- Key: TEIID-580 URL: https://jira.jboss.org/jira/browse/TEIID-580 Project: Teiid Issue Type: Feature Request Components: AdminApi, Query Engine, Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert Here are the discussed changes to enable connection pool monitoring: - Create a new stat's class to expose the information: ConnectionPoolStats - Enable the ConnectionPool to monitor the following pieces of information: a. Total Connections - Total Number of Connections for the Connection Pool b Available Connections - Number of available connections in the connection pool. c Active Connections - Number of Connections currently supporting clients. d Connections Created - Number of Connections created since the Connection Pool was created. e Connections Destroyed - Number of Connections destroyed since the Connection Pool was created. In the config.xml for the base Connector component type a. Rename the ConnectorMaxThreads to MaxConnections so that it relates better to the user - Expose the ConnectionPoolStats out the adminAPI -- 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, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-767) Combine the memorystoragemanager and the buffermanager

by Steven Hawkins (JIRA)

Combine the memorystoragemanager and the buffermanager ------------------------------------------------------ Key: TEIID-767 URL: https://jira.jboss.org/jira/browse/TEIID-767 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 The memorystoragemanager is always assumed to be available by the buffermanager and would be simpler to implement as TupleBatch references on ManagedBatches. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-785) Embedded usage issues

by Steven Hawkins (JIRA)

Embedded usage issues --------------------- Key: TEIID-785 URL: https://jira.jboss.org/jira/browse/TEIID-785 Project: Teiid Issue Type: Quality Risk Components: Embedded, Server Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Now that the deploy.properties contains security information, the connection properties should not be allowed to override its values in the embedded usage scenario. Also our usage of process name does not truly allow for multiple processes to be used with the same install. For now, we should remove the code that attempt to differentiate the logs based upon the process name and let this issue serve as KI that embedded usage should only be for dedicated scenarios. If multiple classloaders or vms need to share the same install, then server mode should be used. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-772) Fix TestEmbeddedVDBService test in the runtime project

by Van Halbert (JIRA)

Fix TestEmbeddedVDBService test in the runtime project ------------------------------------------------------- Key: TEIID-772 URL: https://jira.jboss.org/jira/browse/TEIID-772 Project: Teiid Issue Type: Bug Affects Versions: 6.2.0 Reporter: Van Halbert Assignee: Van Halbert Fix For: 6.2.0 The TestEmbeddedVDBService test was picking up a different Empty.vdb and was failing locally. Change to look for the TestEmpty vdb. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-474) Need to Hard-code serialVersionUID in LogonResult

by Ted Jones (JIRA)

Need to Hard-code serialVersionUID in LogonResult ------------------------------------------------- Key: TEIID-474 URL: https://jira.jboss.org/jira/browse/TEIID-474 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.1.0 Since com.metamatrix.platform.security.api.LogonResult exists in the teiid-client.jar, it may have a different serialVersionUID than the server when using the server kit and manually building the SOAP war. This causes an invalid serialVersionUID exception trying to connect. The serialVersionUID should be hard-coded to avoid this issue. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-533) HostController Process is redundent and should be removed

by Ramesh Reddy (JIRA)

HostController Process is redundent and should be removed --------------------------------------------------------- Key: TEIID-533 URL: https://jira.jboss.org/jira/browse/TEIID-533 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 6.0.0 Reporter: Ramesh Reddy Fix For: 6.1.0 Host Controller process does not really have significant importance in a server environment and is redundant. The main responsibility of the Host Controller is spawn the process that is the Server. The second responsibility is to act as surviving process during the "bounce", and kill and restart the Server processes. To accomplish this it takes up valuable resources like memory and cluster replication etc. We can accomplish these both task in alternative means Option: 1 Instead of keeping Host Controller alive all the time, it can be retired once the Server process(es) are spawned. When Console or Admin API, request a bounce of server or cluster, it can be communicated to all the participating Servers over the JGroups channel then Server process that received bounce request, can spawn a "nanny" process ( this can be same Host controller which started first time) and kill itself. The the invoked nanny process will finish the starting the process back up. Option: 2 Scripts can written to start the server process first time easily, when the bounce request comes in the process can die with certain unique exit code, scripts can be written such that when they see the bounce specific exit code, they restart the process again. These options have a good side effect, that is when the Server is bounced in the new scenario, any patches submitted can be applied to the new server before they are started. Option2 is simple, however the only hurdle with Option 2 is when single host has two+ processes, and got bounced, then there is possible way to way to communicate back with script, as to which Server process it is responsible to start back up. It can start all of them, but starting a single seems difficult. Please offer suggestions and your preference. If we can not solve the issue with option 2, option 1 will be implemented. -- 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, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIID-652) Custom Connectors: Teiid looks in configuration.xml--not ConfigurationInfo.def--for connector information

by Paul Nittel (JIRA)

Custom Connectors: Teiid looks in configuration.xml--not ConfigurationInfo.def--for connector information --------------------------------------------------------------------------------------------------------- Key: TEIID-652 URL: https://jira.jboss.org/jira/browse/TEIID-652 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Environment: fedora 10, java 1.6.0_10b33, Teiid 6.1.0M4, Designer 6/1/09 Reporter: Paul Nittel Assignee: Steven Hawkins Attachments: Jahoo.vdb I created the Yahoo UDF project and tested it in the Designer. All OK. I exported the VDB to Teiid/deploy and copied the connector jars to Teiid/extensions. I was able to query the two relational sources, but not Yahoo. Ramesh and I found we could add the ConnectorClass and ConnectorClassPath properties to the yahoo binding section of ConfigurationInfo.def and it would work. Deleting those and copying the entire Yahoo ConnectorType sectioninto configuration.xml also worked. Teiid is looking in the wrong place for the connector type information. (Artifacts are attached.) -- 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, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-663) Enrich "embedded" service offerings

by Ramesh Reddy (JIRA)

Enrich "embedded" service offerings ----------------------------------- Key: TEIID-663 URL: https://jira.jboss.org/jira/browse/TEIID-663 Project: Teiid Issue Type: Task Components: Embedded, Query Engine Reporter: Ramesh Reddy Priority: Critical Fix For: 6.2.0 Currently "embedded" is missing service offerings that have been available in the earlier version of the Server offerings. The sub-tasks will define the individual services that needs to be added to "embedded" -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-667) Simplify "Command Logging"

by Ramesh Reddy (JIRA)

Simplify "Command Logging" -------------------------- Key: TEIID-667 URL: https://jira.jboss.org/jira/browse/TEIID-667 Project: Teiid Issue Type: Task Components: Common Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.2.0 Currently the command logging is defined by Tracking Service and it can be extended by the user through "CommandLoggerSPI". This is verbose, Command Logger should be no different than any other logging, only that the messages are sent to a specific context. User should have ability to stream to Teiid log file, or can add appender to separate them from main log file. File based appender should be supported. -- 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, 3 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2009