September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24844 at 9/1/17 4:25 PM: ------------------------------------------------------------ Current state: !redballs-16.png|thumbnail! Trying a couple things: a) use SHORT_COMBINATION for workspace paths, as we seem to have intermittent failures on Windows slaves [1]. b) enable Naginator to rebuild failing matrix combos (eg., because a slave dies in mid-run) after 30 mins [2] Testing these fixes on this build [3]. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=97 was (Author: nickboldt): Trying a couple things: a) use SHORT_COMBINATION for workspace paths, as we seem to have intermittent failures on Windows slaves [1]. b) enable Naginator to rebuild failing matrix combos (eg., because a slave dies in mid-run) after 30 mins [2] Testing these fixes on this build [3]. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=97 > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > Attachments: red-weekly-smoke-tests.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24844 at 9/1/17 4:24 PM: ------------------------------------------------------------ Updated a number of smoke/weekly jobs to use label_exp instead of label, and run the macosx configs w/ jdk1.8 (not openjdk-1.8). For jobs where configuration has fedora or ubuntu, I didn't change the jobs (even if there was a filter for mac, but the job doesn't run on mac). https://github.com/jbdevstudio/jbdevstudio-ci/commit/c6da931da894697a0b2c... Current state (18 red balls): !red-weekly-smoke-tests.png|thumbnail! See also JBIDE-24895 was (Author: nickboldt): Updated a number of smoke/weekly jobs to use label_exp instead of label, and run the macosx configs w/ jdk1.8 (not openjdk-1.8). For jobs where configuration has fedora or ubuntu, I didn't change the jobs (even if there was a filter for mac, but the job doesn't run on mac). https://github.com/jbdevstudio/jbdevstudio-ci/commit/c6da931da894697a0b2c... Current state: !red-weekly-smoke-tests.png|thumbnail! See also JBIDE-24895 > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > Attachments: red-weekly-smoke-tests.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24844) fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24844?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24844: ------------------------------------ Trying a couple things: a) use SHORT_COMBINATION for workspace paths, as we seem to have intermittent failures on Windows slaves [1]. b) enable Naginator to rebuild failing matrix combos (eg., because a slave dies in mid-run) after 30 mins [2] Testing these fixes on this build [3]. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=97 > fix *.it.weekly jobs to properly build on macos w/ jdk1.8 (not openjdk 1.8) > --------------------------------------------------------------------------- > > Key: JBIDE-24844 > URL: https://issues.jboss.org/browse/JBIDE-24844 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > Attachments: red-weekly-smoke-tests.png > > > As noted in JBIDE-24835, the it.weekly jobs try to run on macos w/ openjdk 1.8, but no such JDK exists there. Therefore need a combinationFilter to let us build with openjdk on windows and linux, and oracle jdk on macos. > {code} > combinationFilter = (label_exp == "macosx").implies(jdk == "jdk1.8") && (label_exp != "macosx").implies(jdk == "openjdk-1.8") > {code} > TODO: verify all the jobs linked from here [1] are working for all OSes > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi... > * hibernatetools-itests.download-devstudio - test failures on rhel7 (not a matrix job) > * livereload.it.weekly - failing for windows 8.1 & 10 due to unresolved parent pom > * browsersim.it.weekly - failing for windows 8.1 due to unresolved parent pom > * archives.it.weekly - failed to resolve tycho-plugins:repo-utils1.0.0 (bad Nexus settings?) on win81 > * vpe.it.weekly - test failures on win81 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24763: ------------------------------------ Holy crap, we're down to less than 10 failing tests per OS/JDK combination. This one seems to fail most often, on rhel7, win10, win81, and win7: {code} Failed org.jboss.tools.as.ui.bot.itests.download.InvalidCredentialProductDownloadTest.useInvalidCredentials default (from org.jboss.tools.as.ui.bot.itests.AllTestsSuite) The following shells remained open [NLS missing message: WizardError in: org.jboss.tools.foundation.ui.internal.messages] Stacktrace java.lang.AssertionError: The following shells remained open [NLS missing message: WizardError in: org.jboss.tools.foundation.ui.internal.messages] at org.junit.Assert.fail(Assert.java:88) at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.run(CloseAllShellsExt.java:79) at org.jboss.reddeer.junit.extension.after.test.impl.CloseAllShellsExt.runAfterTest(CloseAllShellsExt.java:71) at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:74) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:171) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57){code} https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... Second most common failures are these, on win10, win81, and win7 (links above): {code} org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operate default [1] org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest default.org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest default org.jboss.tools.jmx.core.test.DefaultProviderTest.testConnection {code} > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > 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.1.AM2 > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4069) BreadCrumb should be fixed on top of the page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4069?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4069: -------------------------------- Fix Version/s: 11.1.0.AM2 (was: 11.x) > BreadCrumb should be fixed on top of the page > --------------------------------------------- > > Key: JBDS-4069 > URL: https://issues.jboss.org/browse/JBDS-4069 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Mohit Suman > Labels: ui > Fix For: 11.1.0.AM2 > > > Confirmation and Install pages have scrolling. BreadCrumb should always stay on to of the page to let user see current steps and overall installation progress without scrolling back up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4528) Fix download size value in bytes for components

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4528?page=com.atlassian.jira.plugin.... ] Mohit Suman reassigned JBDS-4528: --------------------------------- Assignee: Mohit Suman > Fix download size value in bytes for components > ----------------------------------------------- > > Key: JBDS-4528 > URL: https://issues.jboss.org/browse/JBDS-4528 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM1 > Reporter: Mohit Suman > Assignee: Mohit Suman > > The product download size value to be updated and stored in bytes(binary). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4528) Fix download size value in bytes for components

by Mohit Suman (JIRA)

Mohit Suman created JBDS-4528: --------------------------------- Summary: Fix download size value in bytes for components Key: JBDS-4528 URL: https://issues.jboss.org/browse/JBDS-4528 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 11.1.0.AM1 Reporter: Mohit Suman The product download size value to be updated and stored in bytes(binary). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-24797: ------------------------------------------ I found the maven plugin, that allows to apply formatting exported from Eclipse preferences: http://code.revelc.net/formatter-maven-plugin/formatter-maven-plugin/. I also created 2 PRs to jbosstools-openshift # https://github.com/jbosstools/jbosstools-openshift/pull/1560 - slightly changed eclipse formatter # https://github.com/jbosstools/jbosstools-openshift/pull/1559 - default eclipse formatter You can find all the details in the PR comment. > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.AM2 > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:50 AM: ------------------------------------------------------------------- [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up and terminates once you have it continue after the breakpoint (F8). So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:50 AM: ------------------------------------------------------------------- [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2017