[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4162:
----------------------------------
Note that if you install ANYTHING from Central (or in fact any other update site), the missing dependency will be installed into .eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
So... this is a pretty benign issue. Perhaps we should add the plugin back into the rpm install so it's already installed by default?
> unresolved bundles - slf4j
> ---------------------------
>
> Key: JBDS-4162
> URL: https://issues.jboss.org/browse/JBDS-4162
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rhscl, rpm, target-platform
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: who-uses_ch.qos.logback.slf4j_1.0.7.png, who-uses_slf4j.impl.log4j12_1.7.2.png
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
> org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23487) Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23487?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-23487.
------------------------------------
confirmed by QE that cant be replicated. Closing.
> Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23487
> URL: https://issues.jboss.org/browse/JBIDE-23487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Martin Malina
> Assignee: Andre Dietisheim
> Labels: openshift_v3, rsync, server_adapter
> Fix For: 4.4.2.Final
>
>
> While testing Rob's jolokia stuff from JBIDE-23429 I did this:
> 1. Start CDK (2.3.cr1)
> 2. Create eap64-basic-s2i app
> 3. Wait till the app is built and the pod is running
> 4. Right-click the eap-app in OpenShift explorer and create a server adapter
> 5. Now the server adapter is publishing and this will fail:
> {code}
> Could not sync /Users/rasp/jbossqa/JBDS/10.0.0/workspace-neon-1a/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> Syncing com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@41249d31 to com.openshift.restclient.capability.resources.IRSyncable$PodPeer@27c8ba3a failed: Unable to connect to the server: net/http: TLS handshake timeout
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
> error: exit status 12
> {code}
> This is on macOS Sierra with JBoss Tools from master with Rob's patches, but he says his patches have nothing to do with publishing. I may try out a normal build of devstudio or JBT later.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23487) Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23487?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-23487.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Cannot Reproduce Bug
resolving since cant be replicated for now. Feel free to reopen if you face it again.
> Server adapter: Publishing fails when server adapter is created out of eap app running on openshift (in cdk)
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23487
> URL: https://issues.jboss.org/browse/JBIDE-23487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Martin Malina
> Assignee: Andre Dietisheim
> Labels: openshift_v3, rsync, server_adapter
> Fix For: 4.4.2.Final
>
>
> While testing Rob's jolokia stuff from JBIDE-23429 I did this:
> 1. Start CDK (2.3.cr1)
> 2. Create eap64-basic-s2i app
> 3. Wait till the app is built and the pod is running
> 4. Right-click the eap-app in OpenShift explorer and create a server adapter
> 5. Now the server adapter is publishing and this will fail:
> {code}
> Could not sync /Users/rasp/jbossqa/JBDS/10.0.0/workspace-neon-1a/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample-project@eap-app/deploy to all pods running the service eap-app
> Syncing com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@41249d31 to com.openshift.restclient.capability.resources.IRSyncable$PodPeer@27c8ba3a failed: Unable to connect to the server: net/http: TLS handshake timeout
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
> error: exit status 12
> {code}
> This is on macOS Sierra with JBoss Tools from master with Rob's patches, but he says his patches have nothing to do with publishing. I may try out a normal build of devstudio or JBT later.
--
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:
---------------------------------------
It looks that way
> 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-4179) DevStudio installer uses console installation instead of wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4179:
--------------------------------------
[~mlabuda] does it reproducible on Fedora (with JDK 1.8.0_102) only?
Looks like pure upstream issue which worth documentation. cc: [~mhusnain]
> 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: documentation, installer, upstream
> 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-4179) DevStudio installer uses console installation instead of wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4179:
---------------------------------
Workaround Description: Update OpenJDK
> 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: documentation, installer, upstream
> 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] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23422 at 11/16/16 1:03 PM:
--------------------------------------------------------------------
[~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config:
{quote}
`*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data.
`*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time.
`*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data.
`*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open.
{quote}
So when enabling debugging we should be able to alter the deployment config of the router?
was (Author: adietish):
[~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config:
{quote}
`*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data.
`*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time.
`*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data.
`*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open.
{quote}
> 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23422:
------------------------------------------
[~jcantrill] thx, I was pointed to the same PR and if I read it carefully I see the following options that we can set to the env vars of the deployment config:
{quote}
`*ROUTER_DEFAULT_CLIENT_TIMEOUT*`| 30s | How long a client has to acknowledge or send data.
`*ROUTER_DEFAULT_CONNECT_TIMEOUT*`| 5s | The maximum connect time.
`*ROUTER_DEFAULT_SERVER_TIMEOUT*`| 30s | How long a server has to acknowledge or send data.
`*ROUTER_DEFAULT_TUNNEL_TIMEOUT*` | 1h | How long to allow TCP or WebSocket connections to remain open.
{quote}
> 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-4179) DevStudio installer uses console installation instead of wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4179:
---------------------------------
Component/s: documentation
> 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: documentation, installer, upstream
> 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-4179) DevStudio installer uses console installation instead of wizard
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4179:
---------------------------------
Component/s: upstream
> 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, upstream
> 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