[JBoss JIRA] (JBIDE-14356) GC overhead limit exceeded when adding fileset to LiveReload Server
by Stian Thorgersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14356?page=com.atlassian.jira.plugi... ]
Stian Thorgersen commented on JBIDE-14356:
------------------------------------------
That makes sense, I assumed that was a way to specify what resources in the workspace would trigger a reload. Does such an option make sense? I assume currently modifying any file triggers a reload in all browser tabs connected to the LiveReload server?
There's also the Add/Remove option, which just says "There are no resources that can be added or removed from the server".
> GC overhead limit exceeded when adding fileset to LiveReload Server
> -------------------------------------------------------------------
>
> Key: JBIDE-14356
> URL: https://issues.jboss.org/browse/JBIDE-14356
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Reporter: Stian Thorgersen
> Assignee: Rob Stryker
>
> When creating a LiveReload Server and adding a fileset Eclipse hangs consuming a lot of CPU. Eventually the error message "Unhandled event loop exception / GC overhead limit exceeded" is displayed.
> From the stack trace while this is going the only interesting thread is:
> {code}
> "main" prio=10 tid=0x00007ff9a0009800 nid=0x22c2 runnable [0x00007ff9a81fe000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8654)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1243)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2283)
> at org.eclipse.swt.widgets.Shell.setVisible(Shell.java:2153)
> at org.eclipse.swt.widgets.Shell.open(Shell.java:1546)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.statushandlers.InternalDialog.open(InternalDialog.java:327)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:270)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197)
> at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57)
> at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:106)
> at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:242)
> at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopException(WorkbenchAdvisor.java:326)
> at org.eclipse.ui.internal.ExceptionHandler.handleException(ExceptionHandler.java:65)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:830)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.ide.eclipse.archives.webtools.filesets.FilesetActionProvider$1.run(FilesetActionProvider.java:202)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> I'm running:
> * Eclipse Kepler M6 with JBoss Tools 4.1 Alpha 2
> * OpenJDK 1.7.0_21
> * Ubuntu 13.04
> To reproduce create a new LiveReload server. Expand it, right click on 'Filesets' and select 'Create New File Filter'. Then write '/' in 'Root Directory'. Observe that Eclipse now consumes ~100% cpu on all available cores. Wait for a few minutes and the error message mentioned earlier should be displayed
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-14342 at 5/2/13 4:34 AM:
------------------------------------------------------------------
IMHO we need 2 changes here:
1) need to report accurately that we timeouted when creating the jenkins (<timeout> vs <no reponse>)
2) we need to increase client timeouts: either defaults in the client, provide means for users to increase client timeouts (custom client-specific system properties) or method overloads that allow specific timeouts for specific operations
was (Author: adietish):
IMHO we need 2 changes here:
1) need to report accurately that we timeouted when creating the jenkins (<timeout> vs <no reponse>)
2) we need to increase client timeouts: either defaults in the client or provide means for the client to increase its timeouts (custom system properties)
> I dont get credentials reported when I create a jenkins
> -------------------------------------------------------
>
> Key: JBIDE-14342
> URL: https://issues.jboss.org/browse/JBIDE-14342
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
> Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png
>
>
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14125) Should 'Search' button be changed to 'Browse' for consistency?
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14125?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-14125.
-------------------------------
Resolution: Done
> Should 'Search' button be changed to 'Browse' for consistency?
> --------------------------------------------------------------
>
> Key: JBIDE-14125
> URL: https://issues.jboss.org/browse/JBIDE-14125
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta1
>
> Attachments: BrowserSim_BrowseButton.png, Forge_SearchButton.png, OpenShift_BrowseButton.png
>
>
> Windows > Preferences > Forge > Installed Forge Runtimes. Click 'Add'. The button following the 'Location' field is labelled 'Search'.
> In the other windows I have encountered in JBDS that have a 'Location' field, the neighbouring button has been labelled 'Browse'. See attached screen captures as examples.
> This is not a big issue. But should 'Search' be changed to 'Browse' for consistency?
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14350) Search field disappears when Central editor is too small
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14350?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-14350:
-------------------------------
Attachment: searchField1.png
I agree that new row would be ugly.
But wouldn't be possible to set some minimal width to header? So it would look something like this:
!searchField1.png!
> Search field disappears when Central editor is too small
> --------------------------------------------------------
>
> Key: JBIDE-14350
> URL: https://issues.jboss.org/browse/JBIDE-14350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha2
> Reporter: Radim Hopp
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
> Attachments: searchField.png, searchField1.png
>
>
> Search field disappears, when Central editor is shrinked to certain width.
> Would it be possible either move the search field under buttons and "show on startup" checkbox or define some minimal width.
> Thanks
> !searchField.png!
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14342) I dont get credentials reported when I create a jenkins
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14342:
------------------------------------------
IMHO we need 2 changes here:
1) need to report accurately that we timeouted when creating the jenkins (<timeout> vs <no reponse>)
2) we need to increase client timeouts: either defaults in the client or provide means for the client to increase its timeouts (custom system properties)
> I dont get credentials reported when I create a jenkins
> -------------------------------------------------------
>
> Key: JBIDE-14342
> URL: https://issues.jboss.org/browse/JBIDE-14342
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
> Attachments: correct-creation-log.png, no-information-from-openshift.png, null-creation-log.png
>
>
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2623:
-------------------------------------------
shouldn't the 3 "aggregation" be more like:
for JBT: stage aggregate on dl.jb.org which then gets put into relevant release part of dl.jb.org
for JBDS: stage aggregate on www.qa which then gets put into relevant release part of ds.jb.com
i.e shouldn't need "three" should it or am I missing something ?
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite, Upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2626) Use TP for central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2626?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen closed JBDS-2626.
-------------------------------------
Resolution: Duplicate Issue
JBDS-2623 was created yesterday that makes this a duplicate
> Use TP for central
> ------------------
>
> Key: JBDS-2626
> URL: https://issues.jboss.org/browse/JBDS-2626
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Max Rydahl Andersen
>
> As discovered in JBDS-2486 the current mechanism for mirroring and setup of central is spread across build.xml's and no reliable way to reproduce nor validate a site.
> Suggestion is to do "dumb" mirrors which is then used together with a TP with specific IU's + versions.
--
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
12 years, 11 months