[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23422:
---------------------------------------
Thinking about this further, I don't understand how the router is involved in this workflow. From what I recall, we use 'oc debug' to connect to the pod which would not route any traffic through the router. There are additional switched that may be of use. Do we have this same issue using oc to connect to the pod directly outside of eclipse?
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23422:
---------------------------------------
Looks like nothing can be done from the client side, but open PR to document change to the router that would assist: https://github.com/openshift/openshift-docs/pull/3090
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4080) Avoid to redownload everything on each install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4080?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4080:
--------------------------------
Labels: new_and_noteworthy (was: )
> Avoid to redownload everything on each install
> ----------------------------------------------
>
> Key: JBDS-4080
> URL: https://issues.jboss.org/browse/JBDS-4080
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 10.2.0.AM2
>
> Attachments: page where we see the redownload.png
>
>
> I am at the 3rd attempt to install.
> Even if I reuse the same folder, it redownloads everything and as it takes ages it would be nice to provide cache of the downloaded files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4080) Avoid to redownload everything on each install
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4080?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-4080.
-------------------------------
Resolution: Done
> Avoid to redownload everything on each install
> ----------------------------------------------
>
> Key: JBDS-4080
> URL: https://issues.jboss.org/browse/JBDS-4080
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 1.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 10.2.0.AM2
>
> Attachments: page where we see the redownload.png
>
>
> I am at the 3rd attempt to install.
> Even if I reuse the same folder, it redownloads everything and as it takes ages it would be nice to provide cache of the downloaded files
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-4179 at 11/16/16 11:40 AM:
----------------------------------------------------------------
Nope, but the reason behind it is JDK GraphicsEnvironment.isHeadless() returning true and that is why IzPack decides it has no UI and switches to console mode.
was (Author: dgolovin):
Nope, but the reason behind it is JDK GraphicsEnvironment.isHeadless() returning true and that is why IzPack decides it has no UI and switch to console mode.
> DevStudio installer uses console installation instead of wizard
> ---------------------------------------------------------------
>
> Key: JBDS-4179
> URL: https://issues.jboss.org/browse/JBDS-4179
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.2.0.GA
> Environment: openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Denis Golovin
>
> I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
> This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4184) Can't update/install plugins
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4184?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4184:
-------------------------------
Description:
I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site:
[1] https://devstudio.redhat.com/10.0/snapshots/updates/
Eclipse was not able to detect any updates (I got "No updates were found" message).
Then I tried to install plugins using "Install new software".
Install new software->select Bring Your Own Eclipse->next->restart
Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
[^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
[^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
I also noticed there isn't update site [1] by default after installation. I had to add it.
was:
I tried "Check for Updates" in DevStudio 20161116.1305 and 20161116.1305. I used this update site:
[1] https://devstudio.redhat.com/10.0/snapshots/updates/
Eclipse was not able to detect any updates (I got "No updates were found" message).
Then I tried to install plugins using "Install new software".
Install new software->select Bring Your Own Eclipse->next->restart
Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
[^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
[^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
I also noticed there isn't update site [1] by default after installation. I had to add it.
> Can't update/install plugins
> ----------------------------
>
> Key: JBDS-4184
> URL: https://issues.jboss.org/browse/JBDS-4184
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL 7
> Reporter: Lukáš Valach
> Attachments: rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt
>
>
> I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site:
> [1] https://devstudio.redhat.com/10.0/snapshots/updates/
> Eclipse was not able to detect any updates (I got "No updates were found" message).
> Then I tried to install plugins using "Install new software".
> Install new software->select Bring Your Own Eclipse->next->restart
> Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
> [^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
> [^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
> I also noticed there isn't update site [1] by default after installation. I had to add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4175:
------------------------------------
I tried the same as Vaclav. I got errors after restart - during start of eclipse.
??I don't think Central itself is to blame here??
I think so. See JBDS-4184
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4183) Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4183?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4183:
-----------------------------
Description:
Steps to repro:
1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
{code}
$➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
total 36K
-rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
{code}
But this plugin is already installed here:
{code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
{code}
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
{code}
... the result of this install is to cause use constrain violations and break the devstudio install.
A bigger problem occurs in JBDS-4150 when installing Thym or Aerogear features, since a second version of org.apache.httpcomponents.httpclient_4.3.6.v201511171540.jar is installed even though there's already one in the /opt/rh/ install footprint.
was:
Steps to repro:
1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
{code}
$➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
total 36K
-rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
{code}
But this plugin is already installed here:
{code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
{code}
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
{code}
... the result of this install is to cause use constrain violations and break the devstudio install.
> Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4183
> URL: https://issues.jboss.org/browse/JBDS-4183
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Priority: Blocker
>
> Steps to repro:
> 1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
> 2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
> 3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
> {code}
> $➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
> total 36K
> -rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
> {code}
> But this plugin is already installed here:
> {code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
> So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
> {code}
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
> {code}
> ... the result of this install is to cause use constrain violations and break the devstudio install.
> A bigger problem occurs in JBDS-4150 when installing Thym or Aerogear features, since a second version of org.apache.httpcomponents.httpclient_4.3.6.v201511171540.jar is installed even though there's already one in the /opt/rh/ install footprint.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4184) Can't update/install plugins
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4184:
----------------------------------
Summary: Can't update/install plugins
Key: JBDS-4184
URL: https://issues.jboss.org/browse/JBDS-4184
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 10.2.0.GA
Environment: RHEL 7
Reporter: Lukáš Valach
Attachments: rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt
I tried "Check for Updates" in DevStudio 20161116.1305 and 20161116.1305. I used this update site:
[1] https://devstudio.redhat.com/10.0/snapshots/updates/
Eclipse was not able to detect any updates (I got "No updates were found" message).
Then I tried to install plugins using "Install new software".
Install new software->select Bring Your Own Eclipse->next->restart
Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
[^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
[^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
I also noticed there isn't update site [1] by default after installation. I had to add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months