[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23602:
-------------------------------------
Labels: openshift_v3 server_adapter (was: )
> Server adapter: Hot code replace failed dialog has poor usability
> -----------------------------------------------------------------
>
> Key: JBIDE-23602
> URL: https://issues.jboss.org/browse/JBIDE-23602
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.AM2
>
> Attachments: hot-code-replace-failed-2.png
>
>
> steps to reproduce:
> # ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it
> # EXEC: open HelloService and change it to the following:
> {code:title=HelloService}
> public class HelloService {
> private static final String MAGIC_STRING = "42";
>
> String createHelloMessage(String name) {
> return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!";
> }
> }
> {code}
> and save the editor
> Result:
> "Hot code replace failed" dialog pops up, which is expected.
> !hot-code-replace-failed-2.png!
> But it's usability is poor:
> * the affected module is not fully shown (half of it cut off)
> * there's no margin on the right border of the dialog
> * No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22902) NullPointerException in CDICoreBuilder$IncrementCheck.<init>
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22902?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22902:
------------------------------------
bump up to parent pom version = 4.4.3.AM3-SNAPSHOT
> NullPointerException in CDICoreBuilder$IncrementCheck.<init>
> ------------------------------------------------------------
>
> Key: JBIDE-22902
> URL: https://issues.jboss.org/browse/JBIDE-22902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.core.CDICoreBuilder$IncrementCheck.<init>(CDICoreBuilder.java:588)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:190)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> 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.10.1.v20150725-1910 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.0.v20150303-1130 | 3.10.0.v20150303-1130 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> Operating Systems:
> | Linux | 4.1.15 | 4.5.7.fc23 |
> | MacOSX | 10.11.4 | 10.11.5 |
> | 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/571e1421e4b08bd809...] 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-22901) NullPointerException in CDIProject.rebuildXML
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22901?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22901:
------------------------------------
bump up to parent pom version = 4.4.3.AM3-SNAPSHOT
> NullPointerException in CDIProject.rebuildXML
> ---------------------------------------------
>
> Key: JBIDE-22901
> URL: https://issues.jboss.org/browse/JBIDE-22901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.AM3
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildXML(CDIProject.java:1458)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1214)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:272)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> 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.v20160422-0304 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160504-0322 |
> | org.eclipse.m2e.core.ui | 1.6.3.20160209-1446 | 1.7.0.20160504-0322 |
> | org.eclipse.ui.ide | 3.11.0.v20150825-2158 | 3.11.0.v20150825-2158 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> Operating Systems:
> | Linux | 3.19.0 | 3.19.0 |
> | 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/56ec34a1e4b08ccb7b...] 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-22902) NullPointerException in CDICoreBuilder$IncrementCheck.<init>
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22902?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22902:
------------------------------------
bump up to parent pom version = 4.4.3.AM3-SNAPSHOT
> NullPointerException in CDICoreBuilder$IncrementCheck.<init>
> ------------------------------------------------------------
>
> Key: JBIDE-22902
> URL: https://issues.jboss.org/browse/JBIDE-22902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.core.CDICoreBuilder$IncrementCheck.<init>(CDICoreBuilder.java:588)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:190)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> 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.10.1.v20150725-1910 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.debug.core | 3.10.0.v20150303-1130 | 3.10.0.v20150303-1130 |
> | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> Operating Systems:
> | Linux | 4.1.15 | 4.5.7.fc23 |
> | MacOSX | 10.11.4 | 10.11.5 |
> | 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/571e1421e4b08bd809...] 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-22901) NullPointerException in CDIProject.rebuildXML
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22901?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22901:
------------------------------------
bump up to parent pom version = 4.4.3.AM3-SNAPSHOT
> NullPointerException in CDIProject.rebuildXML
> ---------------------------------------------
>
> Key: JBIDE-22901
> URL: https://issues.jboss.org/browse/JBIDE-22901
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.AM3
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildXML(CDIProject.java:1458)
> at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1214)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:442)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:272)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> 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.v20160422-0304 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160504-0322 |
> | org.eclipse.m2e.core.ui | 1.6.3.20160209-1446 | 1.7.0.20160504-0322 |
> | org.eclipse.ui.ide | 3.11.0.v20150825-2158 | 3.11.0.v20150825-2158 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 |
> Operating Systems:
> | Linux | 3.19.0 | 3.19.0 |
> | 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/56ec34a1e4b08ccb7b...] 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse
by Jon Kranes (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23757?page=com.atlassian.jira.plugi... ]
Jon Kranes updated JBIDE-23757:
-------------------------------
Issue Type: Bug (was: Feature Request)
> Thread deadlock when starting Eclipse
> -------------------------------------
>
> Key: JBIDE-23757
> URL: https://issues.jboss.org/browse/JBIDE-23757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.4.2.Final
> Environment: MacOS Sierra, JDK 1.8.0_112
> Reporter: Jon Kranes
>
> Steps to reproduce:
> * Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result)
> * Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final
> * Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results)
> * Add Wildfly 10.x server to Eclipse
> * Create a default Maven Web App project
> * Add the web app project to the Wildfly server
> * Exit Eclipse and restart
> Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit.
> Thread dump output from jvisualvm shows a thread deadlock:
> Found one Java-level deadlock:
> =============================
> "Thread-8":
> waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server),
> which is held by "Worker-0"
> "Worker-0":
> waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager),
> which is held by "Thread-8"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-8":
> at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034)
> - waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152)
> - locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68)
> "Worker-0":
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109)
> - waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)
> at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)
> - locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634)
> at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058)
> at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039)
> at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Found 1 deadlock.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse
by Jon Kranes (JIRA)
Jon Kranes created JBIDE-23757:
----------------------------------
Summary: Thread deadlock when starting Eclipse
Key: JBIDE-23757
URL: https://issues.jboss.org/browse/JBIDE-23757
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 4.4.2.Final
Environment: MacOS Sierra, JDK 1.8.0_112
Reporter: Jon Kranes
Steps to reproduce:
* Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result)
* Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final
* Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results)
* Add Wildfly 10.x server to Eclipse
* Create a default Maven Web App project
* Add the web app project to the Wildfly server
* Exit Eclipse and restart
Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit.
Thread dump output from jvisualvm shows a thread deadlock:
Found one Java-level deadlock:
=============================
"Thread-8":
waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server),
which is held by "Worker-0"
"Worker-0":
waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager),
which is held by "Thread-8"
Java stack information for the threads listed above:
===================================================
"Thread-8":
at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034)
- waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697)
at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152)
- locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81)
at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73)
at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68)
"Worker-0":
at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109)
- waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
at org.eclipse.osgi.container.Module.doStart(Module.java:581)
at org.eclipse.osgi.container.Module.start(Module.java:449)
at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)
at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)
- locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634)
at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058)
at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039)
at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542)
at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Found 1 deadlock.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23705) no content assist in freemarker templates for interface-based beans
by Ronald Müller (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23705?page=com.atlassian.jira.plugi... ]
Ronald Müller commented on JBIDE-23705:
---------------------------------------
Thank you for reviewing. My pull request was thought as proposal, not as final implementation. Its running on my maschine now and works so far (at least for me ;-) ). I'm sorry that didn't provide any tests for that, but i'm not familiar with plugin development and have not enough spare time for a deep dive.
Anyway the mentioned class/method should definitly be reviewed. There are serious bugs in there. The reflection part will not run in any case. See line 181 of jbosstools-freemarker/plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/model/interpolation/NameFragment.java The condition there will never hold true.
regards ronald
> no content assist in freemarker templates for interface-based beans
> -------------------------------------------------------------------
>
> Key: JBIDE-23705
> URL: https://issues.jboss.org/browse/JBIDE-23705
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Reporter: Ronald Müller
>
> If your beans in freemarker templates are described by an interface, the code completion (content assist) will not work.
> There two mechanism implemented to provide content suggestion:
> # Bean-Introspection: this doesn't work for interfaces
> # Java Reflections: there are bugs which prevent any suggestions
> My suggestion: use only reflections - it will work for both and isn't that harder to implement.
> I'm working on a pull request for fixing this issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months