[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21847:
----------------------------------
Attachment: video.ogg-2.ogv
Attached screencast. Application is created from eap basic s2i template. You can see there are 3 ports available for port forwarding. It seems it is not properly rendered/redrawn upon stopping port forwarding (notice checking/unchecking checkbox make button Start All available).
> Start port forwarding button is disabled after starting and stopping it
> -----------------------------------------------------------------------
>
> Key: JBIDE-21847
> URL: https://issues.jboss.org/browse/JBIDE-21847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: video.ogg-2.ogv
>
>
> In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21847:
---------------------------------------
Environment: Fedora 22, OpenShift tooling B219 in Eclipse 4.5.2 using local OpenShift 3.2 from cdk2.
I will attach a screencast in few minutes.
> Start port forwarding button is disabled after starting and stopping it
> -----------------------------------------------------------------------
>
> Key: JBIDE-21847
> URL: https://issues.jboss.org/browse/JBIDE-21847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1
>
>
> In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Michal Jurc commented on JBIDE-21822:
-------------------------------------
I have discovered that I have been importing the {{ejb-remote}} quickstart in a wrong way. Quickstarts will not import correctly if they are located in JBDS workspace. Also, importing the quickstart projects by {{File -> Import Projects from Folder}} instead of using {{File -> Import -> Existing Maven Projects}} will result in the same error. Importing the {{ejb-remote}} quickstart by {{File -> Import Projects from Folder}} will load projects called {{ejb-remote}}, {{ejb-remote-client}} and {{ejb-remote-server-side}} in Project Explorer while importing the quickstart by {{File -> Import Projects from Folder}} will load projects called {{jboss-ejb-remote}}, {{jboss-ejb-remote-client}} and {{jboss-ejb-remote-server-side}}.
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Michal Jurc edited comment on JBIDE-21822 at 3/11/16 3:12 AM:
--------------------------------------------------------------
I have discovered that I have been importing the {{ejb-remote}} quickstart in a wrong way. Quickstarts will not import correctly if they are located in JBDS workspace. Also, importing the quickstart projects by {{File -> Import Projects from Folder}} instead of using {{File -> Import -> Existing Maven Projects}} will result in the error mentioned in the issue. Importing the {{ejb-remote}} quickstart by {{File -> Import Projects from Folder}} will load projects called {{ejb-remote}}, {{ejb-remote-client}} and {{ejb-remote-server-side}} in Project Explorer while importing the quickstart by {{File -> Import Projects from Folder}} will load projects called {{jboss-ejb-remote}}, {{jboss-ejb-remote-client}} and {{jboss-ejb-remote-server-side}}.
was (Author: mjurc):
I have discovered that I have been importing the {{ejb-remote}} quickstart in a wrong way. Quickstarts will not import correctly if they are located in JBDS workspace. Also, importing the quickstart projects by {{File -> Import Projects from Folder}} instead of using {{File -> Import -> Existing Maven Projects}} will result in the same error. Importing the {{ejb-remote}} quickstart by {{File -> Import Projects from Folder}} will load projects called {{ejb-remote}}, {{ejb-remote-client}} and {{ejb-remote-server-side}} in Project Explorer while importing the quickstart by {{File -> Import Projects from Folder}} will load projects called {{jboss-ejb-remote}}, {{jboss-ejb-remote-client}} and {{jboss-ejb-remote-server-side}}.
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Xia Zhao (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Xia Zhao updated JBIDE-21849:
-----------------------------
Description:
-Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
-Issue did not repro if switch to OSE
-Repro on Linux/Windows/Mac OS
was:No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Xia Zhao (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Xia Zhao updated JBIDE-21849:
-----------------------------
Environment:
-JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
-AP puddle: 2016-03-09.2
-oc version:
oc v3.2.0.1
kubernetes v1.2.0-alpha.7-703-gbc4550d
was:
OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
OS: Fedora 17 & MAC OS 10
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3
>
> No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Xia Zhao (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Xia Zhao updated JBIDE-21849:
-----------------------------
Steps to Reproduce:
1.Login to AP by oc client
2.Create a new project with sufficient resources in it:
$oc get svc
NAME CLUSTER_IP EXTERNAL_IP PORT(S) SELECTOR AGE
java-mainclass x.x.x.x <none> 8778/TCP app=java-mainclass,deploymentconfig=java-mainclass 4m
$ oc get po
NAME READY STATUS RESTARTS AGE
java-mainclass-1-u62c4 1/1 Running 0 5m
java-mainclass-1-y7igr 1/1 Running 0 6m
3.Logout from oc client
4.Login AP with JBT, expand the project node
Actual Result:
Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
Expected Result:
Should list all the services under a project
Additional info:
The related issue on oc side is fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1311049
was:
1. Prepare 2 applications which will deliver different HTML outputs on a same port 8080. Say pod1 in project1 will reurn string "I'm A" if you curl http://127.0.0.1/8080 after a successful port-forward operation, and pod2 in project2 will reutrn string "I'm B" if you curl http://127.0.0.1/8080 after a successful port-forward operation. (Let me know if you need the detailed application json files for these 2 projects)
2. Deploy these 2 applications sepereately into project1 and project2 of openshift
3. Login openshift with JBT (I used Jboss Developer Studio on Mac OS)
4. Inside JBT, go to project1, right click on pod1 (when this pod is running healty), port-forward it to local port 8080 --> This is used to make local 8080 port is now in use
5. curl http://127.0.0.1/8080, should return string "I'm A" in the result HTML file
6. If you go back to JBT, close the port-forward window in step #4, and revisit it , should still see from UI that port forwarding is in process
7. Now go to project2, right click on pod2 (when this pod is running healty), port-forward it to local port 8080 --> This should not be success since port 8080 is already in use, but no error message is popped up, and the Port Forward wizard pretended to be succeeded.
8. Close the port-forward window in step7, and revisit it for the 2nd time now, we can see from the UI that port forwarding is ended.
9. curl http://127.0.0.1/8080, still return string "I'm A" in the result HTML file, this means the port forward in step4 is still taking effect, and the attempt in step 6 had failed, this is the expected result here.
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3
>
> No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Xia Zhao (JIRA)
Xia Zhao created JBIDE-21849:
--------------------------------
Summary: [AP] Not able to list services under a project after login to AP
Key: JBIDE-21849
URL: https://issues.jboss.org/browse/JBIDE-21849
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
OS: Fedora 17 & MAC OS 10
Reporter: Xia Zhao
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.CR1
No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month