[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21059:
-----------------------------------
Fix Version/s: 4.4.x
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21745:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Unable to download EAP 7 Beta runtime using username without "@redhat.com"
> --------------------------------------------------------------------------
>
> Key: JBIDE-21745
> URL: https://issues.jboss.org/browse/JBIDE-21745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Final, 4.3.1.CR1
> Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page.
> Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown:
> {noformat}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {noformat}
> But even after that I'm unable to download that runtime with the same credentials.
> Using login with "@redhat.com" I'm able to download the runtime.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21953) 10.1.2.2.* not working on Windows from RH network
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21953:
--------------------------------------
Assignee: Hardy Ferentschik (was: Martin Malina)
> 10.1.2.2.* not working on Windows from RH network
> -------------------------------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21992:
-----------------------------------------------
If this issue is resolved, should be create a new one for missing descriptions?
By the way, there is a common issue with descriptions. If a dialog is not pre-filled and requires user input, then error/cancel message prompting user to do the input usually appears in the message area so that user will know what the page is about only after he puts correct values. :)
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21992 at 3/30/16 1:41 PM:
------------------------------------------------------------------------
If this issue is resolved, should we create a new one for missing descriptions?
By the way, there is a common issue with descriptions. If a dialog is not pre-filled and requires user input, then error/cancel message prompting user to do the input usually appears in the message area so that user will know what the page is about only after he puts correct values. :)
was (Author: scabanovich):
If this issue is resolved, should be create a new one for missing descriptions?
By the way, there is a common issue with descriptions. If a dialog is not pre-filled and requires user input, then error/cancel message prompting user to do the input usually appears in the message area so that user will know what the page is about only after he puts correct values. :)
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21953) 10.1.2.2.* not working on Windows from RH network
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21953:
-----------------------------------
Summary: 10.1.2.2.* not working on Windows from RH network (was: xip.io not working on Windows)
> 10.1.2.2.* not working on Windows from RH network
> -------------------------------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22005:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Unexpected EOF in pod log
> -------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21953) xip.io not working on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21953:
-----------------------------------
Fix Version/s: 4.4.x
> xip.io not working on Windows
> -----------------------------
>
> Key: JBIDE-21953
> URL: https://issues.jboss.org/browse/JBIDE-21953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Martin Malina
> Priority: Critical
> Fix For: 4.4.x
>
>
> This is definitely an upstream issue, but I think it's worth having it here and gather information from others.
> Marian tried openshift with cdk today on our Windows laptop and the url generated for the app he deployed didn't work.
> So I tried something simple like "ping 10.1.2.2.xip.io" from command line and it didn't work.
> "ping xip.io" worked.
> On my OS X laptop, this works as expected:
> {code}
> $ ping 10.1.2.2.xip.io
> PING 10.1.2.2.xip.io (10.1.2.2): 56 data bytes
> Request timeout for icmp_seq 0
> {code}
> Whereas on windows I only get:
> Ping request could not find host 10.1.2.2.xip.io. Please check the name and try again.
> I'm not sure if it's just a problem with our laptop, but it needs investigating in any case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22005) Unexpected EOF in pod log
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22005:
---------------------------------------
This could also be maybe the connection is open so long that it times out? Can you describe how long it was open and provide any eclipse logs that may be relevant?
> Unexpected EOF in pod log
> -------------------------
>
> Key: JBIDE-22005
> URL: https://issues.jboss.org/browse/JBIDE-22005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
>
> I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log.
> Last lines from console (output of application pod log)
> {code}
> ...
> [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe...
> error: unexpected EOF
> {code}
> I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months