[jbosstools-issues] [JBoss JIRA] (JBIDE-23288) Users somehow have server configured for as6 shutdown behavior (jmx) and as7+ deployment scanner behavior (mgmt)

Rob Stryker (JIRA) issues at jboss.org
Mon Nov 14 09:21:00 EST 2016


     [ https://issues.jboss.org/browse/JBIDE-23288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker updated JBIDE-23288:
--------------------------------
    Fix Version/s: LATER


> Users somehow have server configured for as6 shutdown behavior (jmx) and as7+ deployment scanner behavior (mgmt)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23288
>                 URL: https://issues.jboss.org/browse/JBIDE-23288
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>            Reporter: Automated Error Reporting Bot
>             Fix For: LATER
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: HIDDEN
>     at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
>     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: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)
> {noformat}
> Bundles:
> | org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.100.v20160418-1621 |
> | 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.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 |
> | org.eclipse.jst.j2ee | 1.1.850.v201506041749 | 1.1.850.v201506041749 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.eclipse.ui.forms | 3.6.200.v20150506-2029 | 3.6.200.v20150506-2029 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.common.frameworks | 1.2.200.v201304241450 | 1.2.200.v201304241450 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 |
> | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 |
> | org.jboss.ide.eclipse.as.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.ide.eclipse.as.management.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.ide.eclipse.as.management.wildfly9 | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.ide.eclipse.as.ui | 3.1.0.Beta2-v20150723-0026-B29 | 3.1.1.Final-v20160409-0826-B118 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.tools.jmx.ui | 1.7.1.Final-v20160409-0826-B118 | 1.8.0.Final-v20160614-2020-B9 |
> Operating Systems:
> | Linux | 2.6.32.3 | 4.7.4.fc24 |
> | MacOSX | 10.11.4 | 10.11.6 |
> | 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/570ce1e8e4b07391bf068194] for the latest data.
> Thank you for your assistance.
>  Your friendly error-reports-inbox.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list