October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23283) NullPointerException in ControllableServerBehavior.setModulesStopped

by Automated Error Reporting Bot (JIRA)

Automated Error Reporting Bot created JBIDE-23283: ----------------------------------------------------- Summary: NullPointerException in ControllableServerBehavior.setModulesStopped Key: JBIDE-23283 URL: https://issues.jboss.org/browse/JBIDE-23283 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Reporter: Automated Error Reporting Bot The following problem was reported via the automated error reporting: Message: Problems occurred when invoking code from plug-in: "org.eclipse.debug.core". {noformat} java.lang.NullPointerException: null at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setModulesStopped(ControllableServerBehavior.java:220) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setModulesStopped(ControllableServerBehavior.java:227) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStopped(ControllableServerBehavior.java:216) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ProcessTerminatedDebugListener.handleProcessTerminatedEvent(ProcessTerminatedDebugListener.java:74) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ProcessTerminatedDebugListener.handleDebugEvents(ProcessTerminatedDebugListener.java:48) at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java:1161) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java:1197) at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:441) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} Bundles: | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160901-1938 | | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160901-1938 | | org.eclipse.debug.core | 3.10.0.v20150303-1130 | 3.11.0.v20160914-0904 | | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 | | org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Final-v20150924-2222-B46 | 3.2.1.v20160711-1757 | Operating Systems: | Linux | 3.13.0 | 4.4.21 | | MacOSX | 10.11.4 | 10.11.6 | | Windows | 6.1.0 | 10.0.0 | The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571778bbe4b032f683...] for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23210) Application wizard: builder image application are created all the time for first project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23210: ------------------------------------------ merged https://github.com/jbosstools/jbosstools-openshift/pull/1333 into master > Application wizard: builder image application are created all the time for first project > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23210 > URL: https://issues.jboss.org/browse/JBIDE-23210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: # openshift version > openshift v3.2.1.15 > kubernetes v1.2.0-36-g4a3f9c5 > etcd 2.2.5 > Reporter: Peng Li > Assignee: Andre Dietisheim > Labels: application_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png > > > Creation of an application based on builder image ignore preselected project and is created on first project all the time. This is happening only for builder images. Template based application are not affected by this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23282) Upgrade Forge Runtime to 3.3.2.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23282?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-23282. ------------------------------------- Resolution: Done Labels: new_and_noteworthy (was: ) > Upgrade Forge Runtime to 3.3.2.Final > ------------------------------------ > > Key: JBIDE-23282 > URL: https://issues.jboss.org/browse/JBIDE-23282 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.2.AM1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23157: ------------------------------------ fix jiralint so common and foundation are in assparta, and jst is in californication > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, foundation, jst > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM2 > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23282) Upgrade Forge Runtime to 3.3.2.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-23282: --------------------------------------- Summary: Upgrade Forge Runtime to 3.3.2.Final Key: JBIDE-23282 URL: https://issues.jboss.org/browse/JBIDE-23282 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.4.2.AM1 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.2.AM2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov edited comment on JBIDE-22803 at 10/3/16 12:08 PM: -------------------------------------------------------------------- [~jcantrill] [~adietish] [~jeffmaury] tried to find out how to get the version of the OpenShift Origin Server, but found nothing implemented yes and it seems not-so-easy-to-solve problem. I tried watching projects with [the latest v1.3.0|https://github.com/openshift/origin/releases/tag/v1.3.0] and it works! That's great! I also tried with https://console.engint.openshift.com and the version of OS installed there doesn't support this feature (in spite of OpenShift Master: v3.2.1.15-8-gc402626). I tried to debug and what i notices is that org.jboss.tools.openshift.internal.core.WatchManager.WatchListener error method is called without stopping (because it tries to restart(); all the time). And i have an idea how solve the question of whether the feature is available or not. If we look at response variable of com.openshift.internal.restclient.okhttp.WatchClient.WatchEndpoint.onFailure(IOException, Response) then we'll see the following: Response{protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} I understand that it's a dirty hack, but we can retrieve this url (by response.request().url()), find its _projects?watch=true_ part and analyze the code. And, for example, if this response repeats, say, 3 times, then we understand that the feature is not available. I see how cheaty it is, but it should work was (Author: dbocharov): [~jcantrill] [~adietish] [~jeffmaury] tried to find out how to get the version of the OpenShift Origin Server, but found nothing implemented yes and it seems not-so-easy-to-solve problem. I tried watching projects with [the latest v1.3.0|https://github.com/openshift/origin/releases/tag/v1.3.0] and it works! That's great! I also tried with https://console.engint.openshift.com and the version of OS installed there doesn't support this feature (in spite of OpenShift Master: v3.2.1.15-8-gc402626). I tried to debug and what i notices is that org.jboss.tools.openshift.internal.core.WatchManager.WatchListener error method is called without stopping (because it tries to restart(); all the time). And i have an idea how solve the question of whether the feature is available or not. If we look at response variable of com.openshift.internal.restclient.okhttp.WatchClient.WatchEndpoint.onFailure(IOException, Response) then we'll see the following: Response{protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} I understand that it's a dirty hack, but we can retrieve this url (by response.request().url()) and analyze the code. And, for example, if this response repeats, say, 3 times, then we understand that the feature is not available. I see how cheaty it is, but it should work > When OS projects are created and deleted, seems Openshift explorer restores non existing values > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23246) OpenShift New and Noteworthy for 4.4.2.AM1

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23246?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23246. --------------------------------- lgtm, closing. > OpenShift New and Noteworthy for 4.4.2.AM1 > ------------------------------------------ > > Key: JBIDE-23246 > URL: https://issues.jboss.org/browse/JBIDE-23246 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.2.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23238) Create New and Noteworthy for 4.4.2.AM1

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23238?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23238. --------------------------------- All sub-tasks have been resolved and closed. Closing this one as well. > Create New and Noteworthy for 4.4.2.AM1 > --------------------------------------- > > Key: JBIDE-23238 > URL: https://issues.jboss.org/browse/JBIDE-23238 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.2.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23246) OpenShift New and Noteworthy for 4.4.2.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23246?page=com.atlassian.jira.plugi... ] Jeff MAURY resolved JBIDE-23246. -------------------------------- Resolution: Done > OpenShift New and Noteworthy for 4.4.2.AM1 > ------------------------------------------ > > Key: JBIDE-23246 > URL: https://issues.jboss.org/browse/JBIDE-23246 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.2.AM1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23152) NPE when deploying image with ENV with no value

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23152?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23152: ------------------------------------------ could reproduce and verify the fix with the 2nd scenarion. merged PR into master. > NPE when deploying image with ENV with no value > ----------------------------------------------- > > Key: JBIDE-23152 > URL: https://issues.jboss.org/browse/JBIDE-23152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Dockerfile > > > EXEC: first deploy jboss-eap64-openshift builder image > ASSERT: wait until deployment is finished > EXEC: delete the deployment > EXEC: deploy the image that has been produced (172.30.159.75:5000/ddd/jboss-eap64-openshift:latest if my project was ddd) > ASSERT: error dialog is shown NPE is generated because image has one or several env variables with no value (XXXX=) > As this first scenario seems to be valid only if you're working with CDK2.2 and no proxy set, here is a scenario valid for all versions of CDK: > ASSERT: have a Docker file with an empty ENV value. You can use https://github.com/redhat-helloworld-msa/aloha and edit the Docker file and add the following statement: > {quote}ENV NOVALUE ""{quote} > EXEC: build the Docker image on the CDK Docker connection. If you use aloha (https://github.com/redhat-helloworld-msa/aloha), then you must beforehand run the "mvn package" command to get binary artifacts being produced. Select the Dockerfile, click *_Run As -> Docker Image Build_*, select the CDK Docker connection and give *_msa/aloha:1_* as image name > ASSERT: your Docker image has been generated > EXEC: from the Openshift explorer, select the *_Deploy Docker Image_*, then select the CDK Docker Connection, then click on *_Browse_* and select the *_msa/aloha:1_* image, then click on the Next button > ASSERT: you should get an error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016