May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-610) Deleted connector bindings remain in the system state

by Steven Hawkins (JIRA)

Deleted connector bindings remain in the system state ----------------------------------------------------- Key: TEIID-610 URL: https://jira.jboss.org/jira/browse/TEIID-610 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.1 If a connector binding is first stopped and then removed, it remains in the system state (but is otherwise removed from the system). -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-608) Prevent duplicate hostcontroller launches

by Steven Hawkins (JIRA)

Prevent duplicate hostcontroller launches ----------------------------------------- Key: TEIID-608 URL: https://jira.jboss.org/jira/browse/TEIID-608 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 Even if the hostcontroller persistent process is removed, we still need to ensure that multiple attempts to launch processes works well. The worst issue right now is that the log of the original hostconroller will be replaced with the new (which then immediately exits). See also TEIID-601 -- 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

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-360) SQLServer SQLTranslator issues

by Steven Hawkins (JIRA)

SQLServer SQLTranslator issues ------------------------------ Key: TEIID-360 URL: https://jira.jboss.org/jira/browse/TEIID-360 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 The time literal for Access/SQLServer is incorrect - should use 1970 not 1900 Limit for a set op needs to use a subquery Support for repeat should be aliased to replicate -- 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

14 years, 1 month

1
7
0 / 0

[JBoss JIRA] Created: (TEIID-455) Config edits should use optimistic locking

by Steven Hawkins (JIRA)

Config edits should use optimistic locking ------------------------------------------ Key: TEIID-455 URL: https://jira.jboss.org/jira/browse/TEIID-455 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Config edits are atomic, but do not enforce consistency - the last one always wins. Optimistic locking should be used to properly ensure consistency. Also versions should be restorable. Currently it's not expected that multiple admins will be making changes concurrently, so this is not a critical 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

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (TEIID-509) Add new logging level so that server startup information can be logged and be differentiated from critical/warning level entries

by Van Halbert (JIRA)

Add new logging level so that server startup information can be logged and be differentiated from critical/warning level entries -------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-509 URL: https://jira.jboss.org/jira/browse/TEIID-509 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Van Halbert Assignee: Steven Hawkins Currently, at server startup, nothing is being written to the hostcontroller or vmprocess logs. The previous server started information is no longer being written because of the log level wasn't being differentiated from actual critical/warning messages. Therefore, a new level should be created so that the minimal server startup information can continue to be written to the logs. -- 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

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-381) Migrate Teiid JOPR Plugin from Product to Project

by Ted Jones (JIRA)

Migrate Teiid JOPR Plugin from Product to Project -------------------------------------------------- Key: TEIID-381 URL: https://jira.jboss.org/jira/browse/TEIID-381 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Ted Jones Assignee: Ted Jones Fix For: 6.0.0 The Teiid JOPR Plugin source currently resides on the project side. It needs to be moved to project and incorporated into the TEIID build process. -- 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

14 years, 7 months

4
10
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

14 years, 7 months

3
7
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

14 years, 7 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

14 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIID-484) Upgrade JGroups to 2.6.10

by Ramesh Reddy (JIRA)

Upgrade JGroups to 2.6.10 ------------------------- Key: TEIID-484 URL: https://jira.jboss.org/jira/browse/TEIID-484 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Upgrade the JGroups version to 2.6.10 to be in sync with what is been used in AS 5.1.0. Need to make sure this is version is being used in EAP release before upgrade. -- 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

14 years, 7 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009