May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-50) Federate process hangs after the execution and never exits

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-50?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-50. --------------------------------- Resolution: Done Moved the transaction jar into the patches directory and updated the post delegating override logic to also look at patch entries. > Federate process hangs after the execution and never exits > ---------------------------------------------------------- > > Key: TEIID-50 > URL: https://jira.jboss.org/jira/browse/TEIID-50 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.1.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > After executing the "example" code in the Federate Embedded, the process (JVM) is failing to exit. Normally, when the main thread dies all the non-daemon threads should exit too. -- 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-615) Embedded example scripts contain references to 6.0.0

by Steven Hawkins (JIRA)

Embedded example scripts contain references to 6.0.0 ---------------------------------------------------- Key: TEIID-615 URL: https://jira.jboss.org/jira/browse/TEIID-615 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The launch scripts in the kit need updated to include appropriate version information. -- 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-600) Better handling of connector depdendencies

by Steven Hawkins (JIRA)

Better handling of connector depdendencies ------------------------------------------ Key: TEIID-600 URL: https://jira.jboss.org/jira/browse/TEIID-600 Project: Teiid Issue Type: Quality Risk Components: Connector API Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.1.0 Connector dependencies by in large really fall into two categories - our built-in jars or jars that are intended to be at a system level (such as a driver). By only allowing these jars to exist under a post delegation class loader there are many downsides - it has a negative impact on memory, it can cause issues with classloader leaks, makes built in connector patching more difficult, and simply won't work in the case of native oracle drivers. Here are the steps we would like to take to address this: Promote all top-level built-in connector jars to the lib - this would be things like connector-jdbc, connector-ldap, etc. Add the notion of the common extension classpath to the dqp. Change the common extension classpath to be a delegating classloader. Change the meaning of the connector classpath to "required common dependencies", then at the start of any connector service ensure/add all entries from the connector classpath into the common extension classpath. The common extension classpath will be cached and managed similar to the connector classloader cache. Changes to extension modules will cause it to be reloaded. Since this approach does not actually threat connector classpath setting as a classpath ordering of the entries doe not matter and thus patch jars would not be useful in this setting. Rather users would simply replace the extension module they are attempting to patch. The connector type classpath would remain and still specifies required post delegation libraries. How Designer is managing dependencies does not need to initially change at all. Basically all jars added as connector dependencies will be treated as common. The only scenario that won't work initially is a custom connector requiring post-delegation libraries. We can address this at a later time. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-473) Fix defect in ExtractFunctionModifier that prevents it from handling column refs correctly.

by Jerry Helbling (JIRA)

Fix defect in ExtractFunctionModifier that prevents it from handling column refs correctly. ------------------------------------------------------------------------------------------- Key: TEIID-473 URL: https://jira.jboss.org/jira/browse/TEIID-473 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.x Reporter: Jerry Helbling Assignee: Jerry Helbling Priority: Minor Refers to internal case 280004. Fix defect in ExtractFunctionModifier that prevents it from handling column refs correctly. -- 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] Updated: (TEIID-50) Federate process hangs after the execution and never exits

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-50?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-50: -------------------------------- Component/s: Build/Kits Fix Version/s: 6.1.0 (was: 6.0.0) Priority: Critical (was: Major) > Federate process hangs after the execution and never exits > ---------------------------------------------------------- > > Key: TEIID-50 > URL: https://jira.jboss.org/jira/browse/TEIID-50 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.1.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > After executing the "example" code in the Federate Embedded, the process (JVM) is failing to exit. Normally, when the main thread dies all the non-daemon threads should exit too. -- 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] Reopened: (TEIID-50) Federate process hangs after the execution and never exits

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-50?page=com.atlassian.jira.plugi... ] Steven Hawkins reopened TEIID-50: --------------------------------- Assignee: Steven Hawkins (was: Ramesh Reddy) If the teiid txn jar is in the classpath after the jbossjta jar, then our patches are not picked up. > Federate process hangs after the execution and never exits > ---------------------------------------------------------- > > Key: TEIID-50 > URL: https://jira.jboss.org/jira/browse/TEIID-50 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 6.1.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > After executing the "example" code in the Federate Embedded, the process (JVM) is failing to exit. Normally, when the main thread dies all the non-daemon threads should exit too. -- 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-613) CDK is incomplete

by Steven Hawkins (JIRA)

CDK is incomplete ----------------- Key: TEIID-613 URL: https://jira.jboss.org/jira/browse/TEIID-613 Project: Teiid Issue Type: Bug Components: Build/Kits Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.1.0 The cdk is being built without transitive dependencies, so it lacks common-internal. It should be changed to transitive (there will be some unused dependencies included in the lib, but that won't hurt anything). -- 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] Updated: (TEIID-612) Connector Bindings Property Panel requires selecting Apply twice to activate change.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-612?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-612: --------------------------------- Fix Version/s: 6.1.1 > Connector Bindings Property Panel requires selecting Apply twice to activate change. > ------------------------------------------------------------------------------------ > > Key: TEIID-612 > URL: https://jira.jboss.org/jira/browse/TEIID-612 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.1.0 > Environment: Console on Windows > Reporter: Warren Gibson > Priority: Minor > Fix For: 6.1.1 > > > When applying changes to the Connector Bindings Property panel user must select the Apply button twice to get the change to take. -- 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] Updated: (TEIID-611) Virtual Database Import Wizard Step 1 - the NEXT button does not activate without clicking other areas

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-611?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-611: --------------------------------- Fix Version/s: 6.1.1 > Virtual Database Import Wizard Step 1 - the NEXT button does not activate without clicking other areas > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-611 > URL: https://jira.jboss.org/jira/browse/TEIID-611 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.1.0 > Environment: Console on Windows > Reporter: Warren Gibson > Fix For: 6.1.1 > > > When importing a VDB the first step of the import wizard will not activate the NEXT button until user clicks around in the file system selector and returns to select the 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-538) Using adminapi, importing VDB subsequent times causes a an exception that says the VDB already exist in the extensions

by Van Halbert (JIRA)

Using adminapi, importing VDB subsequent times causes a an exception that says the VDB already exist in the extensions ---------------------------------------------------------------------------------------------------------------------- Key: TEIID-538 URL: https://jira.jboss.org/jira/browse/TEIID-538 Project: Teiid Issue Type: Bug Components: AdminApi, Server Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Van Halbert A VDB cannot be imported more than once because subsequent imports causes an exception that says the VDB already exist in the extensions. There are 2 problems here: 1. The actual exception, SQL Exception - invalid sql, wasn't seen 2. The sql being used was missing a ending quote. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009