[JBoss JIRA] (TEIIDDES-2461) Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2461?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2461:
---------------------------------------------------
Matus Makovy <mmakovy(a)redhat.com> changed the Status of [bug 1197529|https://bugzilla.redhat.com/show_bug.cgi?id=1197529] from MODIFIED to VERIFIED
> 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
> Labels: release_notes, verified_jbdsis-8.0.3.CR2
> Fix For: 9.0.3, 9.2
>
> Attachments: jboss-timeout-preference.png
>
>
> 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.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2461) Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2461?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2461:
-----------------------------------
Labels: release_notes verified_jbdsis-8.0.3.CR2 (was: )
> 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
> Labels: release_notes, verified_jbdsis-8.0.3.CR2
> Fix For: 9.0.3, 9.2
>
> Attachments: jboss-timeout-preference.png
>
>
> 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.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2461) Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2461?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2461.
----------------------------------
> 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
> Labels: release_notes, verified_jbdsis-8.0.3.CR2
> Fix For: 9.0.3, 9.2
>
> Attachments: jboss-timeout-preference.png
>
>
> 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.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2620) Add validation rule to check for circular dependencies in view models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2620?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2620:
-----------------------------------
Attachment: CircularDependencyTest.zip
> Add validation rule to check for circular dependencies in view models
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2620
> URL: https://issues.jboss.org/browse/TEIIDDES-2620
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation
> Affects Versions: 9.1, 9.0.3
> Reporter: Barry LaFond
> Fix For: 9.2, 9.0.4
>
> Attachments: CircularDependencyTest.zip
>
>
> Designer currently allows defining transformations (view models) that depend on each other.
> Need to add a validation rule (ERROR) that will detect this circular dependency.
> The result is some actions like *delete* table/column, etc.. will end up in a StackOverflowException here: at org.teiid.designer.core.workspace.WorkspaceResourceFinderUtil.getResourcesThatUse(WorkspaceResourceFinderUtil.java:747)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2620) Add validation rule to check for circular dependencies in view models
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2620:
--------------------------------------
Summary: Add validation rule to check for circular dependencies in view models
Key: TEIIDDES-2620
URL: https://issues.jboss.org/browse/TEIIDDES-2620
Project: Teiid Designer
Issue Type: Bug
Components: Validation
Affects Versions: 9.0.3, 9.1
Reporter: Barry LaFond
Fix For: 9.2, 9.0.4
Designer currently allows defining transformations (view models) that depend on each other.
Need to add a validation rule (ERROR) that will detect this circular dependency.
The result is some actions like *delete* table/column, etc.. will end up in a StackOverflowException here: at org.teiid.designer.core.workspace.WorkspaceResourceFinderUtil.getResourcesThatUse(WorkspaceResourceFinderUtil.java:747)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2619) Salesforce custom URL not added if Datasource is created with Model Info
by Debbie Steigner (JIRA)
Debbie Steigner created TEIIDDES-2619:
-----------------------------------------
Summary: Salesforce custom URL not added if Datasource is created with Model Info
Key: TEIIDDES-2619
URL: https://issues.jboss.org/browse/TEIIDDES-2619
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Affects Versions: 9.0.2
Reporter: Debbie Steigner
Spawning from https://issues.jboss.org/browse/TEIIDDES-2579 regarding Salesforce custom URL. If you run the import with a custom URL, unless you manually create the Data Source with the Connection Profile Info, the Datasource (Resource Adapter) on the server will not contain the custom URL.
So if the customer takes the default on the Create Data Source, which is Model Info or they let Teiid Designer create it when they create the VDB the connection will fail because the custom URL hasn't been written to the server configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2618) Help users dealing with the deprecation of integer design-time datatype
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2618:
----------------------------------------
Summary: Help users dealing with the deprecation of integer design-time datatype
Key: TEIIDDES-2618
URL: https://issues.jboss.org/browse/TEIIDDES-2618
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling, Usability, Validation
Affects Versions: 9.0.3
Reporter: Andrej Šmigala
The Integer datatype has been replaced with the int datatype in previous version of designer, so it is now not possible to set the datatype to integer when creating new models. The integer datatype is however still supported in designer for legacy purposes (importing old projects, vdbs etc). Using integer in deployed vdbs results in some issues when reimporting (e.g. TEIIDDES-2460).
As [suggested here|https://issues.jboss.org/browse/TEIIDDES-2460?focusedCommentId=13099...], designer should issue a validation warning for each integer use and should also provide a quick fix to convert all the usages of integer to int.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months