[jbosstools-issues] [JBoss JIRA] (JBIDE-14540) forge is started even though I have not used it
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Mon May 20 15:28:06 EDT 2013
Max Rydahl Andersen created JBIDE-14540:
-------------------------------------------
Summary: forge is started even though I have not used it
Key: JBIDE-14540
URL: https://issues.jboss.org/browse/JBIDE-14540
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.1.0.Beta1
Reporter: Max Rydahl Andersen
Priority: Critical
looks like forge 2 startsup instantly and not only takes up memory but also starts multiple threads even though I have not used forge at all.
That is very nasty behavior for a plugin.
Not sure what it is/was doing but this is 5-10 minutes after startup and it is still in some timed/queuing .
"Reference Reaper" daemon prio=5 tid=0x000000011204f800 nid=0xa00b in Object.wait() [0x000
0000111100000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007dca8cab8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
- locked <0x00000007dca8cab8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at org.jboss.modules.ref.References$ReaperThread.run(References.java:68)
"Forge Container org.jboss.forge.container.ForgeImpl at 57f8b993" prio=5 tid=0x0000000110f25000 nid=0xa107 waiting on condition [0x0000000111800000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.jboss.forge.container.ForgeImpl.start(ForgeImpl.java:151)
at org.jboss.forge.container.ForgeImpl$1.run(ForgeImpl.java:92)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list