December 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information

by Patrick Deenen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ] Patrick Deenen updated TEIIDDES-1861: ------------------------------------- Attachment: Teiiddes-1861-screencapture.m4v As you can in the attached screen capture this problem is easy to reproduce and very annoying as we expect to have many security conditions in the final design. > Designer deletes data role "condition" information > -------------------------------------------------- > > Key: TEIIDDES-1861 > URL: https://issues.jboss.org/browse/TEIIDDES-1861 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration, VDB & Execution > Affects Versions: 8.2 > Environment: Windows 7, Eclipse kepler. > Reporter: Pablo Navascues > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: Teiiddes-1861-screencapture.m4v > > > Create a VDB > Create a source model by importing from JDBC > Add model to VDB > Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)" > Synchronize, save VBD. > Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml. > Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well. > This has happened more than once and to more than one developer in the team. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1971: ----------------------------------- Fix Version/s: 8.4 (was: 8.3) > Connection Reset by Peer messages appearing in JBoss log > -------------------------------------------------------- > > Key: TEIIDDES-1971 > URL: https://issues.jboss.org/browse/TEIIDDES-1971 > Project: Teiid Designer > Issue Type: Bug > Reporter: Steven Hawkins > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.4 > > Attachments: retransmission-packet.png, server.log > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1982) Improve Error Dialog message for VDB deployment where source doesnt exist

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1982?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1982: ------------------------------------ Attachment: ErrorDialog.png MongoProjectSet.zip Attaching project set and error dialog screenshot. > Improve Error Dialog message for VDB deployment where source doesnt exist > ------------------------------------------------------------------------- > > Key: TEIIDDES-1982 > URL: https://issues.jboss.org/browse/TEIIDDES-1982 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Fix For: 8.4 > > Attachments: ErrorDialog.png, MongoProjectSet.zip > > > In some cases, when a user tries to deploy a VDB where one of the SourceModel DS does not exist, the user is prompted whether to create the source. > I encountered a case though where an Error Dialog was displayed instead, with the message "No Connection Information in model xxx.xmi". For this case(Mongo) there is no CP available. > Attaching model project set to reproduce, and a screen shot of the dialog. > Message could be more informative, e.g. "The Data Source for model xxx.xmi cannot be found on server, and no CP information is available" or similar. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1982) Improve Error Dialog message for VDB deployment where source doesnt exist

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1982: --------------------------------------- Summary: Improve Error Dialog message for VDB deployment where source doesnt exist Key: TEIIDDES-1982 URL: https://issues.jboss.org/browse/TEIIDDES-1982 Project: Teiid Designer Issue Type: Enhancement Components: VDB & Execution Affects Versions: 8.2 Reporter: Mark Drilling Fix For: 8.4 In some cases, when a user tries to deploy a VDB where one of the SourceModel DS does not exist, the user is prompted whether to create the source. I encountered a case though where an Error Dialog was displayed instead, with the message "No Connection Information in model xxx.xmi". For this case(Mongo) there is no CP available. Attaching model project set to reproduce, and a screen shot of the dialog. Message could be more informative, e.g. "The Data Source for model xxx.xmi cannot be found on server, and no CP information is available" or similar. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ] Paul Richardson edited comment on TEIIDDES-1971 at 12/6/13 9:58 AM: -------------------------------------------------------------------- I have been able to create the peer reset messages in the log by simply clicking the refresh Teiid Instance button in the Servers View. It does not happen on every click but most clicks will generate anywhere from 1-5 peer reset messages. Thus, it appears that the reconnect function is trying to do too much without waiting for the server to complete its response. Evidence for this at the packet level might indicate this (see retransmission-packet snapshot image attached. Ruled out Designer calling teiid-client-related functions too many times but commenting out all listeners reacting to the reconnection of the teiid instance. Even when the only part of Designer that interfaces with teiid is the reconnection, the connection reset messages still appear. was (Author: phantomjinx): I have been able to create the peer reset messages in the log but clicking the refresh Teiid Instance button in the Servers View. It does not happen on every click but most clicks will generate anywhere from 2-5 peer reset messages. Thus, it appears that the reconnect function is trying to do too much without waiting for the server to complete its response. Evidence for this at the packet level might indicate this (see retransmission-packet snapshot image attached. > Connection Reset by Peer messages appearing in JBoss log > -------------------------------------------------------- > > Key: TEIIDDES-1971 > URL: https://issues.jboss.org/browse/TEIIDDES-1971 > Project: Teiid Designer > Issue Type: Bug > Reporter: Steven Hawkins > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.3 > > Attachments: retransmission-packet.png, server.log > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1981: ------------------------------------ Fix Version/s: 8.4 (was: 8.3) > MongoDB issues in Designer > -------------------------- > > Key: TEIIDDES-1981 > URL: https://issues.jboss.org/browse/TEIIDDES-1981 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.4 > > Attachments: MongoCP.xml, plugin.properties, plugin.xml > > > Attempt to model and query MongoDB in Designer > 1) Mongo CP is not available in default JBDS > 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1981: ----------------------------------------- Yes, we were aware that translator doesnt return the schema DDL. Teiid Connection importer notifies the user and it is disallowed. I was trying to hand model, then preview or deploy in Designer and could not get it to work. After some more exploring by Barry and I, here is current status of Designer support: - Birt project does have a Connection Profile for Mongo, but it is not in our JBDS configuration. That is something we may look to expose in the next release. - Because we do not have the CP, preview will not be available. - So currently to deploy a VDB containing Mongo Source in Designer 1) Create/Deploy the Mongo source using TeiidConnection importer (or create manually on server) 2) Create Source model manually in Designer 3) Create VDB and Add source model. Make sure the Source binding name / jndi name matches the source created in #1 4) this allows the vdb to be deployed from designer Pushing to 8.4 for consideration of CP stuff. > MongoDB issues in Designer > -------------------------- > > Key: TEIIDDES-1981 > URL: https://issues.jboss.org/browse/TEIIDDES-1981 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.3 > > Attachments: MongoCP.xml, plugin.properties, plugin.xml > > > Attempt to model and query MongoDB in Designer > 1) Mongo CP is not available in default JBDS > 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1981) MongoDB issues in Designer

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1981?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1981: ---------------------------------------- Please note that currently MongoDB translator is *NOT* capable of returning metadata, so using with "Teiid Connection" importer will not work. The user must hand model, or import a schema from some other database and then edit to add additional metadata extensions to make it work with MongoDB. For full details see the MongoDB documentation in Teiid Documents. > MongoDB issues in Designer > -------------------------- > > Key: TEIIDDES-1981 > URL: https://issues.jboss.org/browse/TEIIDDES-1981 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.3 > > Attachments: MongoCP.xml, plugin.properties, plugin.xml > > > Attempt to model and query MongoDB in Designer > 1) Mongo CP is not available in default JBDS > 2) We cannot set the Mongo CP on source model - not supported. We do not have a connectionProvider -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1971: ------------------------------------------- I have been able to create the peer reset messages in the log but clicking the refresh Teiid Instance button in the Servers View. It does not happen on every click but most clicks will generate anywhere from 2-5 peer reset messages. Thus, it appears that the reconnect function is trying to do too much without waiting for the server to complete its response. Evidence for this at the packet level might indicate this (see retransmission-packet snapshot image attached. > Connection Reset by Peer messages appearing in JBoss log > -------------------------------------------------------- > > Key: TEIIDDES-1971 > URL: https://issues.jboss.org/browse/TEIIDDES-1971 > Project: Teiid Designer > Issue Type: Bug > Reporter: Steven Hawkins > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.3 > > Attachments: retransmission-packet.png, server.log > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ] Paul Richardson updated TEIIDDES-1971: -------------------------------------- Attachment: retransmission-packet.png > Connection Reset by Peer messages appearing in JBoss log > -------------------------------------------------------- > > Key: TEIIDDES-1971 > URL: https://issues.jboss.org/browse/TEIIDDES-1971 > Project: Teiid Designer > Issue Type: Bug > Reporter: Steven Hawkins > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.3 > > Attachments: retransmission-packet.png, server.log > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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, 4 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 December 2013