April 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2461) Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2461?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-2461: ----------------------------------------------- so I suggest open a bug in JBIDE requesting the API if it is missing and [~rob.stryker] can look at it when he returns. afaik the server uses the timeout defined in the server adapter, but I'm not sure since I do recall the management layer having its own set of timeouts. Is this issue here that the server is just too long to respond or how ? generally the timeouts been like 5-10 seconds which should be sufficient for any sensible IDE communication or ? p.s. we just released JBDS 8.1.0 which was planned to be last release of the Luna based versions so if it needs backporting please put some info/reasoning into the JBIDE issue as otherwise it will be done for JBDS 9. > Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-2461 > URL: https://issues.jboss.org/browse/TEIIDDES-2461 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 9.1, 9.0.2 > > > The teiid-designer cannot connect to remote JDV server by timeout exceptions[1]. However, the teiid-designer cannnot set timeout for it. > [1] > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336) > at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153) > at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) > at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742) > at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201) > at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72) > at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325) > ... 23 more > Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 25 more > Additional information: > We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2475) In a Table Editor for View model, Primary Key Tab's "column" modal panel does not list all of entries which user can choose

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2475?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2475: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1209308 > In a Table Editor for View model, Primary Key Tab's "column" modal panel does not list all of entries which user can choose > --------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2475 > URL: https://issues.jboss.org/browse/TEIIDDES-2475 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 9.0 > Environment: JBDS 8.1.0.GA > Teiid Designer 9.0.1.Final-v20150211-1407-B643 > Reporter: hisao furuichi > > In a Table Editor for View model, Primary Key Tab's "column" modal panel does not list all of entries which user can choose. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2475) In a Table Editor for View model, Primary Key Tab's "column" modal panel does not list all of entries which user can choose

by hisao furuichi (JIRA)

hisao furuichi created TEIIDDES-2475: ---------------------------------------- Summary: In a Table Editor for View model, Primary Key Tab's "column" modal panel does not list all of entries which user can choose Key: TEIIDDES-2475 URL: https://issues.jboss.org/browse/TEIIDDES-2475 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 9.0 Environment: JBDS 8.1.0.GA Teiid Designer 9.0.1.Final-v20150211-1407-B643 Reporter: hisao furuichi In a Table Editor for View model, Primary Key Tab's "column" modal panel does not list all of entries which user can choose. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2337) Add Swagger UI to Expose VDB RESTFul Procedures

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2337?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2337: -------------------------------- Fix Version/s: 9.1 9.0.2 Beta1 > Add Swagger UI to Expose VDB RESTFul Procedures > ----------------------------------------------- > > Key: TEIIDDES-2337 > URL: https://issues.jboss.org/browse/TEIIDDES-2337 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.6 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > Should investigate adding Swagger to expose RESTFul procedures in a given VDB. > http://swagger.io/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2337) Add Swagger UI to Expose VDB RESTFul Procedures

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2337?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2337: ----------------------------------- Assignee: Barry LaFond (was: Ted Jones) > Add Swagger UI to Expose VDB RESTFul Procedures > ----------------------------------------------- > > Key: TEIIDDES-2337 > URL: https://issues.jboss.org/browse/TEIIDDES-2337 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.6 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > Should investigate adding Swagger to expose RESTFul procedures in a given VDB. > http://swagger.io/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2337) Add Swagger UI to Expose VDB RESTFul Procedures

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2337?page=com.atlassian.jira.plu... ] Ted Jones reopened TEIIDDES-2337: --------------------------------- Reopening to add to master > Add Swagger UI to Expose VDB RESTFul Procedures > ----------------------------------------------- > > Key: TEIIDDES-2337 > URL: https://issues.jboss.org/browse/TEIIDDES-2337 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.6 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 9.1, 9.0.2 Beta1, 9.0.2 > > > Should investigate adding Swagger to expose RESTFul procedures in a given VDB. > http://swagger.io/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2474) Update rest logic to be streaming

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2474?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2474: ----------------------------------- Fix Version/s: 9.3 > Update rest logic to be streaming > --------------------------------- > > Key: TEIIDDES-2474 > URL: https://issues.jboss.org/browse/TEIIDDES-2474 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Web Services Support > Reporter: Steven Hawkins > Fix For: 9.3 > > > With TEIID-3390 Teiid will by default cleanup temp lobs when a result/statement is closed. TeiidRSProviderPost would need to implement StreamingOutput or other logic similar to the server side TeiidRSProvider to properly handle the streaming. As a workaround older generated rest wars will need to be setup with connection pools that set the session variable clean_lobs_onclose to false - see https://docs.jboss.org/author/display/TEIID/LOBs -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2473) Support multiple metadata tags

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2473?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2473: ----------------------------------- Fix Version/s: 9.3 > Support multiple metadata tags > ------------------------------ > > Key: TEIIDDES-2473 > URL: https://issues.jboss.org/browse/TEIIDDES-2473 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Fix For: 9.3 > > > With TEIID-3372 we allowed metadata tags under a model, rather than relying on comma separated values. Any Designer side logic dealing with the DMR layer will need to be updated to match the new server side logic - see ModelMetaData getSourceMetadataType and getSourceMetadataText -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2474) Update rest logic to be streaming

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-2474: ---------------------------------------- Summary: Update rest logic to be streaming Key: TEIIDDES-2474 URL: https://issues.jboss.org/browse/TEIIDDES-2474 Project: Teiid Designer Issue Type: Quality Risk Components: Web Services Support Reporter: Steven Hawkins With TEIID-3390 Teiid will by default cleanup temp lobs when a result/statement is closed. TeiidRSProviderPost would need to implement StreamingOutput or other logic similar to the server side TeiidRSProvider to properly handle the streaming. As a workaround older generated rest wars will need to be setup with connection pools that set the session variable clean_lobs_onclose to false - see https://docs.jboss.org/author/display/TEIID/LOBs -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2473) Support multiple metadata tags

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2473?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-2473: ------------------------------------- Description: With TEIID-3372 we allowed metadata tags under a model, rather than relying on comma separated values. Any Designer side logic dealing with the DMR layer will need to be updated to match the new server side logic - see ModelMetaData getSourceMetadataType and getSourceMetadataText (was: To allow for a more flexible configuration, we should support multiple metadata tags under a model, rather than relying on comma separated values.) > Support multiple metadata tags > ------------------------------ > > Key: TEIIDDES-2473 > URL: https://issues.jboss.org/browse/TEIIDDES-2473 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > With TEIID-3372 we allowed metadata tags under a model, rather than relying on comma separated values. Any Designer side logic dealing with the DMR layer will need to be updated to match the new server side logic - see ModelMetaData getSourceMetadataType and getSourceMetadataText -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 April 2015