September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23130) JMX connection to remote server does not work (fs operations, runtime)

by Martin Malina (JIRA)

Martin Malina created JBIDE-23130: ------------------------------------- Summary: JMX connection to remote server does not work (fs operations, runtime) Key: JBIDE-23130 URL: https://issues.jboss.org/browse/JBIDE-23130 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.4.1.Final Reporter: Martin Malina This is basically a follow up of JBIDE-22741. It turns out even if I have a local runtime, jmx connection to a remote fs server still doesn't work for me. 1. Set up a remote WildFly 8.2 server over ssh (use fs operations, local runtime) 2. Make sure the user is set up correctly both on the server and in server editor in Eclipse 3. Start the remote server 4. Try to connect to the server in JMX Navigator You'll get this in the error log view: {code} Error connecting to jmx for server WildFly 8.2 marvin org.jboss.tools.jmx.core.JMXException: There was an error connecting to WildFly 8.2 marvin via JMX. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com launch arguments at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:98) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:211) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:341) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:335) at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:232) at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) ... 7 more {code} {code} There was an error connecting to WildFly 8.2 marvin via JMX. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com launch arguments java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:272) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:253) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:351) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:335) at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:232) at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:211) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:341) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} So it tells me that I need to expose the managerment port. But we never did that for fs operations, no? And indeed it's not exposed: {code} 2810 pts/1 Sl 0:06 \_ java -Dprogram.name=JBossTools: WildFly 8.2 marvin -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log -Dlogging.configuration=file:/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties -Djboss.home.dir=/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final -Dorg.jboss.logmanager.nocolor=true -jar /home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp /home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules -jaxpmodule javax.xml.jaxp-provider -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/home/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone {code} But even if I do expose the management port, it still won't work - then I hit JBIDE-20108 . Anyway, I think we didn't need to expose the management port in the past. Or did we? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22725) Provided wrong credentials, CDK adapter creates openshift connection with a strange IP

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22725: ------------------------------------ Yes, I can reproduce after a vagrant destroy (with CDK2.2RC3) > Provided wrong credentials, CDK adapter creates openshift connection with a strange IP > -------------------------------------------------------------------------------------- > > Key: JBIDE-22725 > URL: https://issues.jboss.org/browse/JBIDE-22725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM1 > Reporter: Martin Malina > Fix For: 4.4.x > > > When you start CDK with wrong credentials, service manager will return this strange IP: > {code} > # docker env: > # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > # Set the following environment variables to enable access to the docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.0.2.15:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.21 > # run following command to configure your shell: > # eval "$(vagrant service-manager env)" > {code} > This has been reported upstream here: > https://github.com/projectatomic/vagrant-service-manager/issues/299 > Let's use this JIRA to track the upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23065) test failure in org.jboss.tools.jsf.vpe.jsf.test

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23065?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23065. -------------------------------- Verified in 10.1.0.GA. > test failure in org.jboss.tools.jsf.vpe.jsf.test > ------------------------------------------------- > > Key: JBIDE-23065 > URL: https://issues.jboss.org/browse/JBIDE-23065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-templates > Affects Versions: 4.4.1.AM3 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.1.Final > > > Need to remove the following tests - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Those tests are also failing locally -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23125) CDK server adapter: NPE when trying to find cdk connection

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23125?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23125: ------------------------------------ Hi. I was trying to reproduce it today, but with no luck. I have AERI configured to automatically send everything and I probably missed this report. Anyway... I can see that I'm the only reporter of this issue. My suggestion is to leave this JIRA open for a little longer and then check in AERI, whether somebody else run into this issue. > CDK server adapter: NPE when trying to find cdk connection > ---------------------------------------------------------- > > Key: JBIDE-23125 > URL: https://issues.jboss.org/browse/JBIDE-23125 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > > This was automatically reproted in aeri https://redhat.ctrlflow.com/reviewers#!/problems/57c68f6be4b0fd7621ccda10 > {code} > Bundle: org.eclipse.jface 3.12.0.v20160518-1929 > Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface". > Exception: > java.lang.NullPointerException: null > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:39) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:182) > at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:198) > at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144) > at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1229) > at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:463) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1258) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:405) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23046) If call to vagrant service-manager times out, openshift / docker connect should still try to be created

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23046?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23046. --------------------------------- It would be really nice to be able to verify this, but currently it seems nobody can reproduce the timeout issue - JBIDE-22818 and CDK-4 . So I don't see how I could verify this. [~rob.stryker], do you have a suggestion? For now, I'm closing this. > If call to vagrant service-manager times out, openshift / docker connect should still try to be created > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23046 > URL: https://issues.jboss.org/browse/JBIDE-23046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections. > The code should attempt to survive the error and continue along. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-410) Wrong message when adding duplicate TCP connection [EBZ#500910]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-410: --------------------------------------- Summary: Wrong message when adding duplicate TCP connection [EBZ#500910] Key: ERT-410 URL: https://issues.jboss.org/browse/ERT-410 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Priority: Trivial Created attachment 263985 Wrong error message TCP connection When I am trying to add duplicate TCP connection, an error message is shown: " A connection with the same Unix socket path already exists", but it should be different, for example: "A connection with the same TCP address already exists" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22881) snapshot dependency found in aerogear

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22881?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-22881. ------------------------------ > snapshot dependency found in aerogear > ------------------------------------- > > Key: JBIDE-22881 > URL: https://issues.jboss.org/browse/JBIDE-22881 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.4.1.Final > > > {code} > [ERROR] Found property thym.version = 2.0.0-SNAPSHOT-201605071736 > [INFO] Found BUILD_ALIAS = AM3 (for buildAliasSearch = AM3|Final|GA) > [WARNING] Rule 0: org.jboss.tools.releng.NoSnapshotsAllowed failed with message: > When BUILD_ALIAS (AM3) matches /AM3|Final|GA/, cannot include SNAPSHOT dependencies. > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22880) List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22880?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22880. --------------------------------- It works as expected for me now, so I'm closing this JIRA. Feel free to reopen. Verified in devstudio-10.1.0.GA-v20160902-1725-B43-installer-eap.jar > List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22880 > URL: https://issues.jboss.org/browse/JBIDE-22880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > Attachments: test-projects.zip > > > It is impossible to select "filter by" dropdown or press "Refresh Table" on the deployment tab of ServerEditor in JBoss Developer Studio when anything is deployed. I think it should be possible to change filter configuration but do not edit the table itself. Otherwise, both "Refresh" button and some of filter options becomes useless. See Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22880) List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22880?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22880: --------------------------------------- [~mkalkov], you can verify the fix either in JBoss Tools 4.4.1.Final build in staging: http://download.jboss.org/jbosstools/neon/staging/updates/ Or if you prefer Red Hat JBoss Developer Studio, you can use this staging build: https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... > List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22880 > URL: https://issues.jboss.org/browse/JBIDE-22880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final, 4.4.0.Final > Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. > Reporter: Mikhail Kalkov > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > Attachments: test-projects.zip > > > It is impossible to select "filter by" dropdown or press "Refresh Table" on the deployment tab of ServerEditor in JBoss Developer Studio when anything is deployed. I think it should be possible to change filter configuration but do not edit the table itself. Otherwise, both "Refresh" button and some of filter options becomes useless. See Steps to Reproduce for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19388) Investigate necessity of runtime for local+fs+externally managed server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19388?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19388. --------------------------------- > Investigate necessity of runtime for local+fs+externally managed server > ----------------------------------------------------------------------- > > Key: JBIDE-19388 > URL: https://issues.jboss.org/browse/JBIDE-19388 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > Is a runtime necessary for local server / filesystem based deployment / extenrally managed? How can this be improved? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016