August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26159: ------------------------------------- Sprint: devex #154 September 2018 (was: devex #153 August 2018) > Server adapter: debugging is not stopped if you delete the pod > -------------------------------------------------------------- > > Key: JBIDE-26159 > URL: https://issues.jboss.org/browse/JBIDE-26159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Minor > Labels: port_forwarding, server_adapter > Fix For: 4.9.x > > > steps: > Screencast: https://youtu.be/XMA--S9zj6s > # EXEC: create an application (via ex. nodejs-mongo-persistent template) > # ASSERT: pod for service is running > # EXEC: select pod and pick "Port Forwarding..." and start the forwarding > # ASSERT: forwarding is running > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # EXEC: verify on the cmd-line that the forwarding is running > {code} > $ ps ax | grep oc > 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080 > {code} > Result: > The port forwarding is still running. > In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed). > PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-26160: ------------------------------------- Sprint: devex #154 September 2018 (was: devex #153 August 2018) > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: server_adapter > Fix For: 4.9.x > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. The new pod is not running in debug (dev-) mode any more. To have it running again you need to restart the server adapter into debug, which will re-create a new pod in debug-mode. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26277) Update Test Plan for Devstudio

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26277?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-26277: ------------------------------------ Test plan document is here: https://mojo.redhat.com/docs/DOC-1179340 > Update Test Plan for Devstudio > ------------------------------ > > Key: JBIDE-26277 > URL: https://issues.jboss.org/browse/JBIDE-26277 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.0.AM2 > > > Test plan is outdated and needs to be up to date. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26277) Update Test Plan for Devstudio

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26277?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-26277. -------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.x) Resolution: Done > Update Test Plan for Devstudio > ------------------------------ > > Key: JBIDE-26277 > URL: https://issues.jboss.org/browse/JBIDE-26277 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.0.AM2 > > > Test plan is outdated and needs to be up to date. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26277) Update Test Plan for Devstudio

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26277?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-26277. ------------------------------ > Update Test Plan for Devstudio > ------------------------------ > > Key: JBIDE-26277 > URL: https://issues.jboss.org/browse/JBIDE-26277 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.0.AM2 > > > Test plan is outdated and needs to be up to date. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26278) Fix failing hibernate itests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26278?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-26278: ------------------------------- Sprint: devex #154 September 2018 (was: devex #153 August 2018) > Fix failing hibernate itests > ----------------------------- > > Key: JBIDE-26278 > URL: https://issues.jboss.org/browse/JBIDE-26278 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.x > > > TBD -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26279) Fix failing jax-rs itests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26279?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-26279: ------------------------------- Sprint: devex #154 September 2018 (was: devex #153 August 2018) > Fix failing jax-rs itests > -------------------------- > > Key: JBIDE-26279 > URL: https://issues.jboss.org/browse/JBIDE-26279 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.9.x > > > TBD -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26315) Fix usage test job to run on openstack infra

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-26315: ---------------------------------- Summary: Fix usage test job to run on openstack infra Key: JBIDE-26315 URL: https://issues.jboss.org/browse/JBIDE-26315 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: qa Reporter: Pavol Srna Assignee: Pavol Srna Fix For: 4.9.0.AM3 The job runs here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... ToDos: * bot-ci credentials to access google analytics for jbosstools * selenium implementation in tests for login; https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/InfrastructureT... * jenkins job adjustments -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4652) JDK9 Certification - javascript

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4652?page=com.atlassian.jira.plugin.... ] Pavol Srna resolved JBDS-4652. ------------------------------ Fix Version/s: 12.9.0.AM2 (was: 12.9.0.AM3) Resolution: Done > JDK9 Certification - javascript > ------------------------------- > > Key: JBDS-4652 > URL: https://issues.jboss.org/browse/JBDS-4652 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: javascript > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 12.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4722) Problem creating splash implementation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4722?page=com.atlassian.jira.plugin.... ] Ondrej Dockal reassigned JBDS-4722: ----------------------------------- Assignee: Nick Boldt (was: Ondrej Dockal) > Problem creating splash implementation > -------------------------------------- > > Key: JBDS-4722 > URL: https://issues.jboss.org/browse/JBDS-4722 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: product > Affects Versions: 12.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Nick Boldt > Fix For: 12.9.0.AM3 > > > I got a bunch of error while restarting/starting over devstudio. > {code} > Problem creating splash implementation > java.lang.UnsupportedClassVersionError: com/jboss/devstudio/core/splash/SplashHandler has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:763) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:276) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:555) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:514) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:501) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:470) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:177) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:931) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:60) > at org.eclipse.ui.internal.WorkbenchPlugin.lambda$0(WorkbenchPlugin.java:288) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:71) > at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:285) > at org.eclipse.ui.internal.splash.SplashHandlerFactory$1.run(SplashHandlerFactory.java:134) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.splash.SplashHandlerFactory.create(SplashHandlerFactory.java:129) > at org.eclipse.ui.internal.splash.SplashHandlerFactory.processElement(SplashHandlerFactory.java:112) > at org.eclipse.ui.internal.splash.SplashHandlerFactory.findSplashHandlerFor(SplashHandlerFactory.java:60) > at org.eclipse.ui.internal.Workbench.getSplash(Workbench.java:892) > at org.eclipse.ui.internal.Workbench.access$2(Workbench.java:884) > at org.eclipse.ui.internal.Workbench$2.run(Workbench.java:782) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench.createSplashWrapper(Workbench.java:846) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:597) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:560) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) > 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:656) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592) > at org.eclipse.equinox.launcher.Main.run(Main.java:1498) > at org.eclipse.equinox.launcher.Main.main(Main.java:1471) > Session data: > eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091 > java.version=1.8.0_172 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018