[
https://issues.jboss.org/browse/JBIDE-22008?page=com.atlassian.jira.plugi...
]
Rob Stryker edited comment on JBIDE-22008 at 8/8/16 2:22 PM:
-------------------------------------------------------------
So this is a result of some tests I ran. The goal is to find a jar set (horizontal) that
works with all the listed runnign app servers (column 1).
Nothing seems to work for both EAP and WF in this usecase with an offset declared. Also,
looking at EAP alone, while some jar sets will work most, there is no jarset that will
work for all of the listed EAPs.
Specifically, no jar set is found that works with EAP 6.2.4 and an offset declared.
This doesn't even include regression testing to make sure it won't break a
previous issue with the jars.
{code}
EAP Version Jar Set astools 7x astools_wf9 eap61 eap64 Wf9.0.2 wf10
Eap 6.1.2 Success fast fail success success fast fail fast fail
EAP 6.2.4 success fast fail success success fast fail fast fail
Eap 6.3 success fast fail success success fast fail fast fail
Eap 6.4 success fast fail success success fast fail fast fail
Wf 9.0.2 timeout fail success timeout fail timeout fail success success
Wf 10.0.0 timeout fail success timeout fail timeout fail success success
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
Edit: Updated the wf appservers. Seems my test case was using wrong port.
was (Author: rob.stryker):
So this is a result of some tests I ran. The goal is to find a jar set (horizontal) that
works with all the listed runnign app servers (column 1).
Nothing seems to work for both EAP and WF in this usecase with an offset declared. Also,
looking at EAP alone, while some jar sets will work most, there is no jarset that will
work for all of the listed EAPs.
Specifically, no jar set is found that works with EAP 6.2.4 and an offset declared.
This doesn't even include regression testing to make sure it won't break a
previous issue with the jars.
{code}
EAP Version Jar Set astools 7x astools_wf9 eap61 eap64 Wf9.0.2 wf10
Eap 6.1.2 Success fast fail success success fast fail fast fail
EAP 6.2.4 success fast fail success success fast fail fast fail
Eap 6.3 success fast fail success success fast fail fast fail
Eap 6.4 success fast fail success success fast fail fast fail
Wf 9.0.2 timeout fail success timeout fail timeout fail success success
Wf 10.0.0 timeout fail success timeout fail timeout fail success success
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
Edit: Updated the wf appservers. Seems my test case was using wrong port.
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.1.AM3
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)