[JBoss JIRA] (JBIDE-21221) Slow Memory Leak in JSF tools
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21221?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21221.
---------------------------------
Verified in Red Hat Developer Studio with build id: Alpha1-v20160520-0424-B5396.
> Slow Memory Leak in JSF tools
> -----------------------------
>
> Key: JBIDE-21221
> URL: https://issues.jboss.org/browse/JBIDE-21221
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
> Attached screenshot list:
> 1. GC overhead limit exceeded error [^oom1.png];
> 2. Heap Memory Usage timeline [^mem-usage.png];
> 3. Heap Memory Objects filtered for "org.jboss.tools" [^heap-snapshot2.png];
> 4. Heap Memory Objects none filtered [^heap-snapshot1.png];
> 5. OOM Dialog [^oom2.png]ж
> 6. [^.log]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3895) ClassNotFound exception on clean IDE and workspace
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-3895?page=com.atlassian.jira.plugin.... ]
Pavol Srna updated JBDS-3895:
-----------------------------
Fix Version/s: 10.0.0.Alpha2
> ClassNotFound exception on clean IDE and workspace
> --------------------------------------------------
>
> Key: JBDS-3895
> URL: https://issues.jboss.org/browse/JBDS-3895
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: ui/branding
> Affects Versions: 10.0.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha2
>
>
> In devstudio with build id: Alpha1-v20160520-0424-B5396 there are plenty of error in error log once the IDE has started. See following stacktrace of one from many issues in error log.
> {code}
> Exception occurred while creating new instance of component Component[
> name = com.jboss.devstudio.core.usage.branding
> activate = activate
> deactivate = deactivate
> modified =
> configuration-policy = optional
> factory = null
> autoenable = true
> immediate = true
> implementation = com.jboss.devstudio.core.usage.branding.JBDSUsageBranding
> state = Unsatisfied
> properties = {service.ranking=1}
> serviceFactory = false
> serviceInterface = [org.jboss.tools.usage.branding.IUsageBranding]
> references = null
> located in bundle = com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-0424-B5396 [22]
> ]
> java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-0424-B5396
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:270)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:331)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:482)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.subscribe(EventBroker.java:187)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.subscribe(EventBroker.java:169)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:312)
> 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:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:973)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:649)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:534)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:518)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:973)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:649)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:755)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:726)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:720)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:704)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1317)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:72)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5395)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:617)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:581)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:770)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:744)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:677)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1205)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1283)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1274)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4316)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4312)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4292)
> at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:77)
> at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:200)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:525)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:515)
> at org.eclipse.ui.internal.quickaccess.QuickAccessContents$6.mouseUp(QuickAccessContents.java:726)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:221)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22421) Connection Wizard: Improve extracting of token by informing user/smoothing process
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22421:
-------------------------------------
Summary: Connection Wizard: Improve extracting of token by informing user/smoothing process
Key: JBIDE-22421
URL: https://issues.jboss.org/browse/JBIDE-22421
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha2
Reporter: Marián Labuda
Priority: Minor
In JBIDE-22360 extraction of tokens to log in to OpenShift has been implemented. The process requires a bit of smoothing. User is not informed that the extraction is happening and he finds out only upon closing of the internal browser shell.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22360) Extract OAuth token from the New Connection wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22360?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22360.
---------------------------------
Follow up JIRA has been created. Closing this one as verified.
> Extract OAuth token from the New Connection wizard
> --------------------------------------------------
>
> Key: JBIDE-22360
> URL: https://issues.jboss.org/browse/JBIDE-22360
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: new_and_noteworthy, ux
> Fix For: 4.4.0.Alpha2
>
>
> When creating a new connection in OAuth mode, the user can use an integrated browser to connect to Openshift and once connected, the page displays the token. We could extract the token from that page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3747) Build failures with newest JSPM
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3747?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3747:
------------------------------
Fix Version/s: 10.x
(was: 10.0.0.Alpha2)
> Build failures with newest JSPM
> -------------------------------
>
> Key: JBDS-3747
> URL: https://issues.jboss.org/browse/JBDS-3747
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Minor
> Labels: havoc
> Fix For: 10.x
>
>
> The newest JSPM release (0.16.32 atm.) has broken the build. We have reverted to 0.16.31 until a more permanent solution is discovered. Investigate the failures with newer versions.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3900) The "Java EE Web Project" link from Red Hat Central doesn't work
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3900?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3900:
-----------------------------
> The "Java EE Web Project" link from Red Hat Central doesn't work
> ----------------------------------------------------------------
>
> Key: JBDS-3900
> URL: https://issues.jboss.org/browse/JBDS-3900
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 9.1.0.GA
> Environment: Windows 10 Pro 64 bits
> Intel Core i7 4GB RAM
> jdk1.8.0_91
> Direct internet connection
> Reporter: Claudio Costagliola
> Labels: application_wizard
> Attachments: jbosstools-diagnostics-20160523002632.zip
>
>
> The "Java EE Web Project" link from Red Hat Central doesn't work.
> If I select the same project type from "File - New" menu, it pops up a window saying "Failed to load Wizard",
> "Wizard metadata could not be loaded", "Please check your internet connection, Proxy Settings and try again!".
> I have a direct internet connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3900) The "Java EE Web Project" link from Red Hat Central doesn't work
by Claudio Costagliola (JIRA)
Claudio Costagliola created JBDS-3900:
-----------------------------------------
Summary: The "Java EE Web Project" link from Red Hat Central doesn't work
Key: JBDS-3900
URL: https://issues.jboss.org/browse/JBDS-3900
Project: Red Hat Developer Studio (DevStudio)
Issue Type: Bug
Components: project-examples
Affects Versions: 9.1.0.GA
Environment: Windows 10 Pro 64 bits
Intel Core i7 4GB RAM
jdk1.8.0_91
Direct internet connection
Reporter: Claudio Costagliola
Attachments: jbosstools-diagnostics-20160523002632.zip
The "Java EE Web Project" link from Red Hat Central doesn't work.
If I select the same project type from "File - New" menu, it pops up a window saying "Failed to load Wizard",
"Wizard metadata could not be loaded", "Please check your internet connection, Proxy Settings and try again!".
I have a direct internet connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months