[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17656:
---------------------------------------------
what is the need for forge to monitor the resources ? if no known reasons at least for now skipping it seems simplest (at least when within eclipse) ?
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-17656:
-----------------------------------------
Ok, so we can find a way to abstract this if that works.
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17656:
-----------------------------------------
Yes, Eclipse would also create it's own WatchService instances, that operate in a different thread.
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-17656:
-----------------------------------------
Wonder why this does not happen in the standalone version? Is this something related to Eclipse itself?
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-17656) Forge crashed Eclipse
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17656?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17656:
-----------------------------------------
Dsiabling the {{FileMonitor}} ({{org.jboss.forge.addon.resource.monitor.FileMonitor}}) in the resources addon seems to eliminate the crashes.
[~lincolnthree], [~gastaldi], would you know if this can be disabled in Eclipse? I don't seem to find any notes on how and why this class is used by Forge, and whether it's use could be limited to non-IDE usecases. It does listen for changes in the file system to build some project cache, but why and for what?
> Forge crashed Eclipse
> ---------------------
>
> Key: JBIDE-17656
> URL: https://issues.jboss.org/browse/JBIDE-17656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Environment: Windows 7 64bits, JDK 8.0.0, JBDS 8.0.0.Beta2
> Reporter: Fred Bricon
> Assignee: Vineet Reynolds
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: generate.fsh, hs_err_pid4536.log, hs_err_pid5320.log, hs_err_pid640.log, JVM-GCactivity-heap.png, JVM-GCactivity-Linux.png, JVM-GCactivity.png
>
>
> I tried to reproduce the steps from JBIDE-17655 a 2nd time, Eclipse crashed while forge was scaffolding
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-18179) Forge Console is limited to 80 chars and throws exception if line surpasses the limit
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18179?page=com.atlassian.jira.plugi... ]
Vineet Reynolds edited comment on JBIDE-18179 at 8/30/14 6:16 AM:
------------------------------------------------------------------
The terminal size is set to the default of 24 x 80 during initialization of the shell; we don't send in any terminal properties when creating a new instance of the POSIXTerminal for use in the Forge Console, and thus the defaults are used.
If I'm not mistaken, we need to enhance the {{start()}} method in {{org.jboss.tools.forge.ui.internal.cli.AeshConsole}} to pass in the length of the TextViewer widget, and also resize the terminal width on resizing the TextViewer.
was (Author: vineet.reynolds):
The terminal size is set to the default of 24 x 80 during initialization of the shell; we don't send in any terminal properties when creating a new instance of the POSIXTerminal for use in the Forge Console.
If I'm not mistaken, we need to enhance the {{start()}} method in {{org.jboss.tools.forge.ui.internal.cli.AeshConsole}} to pass in the length of the TextViewer widget, and also resize the terminal width on resizing the TextViewer.
> Forge Console is limited to 80 chars and throws exception if line surpasses the limit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18179
> URL: https://issues.jboss.org/browse/JBIDE-18179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-18179) Forge Console is limited to 80 chars and throws exception if line surpasses the limit
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18179?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-18179:
-----------------------------------------
The terminal size is set to the default of 24 x 80 during initialization of the shell; we don't send in any terminal properties when creating a new instance of the POSIXTerminal for use in the Forge Console.
If I'm not mistaken, we need to enhance the {{start()}} method in {{org.jboss.tools.forge.ui.internal.cli.AeshConsole}} to pass in the length of the TextViewer widget, and also resize the terminal width on resizing the TextViewer.
> Forge Console is limited to 80 chars and throws exception if line surpasses the limit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18179
> URL: https://issues.jboss.org/browse/JBIDE-18179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month
[JBoss JIRA] (JBIDE-18181) Errors when hibernate.cfg.xml not at classpath root
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18181?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18181:
---------------------------------------------
looks like the handling of specific hibernate.cfg.xml got broken. thats a blocker.
> Errors when hibernate.cfg.xml not at classpath root
> ---------------------------------------------------
>
> Key: JBIDE-18181
> URL: https://issues.jboss.org/browse/JBIDE-18181
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: Ubuntu Trusty, Eclipse Luna, OpenJDK 7, Hibernate Tools 3.8.0.CR1-v20140826-1536-B599, Hibernate 4.1.12
> Reporter: Luke Maurer
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> If a project keeps its hibernate.cfg.xml anywhere besides the root of the classpath, Hibernate Tools will not recognize it. In the Hibernate Configurations tree, expanding either Session Factory or Database gives an error ending in “/hibernate.cfg.xml not found”. (The Configuration subtree appears to work.)
> As a workaround, if I go into the directory holding WEB-INF/classes (i.e. where compiled Java bytecode goes) and symlink hibernate.cfg.xml there, it seems to work.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 1 month