[JBoss JIRA] (JBIDE-23565) Add mechanism for detecting if internal browser is able to communicate with eclipse.
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23565?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23565:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> Add mechanism for detecting if internal browser is able to communicate with eclipse.
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-23565
> URL: https://issues.jboss.org/browse/JBIDE-23565
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.4.2.Final
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.5.x
>
>
> Context: I have fresh installation of Fedora 25 (KDE spin). In that installation, webkitgtk3 is not installed by default. As a result of this, Central in eclipse is behaving exactly the same as in normal web browser (only some forge example is displayed (no archetypes) and when this example is clicked on, popup (this one: https://github.com/jbosstools/jbosstools-central-webpage/blob/master/src/...) pops up instead of wizard). This leaves Central unusable.
> Installing webkitgtk3 solved this issue, but it would be great if Central had some mechanism for detecting this and in case it is not able to communicate with eclipse instance it could throw recommendation for user to check if he has webkitgtk3 installed.
> Maybe also document this requirement?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24340:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, integration-tests, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.x
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * log into openshift
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24386) Improve Error Reporting - org.jboss.tools.jmx.jolokia
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24386?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24386:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> Improve Error Reporting - org.jboss.tools.jmx.jolokia
> -----------------------------------------------------
>
> Key: JBIDE-24386
> URL: https://issues.jboss.org/browse/JBIDE-24386
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.4.AM3
> Environment: DevStudio 10.4.0.AM3
> jolokia-jvm-1.3.6-agent.jar
> Reporter: Tomáš Sedmík
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: jolokia.webm
>
>
> I was unable to connect to a Camel Route via Jolokia. I got the following error in Error Log (see attached video). I have to enable _Do NOT verify SSL Certificates_ in connection details to solve this problem.
> The error log could be more descriptive and could notify users where might be a problem.
> {code}
> eclipse.buildId=10.4.0.GA-v20170427-0526-B16
> java.version=1.8.0_111
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product -pluginCustomization /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CR1/resources/pluginCustomization.ini
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -pluginCustomization /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CR1/resources/pluginCustomization.ini -data /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CR1/target/tmp -clean
> org.jboss.tools.jmx.core
> Error
> Tue May 02 19:14:31 CEST 2017
> Error executing JMX request.
> java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Not Found
> at org.jboss.tools.jmx.jolokia.internal.connection.JolokiaMBeanServerConnection.queryNames(JolokiaMBeanServerConnection.java:140)
> at org.jboss.tools.jmx.core.tree.NodeUtils$1.run(NodeUtils.java:58)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.run(JolokiaConnectionWrapper.java:335)
> at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:54)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.loadRoot(JolokiaConnectionWrapper.java:141)
> at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:192)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Not Found
> at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jboss.tools.jmx.jolokia.internal.connection.JolokiaMBeanServerConnection.queryNames(JolokiaMBeanServerConnection.java:135)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22605:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> Remote server with fs operations sometimes cannot be stopped
> ------------------------------------------------------------
>
> Key: JBIDE-22605
> URL: https://issues.jboss.org/browse/JBIDE-22605
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work.
> In one instance of Eclipse, stopping such server didn't work.
> But then I tried in devstudio and it worked, so I assumed it was some glitch.
> But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA.
> From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine.
> One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup:
> {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code}
> (Let me know if you want an additional JIRA for that.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months