[JBoss JIRA] (JBIDE-22723) NullPointerException in ArquillianUtility.getModel
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22723?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22723:
-------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.1.Final)
> NullPointerException in ArquillianUtility.getModel
> --------------------------------------------------
>
> Key: JBIDE-22723
> URL: https://issues.jboss.org/browse/JBIDE-22723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.1.AM3
>
>
> The following problem was reported via the automated error reporting:
> Message: Internal Error
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.arquillian.core.internal.util.ArquillianUtility.getModel(ArquillianUtility.java:398)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianUtility.addManagedDependencies(ArquillianUtility.java:245)
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring$AddDependencyManagement.process(AddArquillianSupportRefactoring.java:384)
> at org.eclipse.m2e.core.ui.internal.editing.PomEdits$CompoundOperation.process(PomEdits.java:668)
> at org.eclipse.m2e.core.ui.internal.editing.PomEdits.performOnDOMDocument(PomEdits.java:510)
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:225)
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:210)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:122)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:207)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:86)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.ltk.core.refactoring | 3.7.0.v20160419-0705 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.8.0.v20160518-1817 | 3.8.0.v20160518-1817 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.jboss.tools.arquillian.core | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 |
> | org.jboss.tools.arquillian.ui | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5783951be4b07f3dc2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22724) ResourceException below ArquillianBuilder.hasErrors (thrown in Marker.checkInfo)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22724?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22724:
-------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM3)
> ResourceException below ArquillianBuilder.hasErrors (thrown in Marker.checkInfo)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22724
> URL: https://issues.jboss.org/browse/JBIDE-22724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: Marker id 139166 not found.
> {noformat}
> org.eclipse.core.internal.resources.ResourceException: Marker id 139166 not found.
> at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57)
> at org.eclipse.core.internal.resources.Marker.getAttribute(Marker.java:102)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.hasErrors(ArquillianBuilder.java:477)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:98)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | MacOSX | 10.11.1 | 10.11.1 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5744cd67e4b0138d62...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22723) NullPointerException in ArquillianUtility.getModel
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22723?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22723:
-------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM2)
> NullPointerException in ArquillianUtility.getModel
> --------------------------------------------------
>
> Key: JBIDE-22723
> URL: https://issues.jboss.org/browse/JBIDE-22723
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: Internal Error
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.arquillian.core.internal.util.ArquillianUtility.getModel(ArquillianUtility.java:398)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianUtility.addManagedDependencies(ArquillianUtility.java:245)
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring$AddDependencyManagement.process(AddArquillianSupportRefactoring.java:384)
> at org.eclipse.m2e.core.ui.internal.editing.PomEdits$CompoundOperation.process(PomEdits.java:668)
> at org.eclipse.m2e.core.ui.internal.editing.PomEdits.performOnDOMDocument(PomEdits.java:510)
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:225)
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:210)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:122)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:207)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:86)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.0.v20160503-1608 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.ltk.core.refactoring | 3.7.0.v20160419-0705 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.8.0.v20160518-1817 | 3.8.0.v20160518-1817 |
> | org.eclipse.m2e.core.ui | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.jboss.tools.arquillian.core | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 |
> | org.jboss.tools.arquillian.ui | 1.2.100.Final-v20160610-0313-B2 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5783951be4b07f3dc2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22722) ArrayStoreException below NewArquillianJUnitTestCaseDeploymentPage.refreshViewer (thrown in ArrayList.toArray)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22722?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22722:
-------------------------------
Fix Version/s: 4.4.1.Final
(was: 4.4.1.AM2)
> ArrayStoreException below NewArquillianJUnitTestCaseDeploymentPage.refreshViewer (thrown in ArrayList.toArray)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22722
> URL: https://issues.jboss.org/browse/JBIDE-22722
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> {noformat}
> java.lang.ArrayStoreException: null
> at java.util.ArrayList.toArray(null:-1)
> at org.jboss.tools.arquillian.ui.internal.wizards.NewArquillianJUnitTestCaseDeploymentPage.refreshViewer(NewArquillianJUnitTestCaseDeploymentPage.java:905)
> at org.jboss.tools.arquillian.ui.internal.wizards.NewArquillianJUnitTestCaseDeploymentPage.access$9(NewArquillianJUnitTestCaseDeploymentPage.java:901)
> at org.jboss.tools.arquillian.ui.internal.wizards.NewArquillianJUnitTestCaseDeploymentPage$10.widgetSelected(NewArquillianJUnitTestCaseDeploymentPage.java:625)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5755d22ee4b06056d2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22724) ResourceException below ArquillianBuilder.hasErrors (thrown in Marker.checkInfo)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22724?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22724:
-------------------------------
Fix Version/s: 4.4.1.AM3
(was: 4.4.1.AM2)
> ResourceException below ArquillianBuilder.hasErrors (thrown in Marker.checkInfo)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22724
> URL: https://issues.jboss.org/browse/JBIDE-22724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Snjezana Peco
> Fix For: 4.4.1.AM3
>
>
> The following problem was reported via the automated error reporting:
> Message: Marker id 139166 not found.
> {noformat}
> org.eclipse.core.internal.resources.ResourceException: Marker id 139166 not found.
> at org.eclipse.core.internal.resources.Marker.checkInfo(Marker.java:57)
> at org.eclipse.core.internal.resources.Marker.getAttribute(Marker.java:102)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.hasErrors(ArquillianBuilder.java:477)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:98)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.jboss.tools.arquillian.core | 1.2.1.Final-v20160331-0142-B69 | 1.2.100.Final-v20160610-0313-B2 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | MacOSX | 10.11.1 | 10.11.1 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5744cd67e4b0138d62...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[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 edited comment on JBIDE-22008 at 7/29/16 2:16 AM:
--------------------------------------------------------------
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 timeout fail fast fail timeout fail fast fail 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 fast fail timeout fail fast fail fast fail fast fail
Wf 10.0.0 timeout fail fast fail timeout fail fast fail fast fail fast fail
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
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 timeout fail fast fail timeout fail fast fail 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 fast fail timeout fail fast fail fast fail fast fail
Wf 10.0.0 timeout fail fast fail timeout fail fast fail fast fail fast fail
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
> 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)
9 years, 8 months
[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 edited comment on JBIDE-22008 at 7/29/16 2:14 AM:
--------------------------------------------------------------
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 timeout fail fast fail timeout fail fast fail 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 fast fail timeout fail fast fail fast fail fast fail
Wf 10.0.0 timeout fail fast fail timeout fail fast fail fast fail fast fail
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
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 timeout fail fast fail timeout fail fast fail 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 fast fail timeout fail fast fail fast fail fast fail
Wf 10.0.0 timeout fail fast fail timeout fail fast fail fast fail fast fail
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
> 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)
9 years, 8 months
[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 edited comment on JBIDE-22008 at 7/29/16 2:13 AM:
--------------------------------------------------------------
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 timeout fail fast fail timeout fail fast fail 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 fast fail timeout fail fast fail fast fail fast fail
Wf 10.0.0 timeout fail fast fail timeout fail fast fail fast fail fast fail
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
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 timeout fail fast fail timeout fail fast fail 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 fast fail timeout fail fast fail fast fail fast fail
Wf 10.0.0 timeout fail fast fail timeout fail fast fail fast fail fast fail
{code}
Basically, all management commands fail currently when an offset is declared for EAP 6.1+.
> 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)
9 years, 8 months