May 2013 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1699: ---------------------------------------- I think we need to shore this feature up a bit. The use case, from my perspective, is a developer who is upgrading from an local 7.7.1 AS + Teiid 8.3 to a 7.8 AS + Teiid 8.4. Both URL's Hosts/Ports will be the same AND I want to test against both (not running at the same time) and switch between them. Probably need to look at our naming requirements and the registry > Issue with ServerView leads to Out of Memory condition > ------------------------------------------------------ > > Key: TEIIDDES-1699 > URL: https://issues.jboss.org/browse/TEIIDDES-1699 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view. > In my situation, I have > 1) JBoss AS5.1 / Teiid 7.7 server > 2) JBoss AS7.1 / Teiid 8.3 servers > The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes. > I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet. > Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1700) Closing projects results in NPE's trying to run preview vdb jobs with closed projects.

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1700: -------------------------------------- Summary: Closing projects results in NPE's trying to run preview vdb jobs with closed projects. Key: TEIIDDES-1700 URL: https://issues.jboss.org/browse/TEIIDDES-1700 Project: Teiid Designer Issue Type: Bug Components: Data Preview, VDB & Execution Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 8.2 Preview manager framework assumes it has open projects when it spawns jobs. Need to add a little logic to insure that projects are OPEN before proceeding -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1699: ------------------------------------------- The TeiidServerManager class governs the live registry of TeiidServers. However, it simply is an arraylist so would support duplicates. However, the internalAdd and internalRemove methods are governed by the isRegistered(TeiidServer) method which checks the server based on URL and username. Likewise, the TeiidServerAdapterFactory which determines the display of Teiid servers in the server view, iterates through the registry and find the server which has the JBoss Server as a parent. This is an instance equality check so I don't think this would be the problem. My gut feeling is that all your 8.3 servers have the same URL and same user, ie. all localhost and all admin, all using port 9999. As such it is unsurprising that they start confusing each other when a JBoss instance is started. The use case of having more than one server on a single host is impossible to satisfy since there is no way to identify uniquely the distinct servers. You can try debugging the TeiidServerManager to conclude if this is the case. > Issue with ServerView leads to Out of Memory condition > ------------------------------------------------------ > > Key: TEIIDDES-1699 > URL: https://issues.jboss.org/browse/TEIIDDES-1699 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Paul Richardson > Fix For: 8.2 > > > I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view. > In my situation, I have > 1) JBoss AS5.1 / Teiid 7.7 server > 2) JBoss AS7.1 / Teiid 8.3 servers > The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes. > I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet. > Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1699: ----------------------------------------- Assignee: Mark Drilling (was: Paul Richardson) > Issue with ServerView leads to Out of Memory condition > ------------------------------------------------------ > > Key: TEIIDDES-1699 > URL: https://issues.jboss.org/browse/TEIIDDES-1699 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view. > In my situation, I have > 1) JBoss AS5.1 / Teiid 7.7 server > 2) JBoss AS7.1 / Teiid 8.3 servers > The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes. > I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet. > Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1259) USABILITY: When reconciling transformation and reserved word is encountered, can the error message indicate its a reserved word

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1259?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1259: ----------------------------------------- Re-tested in Designer 8.1 Final. The error message is much clearer now: TEIID31100 Parsing error: Encountered ", SUM([*]value[*]) FROM" at line 2, column 208. Was expecting: "char" | "cast" | "convert" | "all" | "any" | "array_agg" | "case" | "distinct" | "exists" | "false" ... Not specific to the reserved word, but better. Van, you OK with closing this? > USABILITY: When reconciling transformation and reserved word is encountered, can the error message indicate its a reserved word > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1259 > URL: https://issues.jboss.org/browse/TEIIDDES-1259 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Minor > Fix For: 8.2 > > > When the reconciler is validating the sql and a use of a reserved word is the cause of the invalidation, could the error message indicate as such? This may have already been done, but I didn't see a jira indicating it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1699: --------------------------------------- Summary: Issue with ServerView leads to Out of Memory condition Key: TEIIDDES-1699 URL: https://issues.jboss.org/browse/TEIIDDES-1699 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 8.1 Reporter: Mark Drilling Assignee: Paul Richardson Fix For: 8.2 I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view. In my situation, I have 1) JBoss AS5.1 / Teiid 7.7 server 2) JBoss AS7.1 / Teiid 8.3 servers The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes. I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet. Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1694) Need a more obvious way to change the Default Server

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1694?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1694. ------------------------------------- Resolution: Done Added a link in the Default Server panel, for changing the default server. Also made some improvements to the server selection dialog and added the action to the Guides view menu. Pull request - https://github.com/Teiid-Designer/teiid-designer/pull/149 > Need a more obvious way to change the Default Server > ---------------------------------------------------- > > Key: TEIIDDES-1694 > URL: https://issues.jboss.org/browse/TEIIDDES-1694 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > It is not obvious how to change the default server in Designer. I'd recommend a button/link on the 'Default Teiid Server' area to select a different server. > Also add the "Set Default Server" action to the Modeling Actions.... menu in the Advisor View. > * see AdvisorActionFactory, AdvisorUiConstants, AdvisorActionFactory.addActionsLibraryToMenu() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1417: ---------------------------------------- Maybe, but depends on how complex the fix was. Can you pinpoint the delta that solved this issue from your Refactoring of the Refactor framework? > Problems After Renaming Model Which Is A Dependency For Other Models > -------------------------------------------------------------------- > > Key: TEIIDDES-1417 > URL: https://issues.jboss.org/browse/TEIIDDES-1417 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 8.2 > > > After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs: > Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>" > Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur. > The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found. > See forum post for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1417: ----------------------------------------- Assignee: Barry LaFond (was: Paul Richardson) Barry, This has been fixed for 8.2. Should this be backported to 7.7? > Problems After Renaming Model Which Is A Dependency For Other Models > -------------------------------------------------------------------- > > Key: TEIIDDES-1417 > URL: https://issues.jboss.org/browse/TEIIDDES-1417 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 8.2 > > > After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs: > Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>" > Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur. > The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found. > See forum post for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1622) Sort out the refactoring framework

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1622?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1622. --------------------------------------- Resolution: Done > Sort out the refactoring framework > ---------------------------------- > > Key: TEIIDDES-1622 > URL: https://issues.jboss.org/browse/TEIIDDES-1622 > Project: Teiid Designer > Issue Type: Enhancement > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 8.2 > > > The refactor actions (rename/move/rename-namespace/delete) have been organically developed and patched over the course of several years and as such lack a consistent approach in their operations. > Re-implement the logic of each action using Eclipse's refactoring framework. This will include the following features as a standard part of the implementation: > * Ties into Eclipse's history framework so resources can be restored to a previous state > * Provides a UI so that the user can preview and accept the changes prior to them being performed > * Sensible separation of condition-checking and actual operation > * Functions in the same manner as existing Eclipse refactoring functionality -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2013