September 2017 - jbosstools-issues

[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:41 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. 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 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

[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:39 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 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 was (Author: adietish): 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. Still an improvement, isnt it? * 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 commented on JBIDE-24868: ------------------------------------------ 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. Still an improvement, isnt it? * 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-24960) JBDS 11 produces warnings about missing schemas inconsistently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24960: ---------------------------------- Assignee: Jeff MAURY > JBDS 11 produces warnings about missing schemas inconsistently > -------------------------------------------------------------- > > Key: JBIDE-24960 > URL: https://issues.jboss.org/browse/JBIDE-24960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.Final > Reporter: Michal Jurc > Assignee: Jeff MAURY > Fix For: 4.5.1.AM3 > > > The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it. > This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24963: ------------------------------------ Summary: Create CDI 2 integration tests Key: JBIDE-24963 URL: https://issues.jboss.org/browse/JBIDE-24963 Project: Tools (JBoss Tools) Issue Type: Task Components: cdi, integration-tests Affects Versions: 4.5.1.AM2 Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.5.1.AM3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24960: ----------------------------------------- So 2 solutions: - an xsd or DTD exists and it needs to be provided - no xsd/DTD exists and in this case the doctype need to be specified <!DOCTYPE xml> > JBDS 11 produces warnings about missing schemas inconsistently > -------------------------------------------------------------- > > Key: JBIDE-24960 > URL: https://issues.jboss.org/browse/JBIDE-24960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.Final > Reporter: Michal Jurc > Fix For: 4.5.1.AM3 > > > The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it. > This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24960: ----------------------------------------- When I read the wildfly-config.xml file here https://github.com/jboss-developer/jboss-eap-quickstarts/blob/7.1.0.Beta/... it seems that the top level tag "configuration" is effectively missing a grammar constraint > JBDS 11 produces warnings about missing schemas inconsistently > -------------------------------------------------------------- > > Key: JBIDE-24960 > URL: https://issues.jboss.org/browse/JBIDE-24960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.Final > Reporter: Michal Jurc > Fix For: 4.5.1.AM3 > > > The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it. > This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-24960: ------------------------------------ Steps to Reproduce: Checkout {{ejb-remote}} and {{ejb-security-jaas}} quickstarts from https://github.com/jboss-developer/jboss-eap-quickstarts and import them into JBDS11. (was: Checkout {{ejb-remote}} and {{ejb-security-jaas}} quickstarts from https://github.com/jbossas/eap-quickstarts and import them into JBDS11.) > JBDS 11 produces warnings about missing schemas inconsistently > -------------------------------------------------------------- > > Key: JBIDE-24960 > URL: https://issues.jboss.org/browse/JBIDE-24960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.Final > Reporter: Michal Jurc > Fix For: 4.5.1.AM3 > > > The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it. > This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-4410: ----------------------------------- Basically, we have the 'online' installer and 'bundled' installer to make things a little more complicated. - online installer only has the cygwin setup bundled in - bundled installer bundles devstudio, CDK, openJDK (for windows only), and cygwin > DevSuite 1.4 Installer indicate download size during choice selection > --------------------------------------------------------------------- > > Key: JBDS-4410 > URL: https://issues.jboss.org/browse/JBDS-4410 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Mohit Suman > Priority: Minor > Fix For: 11.1.0.AM1 > > Attachments: size-pkg.png > > > During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late. > The two use cases I see for this: > # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later. > # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V. > Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4410) DevSuite 1.4 Installer indicate download size during choice selection

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4410?page=com.atlassian.jira.plugin.... ] Mohit Suman commented on JBDS-4410: ----------------------------------- [~jrichter1] Can you please let me know which bundled component are we discussing about here. This we have added to give the user idea about the component size when the entire product will be downloaded. > DevSuite 1.4 Installer indicate download size during choice selection > --------------------------------------------------------------------- > > Key: JBDS-4410 > URL: https://issues.jboss.org/browse/JBDS-4410 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Mohit Suman > Priority: Minor > Fix For: 11.1.0.AM1 > > Attachments: size-pkg.png > > > During the software selection phase the DevSuite 1.4 installer should indicate the approximate size of the download. The download size is shown during actual installation progress, but by that time it's too late. > The two use cases I see for this: > # A minishift/CDK user that is looking to try OpenShift might not want to download and install all of JBoss. Seeing the size of it ahead of time, would avoid some shock later. > # When trying to decide between enabling Hyper-V or installing VirtualBox, knowing the size might influence the user to just enable Hyper-V. > Note: I think I filed a bug against a previous version that the installer provides No estimate of the required disk space in order to proceed. Doesn't look like it is still open. -- 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