[JBoss JIRA] (TEIIDDES-1931) StackOverFlow when restoring TeiidServerManager state
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1931:
-----------------------------------------
Summary: StackOverFlow when restoring TeiidServerManager state
Key: TEIIDDES-1931
URL: https://issues.jboss.org/browse/TEIIDDES-1931
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 8.3
Reporter: Paul Richardson
Fix For: 8.3
When starting designer with a saved server model, the TeiidServerManager is restored. However, 2 types of stack over flow exceptions can occur.
ModelerCore makes the init of the manager thread-safe by surrounding the construction with a synchronized object. However, this does not prevent the same thread calling it. This can occur when the newly constructed TeiidServers call their disconnect method, which uses the manager to notify any interested listeners.
First, the use of the manager here can mean the potential creation of a second manager, looping ad infinitem. Fixing this in ModelerCore, then has the difficulty that the single 'restoring' manager tries to notify the interested listeners. If such listeners have already been assigned, eg. PreviewManager, then they can start trying to use the manager illegally before its completed restoration.
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1930) NPE running Preview Data from Guides View
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1930:
--------------------------------------
Summary: NPE running Preview Data from Guides View
Key: TEIIDDES-1930
URL: https://issues.jboss.org/browse/TEIIDDES-1930
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.3
While testing Import JDBC action guide, ran into NPE running preview data action:
java.lang.NullPointerException
at org.eclipse.core.runtime.Path.append(Path.java:261)
at org.teiid.designer.ui.viewsupport.DesignerPropertiesUtil.getPreviewTargetModel(DesignerPropertiesUtil.java:357)
at org.teiid.designer.ui.viewsupport.DesignerPropertiesUtil.getPreviewTargetObject(DesignerPropertiesUtil.java:374)
at org.teiid.designer.runtime.ui.preview.PreviewDataDialog.createContents(PreviewDataDialog.java:173)
at org.eclipse.jface.window.Window.create(Window.java:432)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.eclipse.jface.window.Window.open(Window.java:791)
at org.teiid.designer.runtime.ui.preview.PreviewDataAction.run(PreviewDataAction.java:55)
at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:590)
at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.launchGuidesAction(TeiidGuidesSection.java:252)
at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.access$1(TeiidGuidesSection.java:244)
at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection$3.doubleClick(TeiidGuidesSection.java:153)
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1914) Recursive element - mismatch column names between mapping classes
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1914?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1914.
-------------------------------------
Resolution: Done
The validation rule was working as expected, but the messages were not very specific. I made a couple changes to the error messages:
- Re-worded the message, including the specific problem column name
- now only generate the first error message encountered, rather than several for the same mapping class. In this example, four messages were being generated and that has been reduced to one.
pull request - https://github.com/Teiid-Designer/teiid-designer/pull/263
Another issue that I encountered is that once you copy the MC columns into the supervisor MC in the wrong order, there is no easy way to re-order them. I was able to change the order by deleting/creating columns, but we may want to open another enhancement JIRA to allow re-ordering.
> Recursive element - mismatch column names between mapping classes
> -----------------------------------------------------------------
>
> Key: TEIIDDES-1914
> URL: https://issues.jboss.org/browse/TEIIDDES-1914
> Project: Teiid Designer
> Issue Type: Feature Request
> Affects Versions: 8.2
> Environment: JBDS 7.0.1.GA, Teiid Designer 8.2Final
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
> Fix For: 8.3
>
> Attachments: Recursive2.zip
>
>
> I run the E2eRecursiveXmlTextSourceTestScript; the XML view model from XSD contains mapping classes Employee and Supervisor. Next I copy the attributes from Employee to Supervisor. If the order of columns in Supervisor isn't the same as in Employee, I get
> "Mismatch column name between mapping class Employee and Supervisor"
> I am not sure if this is bug or if the message error is considered self-explanatory.
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1914) Recursive element - mismatch column names between mapping classes
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1914?page=com.atlassian.jira.plu... ]
Lucie Fabrikova updated TEIIDDES-1914:
--------------------------------------
Attachment: Recursive2.zip
> Recursive element - mismatch column names between mapping classes
> -----------------------------------------------------------------
>
> Key: TEIIDDES-1914
> URL: https://issues.jboss.org/browse/TEIIDDES-1914
> Project: Teiid Designer
> Issue Type: Feature Request
> Affects Versions: 8.2
> Environment: JBDS 7.0.1.GA, Teiid Designer 8.2Final
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
> Fix For: 8.3
>
> Attachments: Recursive2.zip
>
>
> I run the E2eRecursiveXmlTextSourceTestScript; the XML view model from XSD contains mapping classes Employee and Supervisor. Next I copy the attributes from Employee to Supervisor. If the order of columns in Supervisor isn't the same as in Employee, I get
> "Mismatch column name between mapping class Employee and Supervisor"
> I am not sure if this is bug or if the message error is considered self-explanatory.
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems - TeiidServerManager initialization problem
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1885:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1032157|https://bugzilla.redhat.com/show_bug.cgi?id=1032157] from NEW to CLOSED
> DDL importer problems - TeiidServerManager initialization problem
> ------------------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 8.3
>
> Attachments: ddl-import, stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
> see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems - TeiidServerManager initialization problem
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Lucie Fabrikova closed TEIIDDES-1885.
-------------------------------------
Resolution: Done
> DDL importer problems - TeiidServerManager initialization problem
> ------------------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 8.3
>
> Attachments: ddl-import, stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
> see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems - TeiidServerManager initialization problem
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Lucie Fabrikova commented on TEIIDDES-1885:
-------------------------------------------
The problem seems to be an issue with the automatized test environment setup, I couldn't reproduce it manually as a user.
Workaround for the automatized test: switch to tab "Servers" and invoke the "New server definition" wizard. Next, the DDL can be imported...
> DDL importer problems - TeiidServerManager initialization problem
> ------------------------------------------------------------------
>
> Key: TEIIDDES-1885
> URL: https://issues.jboss.org/browse/TEIIDDES-1885
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 8.3
>
> Attachments: ddl-import, stdcust.ddl
>
>
> When Importing from DDL to create a new view model (DDL File >> Source or View model), the following problems appear:
> a) when choosing auto-select for dialect, the wizard raises the difference panel after hitting Next with generic "Error encountered importing DDL" message and a "No difference report was found" message.
> b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to parse error (as well as a 'No difference report was found" error.
> The DDL in question works in JBDS 6 and earlier.
> Version-Release number of selected component (if applicable):
> JBDS 7 with JBDSIS 7 beta 4
> How reproducible:
> Consistent.
> Steps to Reproduce:
> Import attached DDL via importer.
> see: https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1920:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1028379|https://bugzilla.redhat.com/show_bug.cgi?id=1028379] from ASSIGNED to CLOSED
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: bqt2_sybase_ase_CP.xml, jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1929) View model is changed by attempting to delete dependent source model and previewing delete
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1929?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1929 at 11/21/13 8:01 AM:
------------------------------------------------------------------
Looks like the DeleteResourceRefactoring.indexFile() method is unloading the resource while it's open in an editor which ends up setting Resource.setModified(true). This explains why the diagram goes blank since the EMF objects dissappear.
Thinking the open editor should be detected and closed to prevent this?
was (Author: blafond):
Looks like the DeleteResourceRefactoring.indexFile() method is unloading the resource while it's open in an editor which ends up setting Resource.setModified(true). Thinking the open editor should be detected and closed to prevent this?
> View model is changed by attempting to delete dependent source model and previewing delete
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1929
> URL: https://issues.jboss.org/browse/TEIIDDES-1929
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
> Attachments: TEIIDDES-1929.zip
>
>
> 1) Import attached project set
> 2) Open ProductViews model in editor to show package diagram
> 3) Select ProductsDB2_VDB model and click DELETE
> 4) In Delete refactor wizard click *Preview>* button
> 5) Cancel all and the ProductViews editor tab will be dirty (requires saving) and the package diagram is cleared out.
> Wondering what EMF data is getting set/changed to cause the dirty editor?
--
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, 5 months
[JBoss JIRA] (TEIIDDES-1929) View model is changed by attempting to delete dependent source model and previewing delete
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1929?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1929:
----------------------------------------
Looks like the DeleteResourceRefactoring.indexFile() method is unloading the resource while it's open in an editor which ends up setting Resource.setModified(true). Thinking the open editor should be detected and closed to prevent this?
> View model is changed by attempting to delete dependent source model and previewing delete
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1929
> URL: https://issues.jboss.org/browse/TEIIDDES-1929
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
> Attachments: TEIIDDES-1929.zip
>
>
> 1) Import attached project set
> 2) Open ProductViews model in editor to show package diagram
> 3) Select ProductsDB2_VDB model and click DELETE
> 4) In Delete refactor wizard click *Preview>* button
> 5) Cancel all and the ProductViews editor tab will be dirty (requires saving) and the package diagram is cleared out.
> Wondering what EMF data is getting set/changed to cause the dirty editor?
--
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, 5 months