[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22773:
------------------------------------------
i successfully ran _oc rsync_ after setting permissions for _<workspace-dir>/.metadata/.plugins_:
write click on this dir -> Properties -> Security tab -> Choose "Users" group in the upper list -> put ticks for everything in "Allow" column.
> Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22773
> URL: https://issues.jboss.org/browse/JBIDE-22773
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: server
> Fix For: 4.4.4.Final
>
> Attachments: screenshot-1.png
>
>
> When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error:
> [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24222:
---------------------------------------
This works correctly if you start it first in Terminal and then in Eclipse when it's already running - CDK tooling will recognise it's already running and will just mark it as Started in the Servers view. So that's a workaround.
When this error happens, it seems the tooling shuts down the VM immediately. So when I tried minishift status in Terminal afterwards, it was already Stopped.
> CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24222
> URL: https://issues.jboss.org/browse/JBIDE-24222
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM2
> Environment: macos
> xhyve supervisor
> cdk3 beta3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24186) Eclipse workspace deadlocking during refresh/rebuild
by Beirti O'Nunain (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24186?page=com.atlassian.jira.plugi... ]
Beirti O'Nunain commented on JBIDE-24186:
-----------------------------------------
[~rob.stryker] - FYI: I've not seen this issue (yet) since switching to using just the server components in Eclipse as Jeff described in https://issues.jboss.org/browse/JBIDE-24187
Appreciate that isn't helpful for investigating the deadlock though...
> Eclipse workspace deadlocking during refresh/rebuild
> ----------------------------------------------------
>
> Key: JBIDE-24186
> URL: https://issues.jboss.org/browse/JBIDE-24186
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server
> Affects Versions: 4.4.3.Final
> Reporter: Beirti O'Nunain
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
>
> - Windows 7
> - Eclipse Neon.2 (4.6.2)
> - Developer Studio 10.3.0
> After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
> + "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> ....
> The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
> Profiling with yourkit detects a deadlock in the following thread:
> Worker-33 <--- Frozen for at least 8m 27s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
> I started profiling Yourkit when the build hung. It shows the following as the live call stack:
> Call Tree Time (ms) Level
> <All threads> 530944 1
> org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
> org.eclipse.equinox.launcher.Main.run(String[]) 436 2
> org.eclipse.core.internal.jobs.Worker.run() 421 2
> I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
> Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
> Frozen threads found (potential deadlock)
> It seems that the following threads have not changed their stack for more than 10 seconds.
> These threads are possibly (but not necessarily!) in a deadlock or hung.
> main <--- Frozen for at least 2m 21s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
> org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
> org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
> org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
> org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
> org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
> org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
> org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
> org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
> org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
> org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
> org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
> org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
> org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
> org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
> org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
> org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
> org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
> org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
> org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
> org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
> org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
> org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
> org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
> org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
> org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
> org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
> org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
> sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
> sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
> java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
> org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
> org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
> org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
> Worker-33 <--- Frozen for at least 14m 43s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22773:
------------------------------------------
According to my previous comment and [advanced rsync features for openshift |https://docs.openshift.org/latest/dev_guide/copy_files_to_container.html#advanced-rsync-features] tried to do smth like:
{code:bash}
rsync --rsh='oc rsh --token=PPf_cx_lJnph03Y9tY7SB2mKTtV1WIqg-0dryj5oSqM --server=https://10.1.2.2:8443 --insecure-skip-tls-verify=true -n sample-project' --chmod=ugo=rwX --exclude='.git' jboss-eap70-openshift-1-w4q6z:/opt/eap/standalone/deployments/ /cygdrive/dev/openshift/runtime-New_configuration/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@jboss-eap70-openshift/deploy/
{code}
however, got _rsync error: error in rsync protocol data stream (code 12) at io.c(600) _ and many more errors
> Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22773
> URL: https://issues.jboss.org/browse/JBIDE-22773
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: server
> Fix For: 4.4.4.Final
>
> Attachments: screenshot-1.png
>
>
> When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error:
> [^screenshot-1.png]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24276) CDK3 server adapter/editor: UI inconsistencies - widget order, labels
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24276?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-24276:
--------------------------------
Fix Version/s: 4.4.4.AM3
> CDK3 server adapter/editor: UI inconsistencies - widget order, labels
> ---------------------------------------------------------------------
>
> Key: JBIDE-24276
> URL: https://issues.jboss.org/browse/JBIDE-24276
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.4.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
> Attachments: editor-1location-2hypervisor.png, editor-minishift-location.png, wizard-1hypervisor-2location.png, wizard-minishift-binary.png
>
>
> CDK3 Server adapter wizard and editor differ in labelling and widget ordering. It would be nice if those 2 could be consistent.
> * the widget to set the minishift binary is labeled "Minishift Binary" in the wizard, "Minishift Location" in the editor
> !wizard-minishift-binary.png!
> !editor-minishift-location.png!
> * the widget order in the wizard is 1) Hypervisor 2) Minishift Location while in the editor it's the opposite: 1) Minishift Location 2) Hypervisor
> !editor-1location-2hypervisor.png!
> !wizard-1hypervisor-2location.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24276) CDK3 server adapter/editor: UI inconsistencies - widget order, labels
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24276?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-24276.
---------------------------------
Resolution: Done
pushed to master / maintenance. Simple changes, 2 lines.
> CDK3 server adapter/editor: UI inconsistencies - widget order, labels
> ---------------------------------------------------------------------
>
> Key: JBIDE-24276
> URL: https://issues.jboss.org/browse/JBIDE-24276
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.4.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM3
>
> Attachments: editor-1location-2hypervisor.png, editor-minishift-location.png, wizard-1hypervisor-2location.png, wizard-minishift-binary.png
>
>
> CDK3 Server adapter wizard and editor differ in labelling and widget ordering. It would be nice if those 2 could be consistent.
> * the widget to set the minishift binary is labeled "Minishift Binary" in the wizard, "Minishift Location" in the editor
> !wizard-minishift-binary.png!
> !editor-minishift-location.png!
> * the widget order in the wizard is 1) Hypervisor 2) Minishift Location while in the editor it's the opposite: 1) Minishift Location 2) Hypervisor
> !editor-1location-2hypervisor.png!
> !wizard-1hypervisor-2location.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBTIS-1092) Update IS Neon target platform - 4.4.3
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1092:
---------------------------------
Summary: Update IS Neon target platform - 4.4.3
Key: JBTIS-1092
URL: https://issues.jboss.org/browse/JBTIS-1092
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: target-platform
Affects Versions: 4.4.3.CR1-TP
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.4.3.CR1-TP
*Reason:* Update JBT to 4.4.4.AM2a
*Project page/sources:*
*Version:* 4.4.3 IS TP
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* JBTIS/ DevstudioIS
*Include in JBDS:* Yes (IS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months