[JBoss JIRA] (JBDS-3497) Installer randomly failing to report download statistics
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3497?page=com.atlassian.jira.plugin.... ]
Dmitrii Bocharov updated JBDS-3497:
-----------------------------------
Fix Version/s: 11.x
(was: 11.1.0.AM1)
> Installer randomly failing to report download statistics
> --------------------------------------------------------
>
> Key: JBDS-3497
> URL: https://issues.jboss.org/browse/JBDS-3497
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, installer, usage
> Affects Versions: 9.0.0.Beta2
> Environment: jboss-devstudio-9.0.0.Beta2-installer-standalone.jar
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 11.x
>
>
> In about every third attempt to install JBDS (or maybe more frequently) a p2 error log appears saying this:
> {noformat}!ENTRY org.eclipse.equinox.p2.artifact.repository 2 0 2015-08-04 08:14:33.521
> !MESSAGE Failure reporting download statistics to URL: https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9....
> !STACK 1
> org.eclipse.core.runtime.CoreException: HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.getLastModified(RepositoryTransport.java:235)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.collectStats(MirrorRequest.java:268)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:235)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1
> at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> ... 1 more
> !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1002 2015-08-04 08:14:33.522
> !MESSAGE HTTP Server Unknown HTTP Response Code (-1):https://devstudio.redhat.com/usage/installs/devstudio.product_9.0.mars/9.0.0-SNAPSHOT/Beta2/Beta2-v20150726-0459-B93/org.eclipse.sapphire.java.jdt
> !STACK 1
> org.eclipse.ecf.filetransfer.BrowseFileTransferException: General connection error with response code=-1
> at org.eclipse.ecf.provider.filetransfer.browse.URLFileSystemBrowser.runRequest(URLFileSystemBrowser.java:131)
> at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !SUBENTRY 2 org.eclipse.ecf.identity 4 0 2015-08-04 08:14:33.522
> !MESSAGE General connection error with response code=-1 {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24754) Redhat central screen doesnt show due to JS error
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24754?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-24754:
------------------------------------------
[~psrna] could you please re-test it?
> Redhat central screen doesnt show due to JS error
> -------------------------------------------------
>
> Key: JBIDE-24754
> URL: https://issues.jboss.org/browse/JBIDE-24754
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.5.0.AM1
> Reporter: Anton Hughes
> Fix For: 4.5.x
>
>
> I am trying to run the latest Jboss Tools (Oxygen) on Ubuntu 17.04.
> h2. Eclipse Version
> Eclipse Java EE IDE for Web Developers.
> Version: Oxygen Release (4.7.0)
> Build id: 20170620-1800
> h2. Stacktrace
> {code:java}
> org.eclipse.swt.SWTException: An exception was raised in JavaScript
> at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
> at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
> at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163)
> at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
> at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614)
> at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
> 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:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
> 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:997)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1289)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.lambda$0(LazyStackRenderer.java:68)
> 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:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5439)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> 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:52)
> 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:620)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437)
> at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425)
> at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4497)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4110)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-24758:
----------------------------------------
Assignee: Rob Stryker
> Server editor complains about wrong runtime folder even if fixed
> ----------------------------------------------------------------
>
> Key: JBIDE-24758
> URL: https://issues.jboss.org/browse/JBIDE-24758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar:
> The server's runtime folder does not exist: ......
> So far so good.
> So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24758:
-------------------------------------
Fix Version/s: 4.5.x
> Server editor complains about wrong runtime folder even if fixed
> ----------------------------------------------------------------
>
> Key: JBIDE-24758
> URL: https://issues.jboss.org/browse/JBIDE-24758
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar:
> The server's runtime folder does not exist: ......
> So far so good.
> So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24777) Creating an application from project should allow to connect project to Git if nissing
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24777?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-24777:
----------------------------------------
Assignee: Andre Dietisheim
> Creating an application from project should allow to connect project to Git if nissing
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-24777
> URL: https://issues.jboss.org/browse/JBIDE-24777
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Andre Dietisheim
> Fix For: 4.5.x
>
>
> Using Red Hat Developer Studio 11.0.AM2.
> I'm trying to deploy a new project to OpenShift (Online). As this project is new, it's not connected to any Git repo.
> When going through the wizards to create an application, the wizard shows an error message because project isn't connected to Git. The only way to connect to Git is to quit the current OpenShift wizard, use the Git wizards to connect project and then re-open the OpenShift wizard.
> I believe a better workflow would be to show in the error message or in the wizard a link to connect the selected repo to Git if it's missing. Then the workflow is more linear and progressive so it's easier for user to move forward.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24779?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov reassigned JBIDE-24779:
----------------------------------------
Assignee: Dmitrii Bocharov
> Starting an OpenShift application seems to lock workspace
> ---------------------------------------------------------
>
> Key: JBIDE-24779
> URL: https://issues.jboss.org/browse/JBIDE-24779
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.x
>
>
> I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages.
> In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete.
> I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months