[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be started with admin rights
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-24084.
---------------------------------
Resolution: Done
> To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be started with admin rights
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24084
> URL: https://issues.jboss.org/browse/JBIDE-24084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM1
> Environment: Windows 10 Pro, x86_64
> HyperV allowed
> Reporter: Ondrej Dockal
> Priority: Blocker
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
>
> One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin rights are not required).
> I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be started with admin rights
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24084:
---------------------------------------
1. Downloaded and installed [devsuite bundle installer|http://cdk-builds.usersys.redhat.com/builds/nightly/devsuite/1....]
2. Close the installer after installation
3. Log out/Log in - this is necessary for changes to hyper-v administrator group to get into place
4. Prepare minishift (setup-cdk)
5. Open devstudio (without admin rights), add cdk server adapter
6. Verified that CDK was successfully started.
> To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be started with admin rights
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24084
> URL: https://issues.jboss.org/browse/JBIDE-24084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM1
> Environment: Windows 10 Pro, x86_64
> HyperV allowed
> Reporter: Ondrej Dockal
> Priority: Blocker
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
>
> One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin rights are not required).
> I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21065.
------------------------------
Verified in Devstudio 10.4.0.GA-v20170511-1748-B62. Closing.
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24233) Server fails to stop when using non-standard management port
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24233?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-24233.
------------------------------
Verified in Devstudio 10.4.0.GA-v20170511-1748-B62. Closing.
> Server fails to stop when using non-standard management port
> ------------------------------------------------------------
>
> Key: JBIDE-24233
> URL: https://issues.jboss.org/browse/JBIDE-24233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.4.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
>
> While testing JBIDE-24006 I found a bug (I think).
> When you change the management port in standalone.xml from 9990 to 9999, the server is able to start, but shows this error upon startup:
> {code}
> Unable to retrieve a list of remote deployment scanners for server WildFly 10.x
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:295)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:293)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:164)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:124)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:114)
> at org.jboss.ide.eclipse.as.ui.dialogs.ModifyDeploymentScannerIntervalDialog$DeploymentScannerUIServerStartedListener$1.run(ModifyDeploymentScannerIntervalDialog.java:82)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:350)
> ... 11 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:124)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 13 more
> {code}
> The server seems to be started alright:
> {code}
> 12:47:43,771 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9999/management
> 12:47:43,771 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9999
> 12:47:43,772 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 3670ms - Started 405 of 655 services (404 services are lazy, passive or on-demand)
> {code}
> And then when I try to stop the server, it fails also:
> Server WildFly 10.x failed to stop.
> {code}
> Could not stop server adapter WildFly 10.x
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.quietlyExecute(Wildfly9Manager.java:373)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.stopServer(Wildfly9Manager.java:284)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.stop(Wildfly9ManagerService.java:162)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.stop(JBoss7ManagerServiceProxy.java:83)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementShutdownController.gracefullStop(ManagementShutdownController.java:81)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stopImpl(LocalLegacyShutdownController.java:129)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:66)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3688)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3645)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.quietlyExecute(Wildfly9Manager.java:368)
> ... 12 more
> Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:124)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 14 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a project without route specified
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-24306.
------------------------------
I successfully connected to JMX through openshift server adapter on application with no route. Verified in Devstudio 10.4.0.GA-v20170511-1748-B62. Closing.
> Cannot connect to JMX through OpenShift Server adapter to a project without route specified
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-24306
> URL: https://issues.jboss.org/browse/JBIDE-24306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
> Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png
>
>
> !image-2017-04-25-14-48-51-427.png|thumbnail!
> in log:
> {noformat}
> eclipse.buildId=10.4.0.AM3-v20170406-1058-B390
> java.version=1.8.0_112
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.core
> Error
> Tue Apr 25 14:47:14 CEST 2017
> An error occurred while opening the connection.
> java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:333)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 5 more
> Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months