[JBoss JIRA] (JBIDE-23283) NullPointerException in ControllableServerBehavior.setModulesStopped
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23283?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23283.
---------------------------------
> 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
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
>
> 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-23297) [AERI] NullPointerException in StandardFileSystemPublishController.moduleToString
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23297?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23297.
---------------------------------
> [AERI] NullPointerException in StandardFileSystemPublishController.moduleToString
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23297
> URL: https://issues.jboss.org/browse/JBIDE-23297
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Could not publish to the server.
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.moduleToString(StandardFileSystemPublishController.java:287)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:300)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |
> | org.eclipse.wst.server.core | 1.8.100.v201605201456 | 1.8.100.v201605201456 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.1.v20160711-1757 | 3.2.1.v20160711-1757 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57e03b3be4b06c2b2e...] 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-23296) NullPointerException in LocalJBoss7ServerRuntime.getBaseDirectory
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23296?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23296.
---------------------------------
> NullPointerException in LocalJBoss7ServerRuntime.getBaseDirectory
> -----------------------------------------------------------------
>
> Key: JBIDE-23296
> URL: https://issues.jboss.org/browse/JBIDE-23296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7ServerRuntime.getBaseDirectory(LocalJBoss7ServerRuntime.java:96)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7ServerRuntime.getConfigLocation(LocalJBoss7ServerRuntime.java:121)
> at org.jboss.ide.eclipse.as.core.server.internal.LocalJBossServerRuntime.getConfigLocationFullPath(LocalJBossServerRuntime.java:130)
> at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.handleConfigDir(ConfigNameResolver.java:157)
> at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.resolveValue(ConfigNameResolver.java:127)
> at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.resolveValue(ConfigNameResolver.java:116)
> at org.eclipse.core.internal.variables.DynamicVariable.getValue(DynamicVariable.java:56)
> at org.eclipse.core.internal.variables.StringSubstitutionEngine.resolve(StringSubstitutionEngine.java:269)
> at org.eclipse.core.internal.variables.StringSubstitutionEngine.substitute(StringSubstitutionEngine.java:192)
> at org.eclipse.core.internal.variables.StringSubstitutionEngine.performStringSubstitution(StringSubstitutionEngine.java:87)
> at org.jboss.ide.eclipse.as.core.resolvers.RuntimeVariableResolver.resolve(RuntimeVariableResolver.java:74)
> at org.jboss.tools.foundation.core.expressions.ExpressionResolver.resolveVariable(ExpressionResolver.java:304)
> at org.jboss.tools.foundation.core.expressions.ExpressionResolver.resolve(ExpressionResolver.java:229)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.getReplacedString(XPathQuery.java:105)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.setEffectiveBaseDir(XPathQuery.java:112)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.<init>(XPathQuery.java:97)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.addQueriesToCategoryFromDefaultFile(XPathModel.java:366)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.loadDefaultPortQueries(XPathModel.java:338)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.handleAddJBossXPaths(XPathModel.java:115)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.access$1(XPathModel.java:114)
> at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:101)
> 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.v20160509-0411 |
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.core.variables | 3.2.800.v20130819-1716 | 3.3.0.v20160419-1720 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui.navigator | 3.6.100.v20160518-1929 | 3.6.100.v20160518-1929 |
> | org.jboss.ide.eclipse.as.core | 3.1.1.Final-v20160409-0826-B118 | 3.2.0.Final-v20160614-2020-B9 |
> | org.jboss.ide.eclipse.as.ui | 3.2.0.Final-v20160614-2020-B9 | 3.2.0.Final-v20160614-2020-B9 |
> | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.3.0.Final-v20160610-1533-B7 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57cd9a2fe4b0fd7621...] 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-23358) OpenShift Explorer: Pod status is not reflecting reality
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23358:
----------------------------------
Description:
When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods".
!pod_status.png!
was:When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods".
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods".
> !pod_status.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23358:
----------------------------------
Attachment: pod_status.png
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods".
> !pod_status.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23358:
----------------------------------
Description:
When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.
!pod_status.png!
was:
When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods".
!pod_status.png!
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: pod_status.png
>
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.
> !pod_status.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23358:
----------------------------------
Labels: openshift_v3 (was: )
> OpenShift Explorer: Pod status is not reflecting reality
> --------------------------------------------------------
>
> Key: JBIDE-23358
> URL: https://issues.jboss.org/browse/JBIDE-23358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: openshift_v3
>
> When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23166) MBean Stubs New Wizard cannot be open
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23166?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23166.
---------------------------------
OK, thanks for the explanation. Closing.
> MBean Stubs New Wizard cannot be open
> -------------------------------------
>
> Key: JBIDE-23166
> URL: https://issues.jboss.org/browse/JBIDE-23166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.1.Final
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.2.AM2
>
> Attachments: mbinstubs.gif, screenshot-1.png
>
>
> It just throws exception below
> {code}The selected wizard could not be started.
> Plug-in org.jboss.ide.eclipse.as.ui.mbeans was unable to load class org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard.
> org.jboss.ide.eclipse.as.ui.mbeans.wizards.NewMBeanWizard cannot be found by org.jboss.ide.eclipse.as.ui.mbeans_3.2.1.v20160607-2122{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months