April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24175) Command to tune the health checks (readiness and liveness)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24175?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24175: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Command to tune the health checks (readiness and liveness) > ---------------------------------------------------------- > > Key: JBIDE-24175 > URL: https://issues.jboss.org/browse/JBIDE-24175 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24178) When deploying user should be able to tune autoscaling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24178?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24178: ------------------------------------- Fix Version/s: 4.5.0.AM1 > When deploying user should be able to tune autoscaling > ------------------------------------------------------ > > Key: JBIDE-24178 > URL: https://issues.jboss.org/browse/JBIDE-24178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24176) When deploying user should be able to tune storage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24176?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24176: ------------------------------------- Fix Version/s: 4.5.0.AM1 > When deploying user should be able to tune storage > -------------------------------------------------- > > Key: JBIDE-24176 > URL: https://issues.jboss.org/browse/JBIDE-24176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > Note: this is not yet supported by OCP Web Console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24145) Command to tune memory requirements for a deployment

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24145?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24145: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Command to tune memory requirements for a deployment > ---------------------------------------------------- > > Key: JBIDE-24145 > URL: https://issues.jboss.org/browse/JBIDE-24145 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24141: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component > ------------------------------------------------------------ > > Key: JBIDE-24141 > URL: https://issues.jboss.org/browse/JBIDE-24141 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.Final > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:* > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2 > {code} > {code} > Failed > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > Failing for the past 2 builds (Since Unstable#74 ) > Took 0.15 sec. > add description > Error Message > Expected: <6> > but: was <10> > Stacktrace > java.lang.AssertionError: > Expected: <6> > but: was <10> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.junit.Assert.assertThat(Assert.java:923) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23422: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.4.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23861) CDI support is not enabled automatically with JBoss AS 7.1 runtime

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23861?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23861: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > CDI support is not enabled automatically with JBoss AS 7.1 runtime > ------------------------------------------------------------------ > > Key: JBIDE-23861 > URL: https://issues.jboss.org/browse/JBIDE-23861 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.4.3.AM2 > Environment: Devstudio AM2-v20170127-1155-B6970, Java 1.8.0_111-b15, JBoss AS 7.1.1.Final > Reporter: Lukáš Valach > Priority: Minor > Fix For: 4.4.4.Final > > Attachments: CdiSupport1.png, CdiSupport2.png > > > When I create a Dynamic Web Project or EJB Project the CDI support should be enabled automatically. It works properly when I have JBoss EAP 7 or Wildfly 10 as target platform, but it doesn't work with JBoss AS 7.1. > There is no error in the log, there is only warning in the problems view. > ??JBoss Tools Knowledge Base probelm: Nature/Builder is not installed on project. Use quick fix to enable %KB_REQUIRED_FOR_FACET and Faceted (test environment only) Content Assistant and Validation.?? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23869: ------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.4.4.Final > > Attachments: image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22773: ------------------------------------------ Created an upstream issue: https://github.com/openshift/origin/issues/13864. The errors happens when rsyncing from pod to the local. Created ROOT.war seems unaccessible at all (see the details in upstream issue description). Tested both in user's directory and in other sub-directories of the c:/ drive, with admin permissions and without. > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.4.4.Final > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-24291: --------------------------------------- Summary: Improve initial loading of JMX Connection tree Key: JBIDE-24291 URL: https://issues.jboss.org/browse/JBIDE-24291 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: jmx Affects Versions: 4.4.4.AM2 Reporter: Aurélien Pupier JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me) It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server. For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 April 2017