January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25672) Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25672?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25672: ------------------------------- Fix Version/s: 4.5.3.AM2 (was: 4.5.3.AM1) > Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com) > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25672 > URL: https://issues.jboss.org/browse/JBIDE-25672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.3.AM2 > > Attachments: image-2018-01-29-15-48-29-101.png > > > # ASSERT: have a connection to open.paas.redhat.com > # EXEC: create a new app based on the "s2i-spring-boot-camel-xml" template. Have the project imported to your workspace and the server adapter created > # ASSERT: a server adapter "s2i-spring-boot-camel-xml" is created > # EXEC: wait for the adapter to get "[started]" > Result: > After some waiting time the adapter throws the following error: > !image-2018-01-29-15-48-29-101.png! > In the Eclipse log you find the following: > {code} > !MESSAGE Could not launch server s2i-spring-boot-camel-xml (DeploymentConfig) at OpenShift 3 (open.paas.redhat.com) > !STACK 0 > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) > at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) > at org.jboss.tools.openshift.internal.core.server.debug.DebugContext.<init>(DebugContext.java:64) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.createDebugContext(OpenShiftLaunchController.java:199) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:93) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25674: ---------------------------------- Assignee: Rob Stryker > NPE in JolokiaConnectionWrapper.extractStatus > --------------------------------------------- > > Key: JBIDE-25674 > URL: https://issues.jboss.org/browse/JBIDE-25674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.3.AM2 > > > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > 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:56) > {noformat} > I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable" > in this case the "response" is null > 2 possibilities: > - it is normal that it is null in this case Jboss Tools need to handle this case > - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25674: ------------------------------- Fix Version/s: 4.5.3.AM2 (was: 4.5.3.AM1) > NPE in JolokiaConnectionWrapper.extractStatus > --------------------------------------------- > > Key: JBIDE-25674 > URL: https://issues.jboss.org/browse/JBIDE-25674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Aurélien Pupier > Fix For: 4.5.3.AM2 > > > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > 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:56) > {noformat} > I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable" > in this case the "response" is null > 2 possibilities: > - it is normal that it is null in this case Jboss Tools need to handle this case > - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25677) Timers are incorrectly managed in server adapter

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25677: ---------------------------------- Summary: Timers are incorrectly managed in server adapter Key: JBIDE-25677 URL: https://issues.jboss.org/browse/JBIDE-25677 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.2.Final Reporter: Jeff MAURY Fix For: 4.5.x Timers are incorrectly managed in OpenShift server adapter. I tried to create a NodeJS server adapter on OpenShift Online Starter. As the first rsync is long (thanks to .npm and node_modules), it may take more than 5mns as OpenShift Online Starter is resource limited. I think we should rather monitor the activity of the rsync operation (through messages) and set a timer related to this activity. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1202) Verify BPMN2 modeller with Devstudio IS 11.2.0.CR1

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1202?page=com.atlassian.jira.plugin... ] Andrej Podhradsky resolved JBTIS-1202. -------------------------------------- Resolution: Done Verified with Devstudio IS 11.2.0.CR1 > Verify BPMN2 modeller with Devstudio IS 11.2.0.CR1 > -------------------------------------------------- > > Key: JBTIS-1202 > URL: https://issues.jboss.org/browse/JBTIS-1202 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 11.2.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 11.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25438. --------------------------------- All pointed tasks were implemented, some of problematic related issues were resolved, some was not yet. Work will continue in those jiras. > Refactor CDK itests to be more stable against CDK starts that fail sometimes > ---------------------------------------------------------------------------- > > Key: JBIDE-25438 > URL: https://issues.jboss.org/browse/JBIDE-25438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM1 > > > Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. > * repair discovery itests > * finish adding of mocking cdk binaries in unsupported cdk versions > * update suites to run faster test classes > * remove deprecated test cases > * think of skipping registration and adding one test case that will start cdk with registration > * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations > Issues to be addressed or incidents that cause fail of job run: > * CDK-216 > * JBIDE-25443 > * https://status.redhat.com/incidents/s7tzh47440f5 > * JBIDE-25446 > * CDK-220 (cdk-3.3.0) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25297) Improve CDK itests so that user do not need to have all CDK versions downloaded himself

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25297?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25297. --------------------------------- > Improve CDK itests so that user do not need to have all CDK versions downloaded himself > --------------------------------------------------------------------------------------- > > Key: JBIDE-25297 > URL: https://issues.jboss.org/browse/JBIDE-25297 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk > Fix For: 4.5.3.AM1 > > > Add mock files that would substitute CDK 2.x Vagrantfile and CDK 3.1.1 binary for purposes of testing UI. These files will be placed in project path in resources/cdk-files. > Let user to pass his vagrant file and cdk-3.1.1 binary path via agrument -Dvagrantfile and -Dminishift in cases where he needs to do so. This argument's values will have priority over files from resources folder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1204) List of fixed issues in BPMN2 1.4.2

by Andrej Podhradsky (JIRA)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1204) List of fixed issues in BPMN2 1.4.2

by Andrej Podhradsky (JIRA)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1204) List of fixed issues in BPMN2 1.4.2

by Andrej Podhradsky (JIRA)

8 years, 1 month

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 January 2018