July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22008) JBoss EAP 6.x server fails to stop in JBDS 9 , if a port-offset is used.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22008?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22008: -------------------------------- Sprint: devex #118 July 2016 > JBoss EAP 6.x server fails to stop in JBDS 9 , if a port-offset is used. > ------------------------------------------------------------------------ > > Key: JBIDE-22008 > URL: https://issues.jboss.org/browse/JBIDE-22008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Reporter: Harshada Boob > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: .log, Screenshot-JBoss - JBoss EAP 6.4 - JBoss Developer Studio .png > > > 1. When EAP 6.4.x is started with a port-offset, the EAP server starts succesfully and works all good, but there is an issue while stopping the server from JBDS. > 2. It fails to stop when clicking for the first time on the 'stop' button in the 'server' tab/window and then the server process is terminated/killed if you again try to stop the server by second time clicking on the 'stop' button in the server tab. > 3. Attached is the screenshot - which is seen when you try to stop the server for the first time and following exception is seen in the workspace/.metadat/.log file (File attached): > ------------------------------------------------------------------------------------------------------------------- > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed > 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.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132) > 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:291) > 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:289) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:161) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersFromServer(AS7DeploymentScannerUtility.java:249) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServer(LocalJBoss7DeploymentScannerAdditions.java:173) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServerSafely(LocalJBoss7DeploymentScannerAdditions.java:135) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersRemoved(LocalJBoss7DeploymentScannerAdditions.java:150) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:83) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58) > 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:252) > 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: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed > 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) > ... 22 more > Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:10000. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122) > 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) > ... 24 more > Caused by: java.io.EOFException: XNIO000812: Connection closed unexpectedly > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:416) > at org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener.handleEvent(HttpUpgrade.java:400) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:339) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:83) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:114) > ... 34 more > ------------------------------------------------------------------------------------------------------------------ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22653: ------------------------------- Sprint: devex #118 July 2016 > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22653: ---------------------------------- Assignee: Andre Dietisheim > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15189: -------------------------------- Sprint: devex #118 July 2016 > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.1.x, 4.2.x > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22817) Add Events support to Properties view

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22817: ----------------------------------- Summary: Add Events support to Properties view Key: JBIDE-22817 URL: https://issues.jboss.org/browse/JBIDE-22817 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.1.AM1 Reporter: Fred Bricon The web console has an Events tab that lists all events for all resources. We could add the same to the Properties view. Later, we could add support for events per resources, but that requires more work how to layout more infos. That'll be the subject of another issue -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22816: ------------------------------- Sprint: devex #118 July 2016 > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.1.AM3 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22816: ---------------------------------- Assignee: Andre Dietisheim > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.1.AM3 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22816: ------------------------------- Story Points: 8 > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.1.AM3 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22663) Use new Style for FilteredTree

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22663?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-22663 at 7/26/16 9:36 AM: ---------------------------------------------------------------- [~aurelien.pupier], sorry - you're right there are potentially more places where a search field is present. I tried the most obvious one to me (since this JIRA has the JMX component set) - the jmx navigator view: !jmx.png! And I can see exactly the same (old) behavior in the New Server wizard. was (Author: mmalina): [~aurelien.pupier], sorry - you're right there are potentially more places where a search field is present. I tried the most obvious one to me (since this JIRA has the JMX component set) - the jmx navigator view: !jmx.png! > Use new Style for FilteredTree > ------------------------------ > > Key: JBIDE-22663 > URL: https://issues.jboss.org/browse/JBIDE-22663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: jmx.png > > > - it will avoid to have "type search text" entered as a real text and provide a nicer UI > it avoids to have the "type search text" used as a filter when clicking in the text field > for UI difference kind see screenshots on https://bugs.eclipse.org/bugs/show_bug.cgi?id=496805 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22663) Use new Style for FilteredTree

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22663?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22663: -------------------------------- Comment: was deleted (was: I also didn't see a real change in behavior but I couldn't figure out what was supposed to change? The MbeanOpenSelectionDialog is in the JMX Navigator view. ) > Use new Style for FilteredTree > ------------------------------ > > Key: JBIDE-22663 > URL: https://issues.jboss.org/browse/JBIDE-22663 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.1.AM3 > > Attachments: jmx.png > > > - it will avoid to have "type search text" entered as a real text and provide a nicer UI > it avoids to have the "type search text" used as a filter when clicking in the text field > for UI difference kind see screenshots on https://bugs.eclipse.org/bugs/show_bug.cgi?id=496805 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2016