July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-17181. ----------------------------------- Resolution: Cannot Reproduce Bug I cannot reproduce this now. But it turns out that currently remote connection to a server via jmx does not work at all: JBIDE-22741 > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.AM2 > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17181. --------------------------------- > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.1.AM2 > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Martin Malina (JIRA)

Martin Malina created JBIDE-22741: ------------------------------------- Summary: JMX connection to remote server does not work (fs operations) Key: JBIDE-22741 URL: https://issues.jboss.org/browse/JBIDE-22741 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.4.1.AM2 Reporter: Martin Malina Assignee: Rob Stryker I wanted to replicate JBIDE-17181 today. And I cannot replicate that problem. But I noticed that jmx connection to a remote wf 8.2 with fs operations doesn't seem to work. I thought there was a long standing issue open for this already, but it turns out this other JIRA is for management mode: JBIDE-20108 So it seems that neither works right now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22738) Image registry URL becomes null when going between Connection and Deploy pages on Deploy image to OS wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22738?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22738: ----------------------------------------------- It is possible in ConnectionWizardPageModel.saveConnection() after calling update() retrieve the shared connection {code} connection = ConnectionsRegistrySingleton.getInstance().getByUrl(ConnectionURL.forConnection(connection)); {code} However, all wizards listening for connection change now notice only instance change when they are notified after connect() with wizard.setConnection(connection); That should be addressed in some way or maybe ignored depending on wizard. > Image registry URL becomes null when going between Connection and Deploy pages on Deploy image to OS wizard > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22738 > URL: https://issues.jboss.org/browse/JBIDE-22738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Attachments: WAY1.webm, WAY2.webm > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21606: --------------------------------------- Basically you just changed the default exec env from java 6 to java 7 for EAP 6.1+, right? So the use case that described in the jira description will still not work. :sad panda: > Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6] > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3966) Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3966?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3966: ------------------------------- Story Points: (was: 1) > Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning > --------------------------------------------------------------------------------------------- > > Key: JBDS-3966 > URL: https://issues.jboss.org/browse/JBDS-3966 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: platform-installer > Reporter: Len DiMaggio > Fix For: 10.1.0.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3966) Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3966?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3966: ------------------------------- Story Points: 1 (was: 100) > Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning > --------------------------------------------------------------------------------------------- > > Key: JBDS-3966 > URL: https://issues.jboss.org/browse/JBDS-3966 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: platform-installer > Reporter: Len DiMaggio > Fix For: 10.1.0.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22737) No connectors found for Central

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22737?page=com.atlassian.jira.plugi... ] Jan Richter reassigned JBIDE-22737: ----------------------------------- Assignee: Nick Boldt > No connectors found for Central > ------------------------------- > > Key: JBIDE-22737 > URL: https://issues.jboss.org/browse/JBIDE-22737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Critical > > Upon devstudio start there are following errors in error log and software update tab in central is not working (no connectors found): > {code} > No URL set for discovery catalog. Property jboss.discovery.directory.url is missing! > An exception stack trace is not available. > {code} > {code} > All attempts to discover connectors have failed > An exception stack trace is not available. > Failed to get connectors from RemoteProxyWizardDiscoveryStrategy > java.lang.NullPointerException > at java.net.URI$Parser.parse(URI.java:3042) > at java.net.URI.<init>(URI.java:588) > at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90) > at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117) > at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:68) > at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:47) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3966) Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3966?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3966: ------------------------------- Story Points: 100 > Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning > --------------------------------------------------------------------------------------------- > > Key: JBDS-3966 > URL: https://issues.jboss.org/browse/JBDS-3966 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: platform-installer > Reporter: Len DiMaggio > Fix For: 10.1.0.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3966) Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3966: ---------------------------------- Summary: Test subtask - please disregard - being used only to test use of sub-tasks in sprint planning Key: JBDS-3966 URL: https://issues.jboss.org/browse/JBDS-3966 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Reporter: Len DiMaggio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016