Automated Error Reporting Bot created JBIDE-23289: ----------------------------------------------------- Summary: ServerProfileModel.getController fails to find publish controller for wf10 [aeri] Key: JBIDE-23289 URL: https://issues.jboss.org/browse/JBIDE-23289 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Automated Error Reporting Bot I hesitated to make a bug report here. On the one hand, this is simply a log message, and the environment still has a chance to recover. However, it does seem extremely strange that the publish subsystem is not being found for wf10. Our unit tests indicate it is found. The fact that this is still being replicated in astools 3.2.x is puzzling to me. But I simply cannot imagine what environment is causing this. Subsystem and profile mappings are done in the same plugin the subsystems are declared for the most part. The following problem was reported via the automated error reporting: Message: No subsystem found for servertype org.jboss.ide.eclipse.as.wildfly.100 and system type publish {noformat} com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted. at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ServerProfileModel.getController(ServerProfileModel.java:187) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ProfileServerBehavior.getController(ProfileServerBehavior.java:59) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.getPublishController(CachedPublisherProfileBehavior.java:35) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.canPublish(ControllableServerBehavior.java:297) at org.eclipse.wst.server.core.internal.Server.canPublish(Server.java:1218) at org.eclipse.wst.server.core.internal.Server.shouldPublish(Server.java:1231) at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.getServerStatusLabel(ServerDecorator.java:139) at org.eclipse.wst.server.ui.internal.cnf.ServerDecorator.decorate(ServerDecorator.java:73) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:273) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:83) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:367) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:349) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:372) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:332) 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.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 | | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 | | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160603-0902 | | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 | | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 | | 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.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.2.1.v20160711-1757 | Operating Systems: | Linux | 3.10.0.28 | 4.6.7.fc24 | | MacOSX | 10.10.5 | 10.12.0 | | Windows | 5.1.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56f024b6e4b08ccb7b...] 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)