[
https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19376:
-------------------------------------
I don't think we should move it into ServerCorePlugin. I think the constructor for
UnifiedServerListenerManager should launch a thread to initialize itself.
ServerCorePlugin.start() needs to return quickly and not be doing so much stuff in
wst.server.core, because it's probably triggering even more loading and potentially
even loops once extension points are brought in.
So I think we need ServerCorePlugin.start to complete as quick as possible and do as
little as possible. But the other danger is that if others add listeners to
UnifiedServerListenerManager that get missed, ie, UnifiedServerListenerManager has
already started adding listeners to wst.server.core, and someone adds a new listener to
UnifiedServerListenerManager which doesn't get added to wst.server.core.
I'll look into it more tomorrow.
Eclipse freezes at or shortly after startup
-------------------------------------------
Key: JBIDE-19376
URL:
https://issues.jboss.org/browse/JBIDE-19376
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.2.Final
Environment: Eclipse Luna EE.
Reporter: Anton Meller
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.3.CR1, 4.3.0.Alpha2
Attachments: 20150224_threaddump-1424762289905.tdump,
20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump,
20150226_threaddump-1424936318015.tdump
Sometimes (probably once or twice a month) my eclipse freezes either right at startup or
short after startup if I try to save some modified file. In Java VisualVM I can see than a
deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method.
Today I have updated JBoss plugins to latest version (from the update site for JBoss
Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup
. It looks like it occurs on larger workspaces (my current workspace has about 70 open
projects (most of them are java projects and depends on each other)) and if servers view
is open/visible right at startup. In a smaller workspace with only 11 projects I had no
luck reproducing the deadlock.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)