[JBoss JIRA] (JBIDE-17455) JBT are not starting when property -Dorg.jboss.tools.vpe.loadxulrunner is set to false
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17455?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17455.
--------------------------------------------
Resolution: Done
> JBT are not starting when property -Dorg.jboss.tools.vpe.loadxulrunner is set to false
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-17455
> URL: https://issues.jboss.org/browse/JBIDE-17455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104 Linux 64 bit Java Oracle 1.7.0_51
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> 1. Start JBT with -vmargs -Dorg.jboss.tools.vpe.loadxulrunner=false parameters
> 2. Import HTML5 project from JBoss Central
> 3. Open index.html page
> ERROR: Opened editor has empty title and visual part is also empty
> 4. Close JBT with with opened index.html page
> 5. Start JBT
> ERROR: JBT did not start
> There is couple of exceptions in log. This is last one:
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2014-05-27 18:10:56.925
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:608)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:600)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:885)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:437)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.custom.SashFormLayout.layout(SashFormLayout.java:190)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:1004)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:962)
> at org.jboss.tools.vpe.editor.xpl.CustomSashForm.layout(CustomSashForm.java:261)
> at org.jboss.tools.vpe.editor.xpl.CustomSashForm$1.handleEvent(CustomSashForm.java:159)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4462)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:693)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:693)
> at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.CTabFolderLayout.layout(CTabFolderLayout.java:116)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:204)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:879)
> at org.eclipse.swt.layout.FillLayout.layout(FillLayout.java:219)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1438)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.CTabFolderLayout.layout(CTabFolderLayout.java:116)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1652)
> at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1658)
> at org.eclipse.swt.widgets.Composite.layout(Composite.java:1004)
> at org.eclipse.swt.custom.CTabFolder.runUpdate(CTabFolder.java:3755)
> at org.eclipse.swt.custom.CTabFolder$10.run(CTabFolder.java:3741)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-17696 at 7/1/14 2:55 PM:
---------------------------------------------------------------
It looks like ether GraphUpdateJob issue or JobManager.yieldRule issue for further debugging would be good to see job yielding tracing output, to enable that you need:
# .option file (see attachment)
# run eclipse with '-consoleLog -debug /path/to/the/.option'
Try to replicate the error again and attach console output to this issue.
Thanks.
was (Author: dgolovin):
It looks like ether GraphUpdateJob issue of JobManager.yieldRule issue for further debugging would be good to see job yielding tracing output, to enable that you need:
# .option file (see attachment)
# run eclipse with '-consoleLog -debug /path/to/the/.option'
Try to replicate the error again and attach console output to this issue.
Thanks.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17696:
---------------------------------------
There should be output that looks like one below:
{code}[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) will yieldRule to JPA Project Change Event Handler(1815)
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) will yieldRule to JPA Project Change Event Handler(1815)
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) is waiting for JPA Project Change Event Handler(1815) to transition from WAITING state
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) waiting to resume
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) resumed{code}
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17696:
----------------------------------
Attachment: .options
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17696:
---------------------------------------
It looks like ether GraphUpdateJob issue of JobManager.yieldRule issue for further debugging would be good to see job yielding tracing output, to enable that you need:
# .option file (see attachment)
# run eclipse with '-consoleLog -debug /path/to/the/.option'
Try to replicate the error again and attach console output to this issue.
Thanks.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17737:
--------------------------------------
Assignee: Snjezana Peco
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta3
>
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17737:
-----------------------------------
Component/s: runtime-detection
(was: seam2)
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Snjezana Peco
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17737:
-----------------------------------
Fix Version/s: 4.2.0.Beta3
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta3
>
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months