[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
[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
[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
[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