[JBoss JIRA] (JBIDE-23662) Scaling To/Up/Down: show an error message (from OpenShift API) reporting outdated objects
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23662?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23662 at 1/13/17 5:59 AM:
-------------------------------------------------------------------
I just tested this on MacOS and it wont happen easily, there are no error happening in the vast majority of my tries.
[~rimolive] I could always reproduce this on linux. You're on linux, correct?
was (Author: adietish):
I just tested this on MacOS and it wont happen easily, there's no error happening.
[~rimolive] I could always reproduce this on linux. You're on linux, correct?
> Scaling To/Up/Down: show an error message (from OpenShift API) reporting outdated objects
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23662
> URL: https://issues.jboss.org/browse/JBIDE-23662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
>
> Every Scale option I select in the OpenShift Explorer view show this error:
> Unable to scale guestbook-service
> Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/sample-project/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "guestbook-service-2": the object has been modified; please apply your changes to the latest version and try again
> However, the scale command is executed successfuly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4084) Provide documentation about using the installed DevStudio
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4084?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4084:
---------------------------------------
I'm a bit lost with all the available pages in documentation. I suppose that when following the documentation from start and not just reading it, it is more coherent now but i don't have time to do these steps for now. So i think that we can close this ticket.
> Provide documentation about using the installed DevStudio
> ---------------------------------------------------------
>
> Key: JBDS-4084
> URL: https://issues.jboss.org/browse/JBDS-4084
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: documentation, platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
>
> when following the getting started http://developers.redhat.com/products/devsuite/get-started/
> at the ned it redirect to the "command-line" version to use Containers.
> it would be really better to provide tutorials to use the installed JBDS and the pre-configured CDK which is available in Servers view.
> Personal note: I wasn't able to find by myself how do it in the Studio, I'm representing a UI-lover end-user, I asked for help on Devsuite HipChat channel
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23757?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23757:
-------------------------------
Fix Version/s: 4.4.3.Final
> Thread deadlock when starting Eclipse
> -------------------------------------
>
> Key: JBIDE-23757
> URL: https://issues.jboss.org/browse/JBIDE-23757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: MacOS Sierra, JDK 1.8.0_112
> Reporter: Jon Kranes
> Fix For: 4.4.3.Final
>
>
> Steps to reproduce:
> * Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result)
> * Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final
> * Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results)
> * Add Wildfly 10.x server to Eclipse
> * Create a default Maven Web App project
> * Add the web app project to the Wildfly server
> * Exit Eclipse and restart
> Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit.
> Thread dump output from jvisualvm shows a thread deadlock:
> Found one Java-level deadlock:
> =============================
> "Thread-8":
> waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server),
> which is held by "Worker-0"
> "Worker-0":
> waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager),
> which is held by "Thread-8"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-8":
> at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034)
> - waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152)
> - locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68)
> "Worker-0":
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109)
> - waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> 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.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)
> at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)
> - locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634)
> at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058)
> at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039)
> at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Found 1 deadlock.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23757?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23757:
-------------------------------
Component/s: server
> Thread deadlock when starting Eclipse
> -------------------------------------
>
> Key: JBIDE-23757
> URL: https://issues.jboss.org/browse/JBIDE-23757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: MacOS Sierra, JDK 1.8.0_112
> Reporter: Jon Kranes
> Fix For: 4.4.3.Final
>
>
> Steps to reproduce:
> * Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result)
> * Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final
> * Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results)
> * Add Wildfly 10.x server to Eclipse
> * Create a default Maven Web App project
> * Add the web app project to the Wildfly server
> * Exit Eclipse and restart
> Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit.
> Thread dump output from jvisualvm shows a thread deadlock:
> Found one Java-level deadlock:
> =============================
> "Thread-8":
> waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server),
> which is held by "Worker-0"
> "Worker-0":
> waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager),
> which is held by "Thread-8"
> Java stack information for the threads listed above:
> ===================================================
> "Thread-8":
> at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034)
> - waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152)
> - locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68)
> "Worker-0":
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109)
> - waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager)
> at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
> at org.eclipse.osgi.container.Module.doStart(Module.java:581)
> at org.eclipse.osgi.container.Module.start(Module.java:449)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> 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.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91)
> at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506)
> - locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server)
> at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634)
> at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058)
> at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039)
> at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542)
> at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Found 1 deadlock.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23536:
-------------------------------
Story Points: 5
> components.py should store the assigned user
> --------------------------------------------
>
> Key: JBIDE-23536
> URL: https://issues.jboss.org/browse/JBIDE-23536
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, release, release-eng
> Fix For: 4.4.3.AM2
>
>
> The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23536.
------------------------------
> components.py should store the assigned user
> --------------------------------------------
>
> Key: JBIDE-23536
> URL: https://issues.jboss.org/browse/JBIDE-23536
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, release, release-eng
> Fix For: 4.4.3.AM2
>
>
> The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23536:
------------------------------------
add methods to queryComponentLead() and set a defaultAssignee(); clean up createnewandnoteworthy.py usage and JIRA template; set assignee on JIRAs based on values in NN_components (defined in components.py)
> components.py should store the assigned user
> --------------------------------------------
>
> Key: JBIDE-23536
> URL: https://issues.jboss.org/browse/JBIDE-23536
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, release, release-eng
> Fix For: 4.4.3.AM2
>
>
> The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months