[jbosstools-issues] [JBoss JIRA] (JBIDE-24025) AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder
[
https://issues.jboss.org/browse/JBIDE-24025?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-24025:
------------------------------------------
I see the following code as possible culprit:
{code:title=ExpressServerUtils}
public static String getDeployFolder(IServerAttributes attributes) {
IApplication application = null;
try {
application = getApplication(attributes);
} catch (GetApplicationException e) {
Throwable cause = e.getCause();
if(cause != null) {
ExpressCoreActivator.pluginLog().logError(e.getMessage(), e);
}
//TODO Consider if this method should throw GetApplicationException.
//For now its behavior is left as before because there are nor reports of its failure.
}
return getDeployFolder(attributes, application);
}
{code}
It catches the exception but then goes on to get the deploy folder anyhow using null as
application parameter.
AssertionFailedException in
ExpressServerUtils.getDefaultDeployFolder
---------------------------------------------------------------------
Key: JBIDE-24025
URL: https://issues.jboss.org/browse/JBIDE-24025
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.3.Final
Reporter: Automated Error Reporting Bot
Labels: openshift_v2
Fix For: 4.4.4.AM1
The following problem was reported via the automated error reporting:
Message: Unhandled event loop exception
org.eclipse.core.runtime.AssertionFailedException: null argument:
at
org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDefaultDeployFolder(ExpressServerUtils.java:292)
at
org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:264)
at
org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:260)
at
org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection.initWidgets(ExpressServerEditorSection.java:122)
at
org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection$1.run(ExpressServerEditorSection.java:103)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
Bundles:
| org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
| org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.1.v20160907-0248 |
| org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.9.0.v201610211907 |
| org.jboss.tools.openshift.express.core | 3.1.0.Final-v20160414-0041-B272 |
3.3.2.v20170119-1710 |
| org.jboss.tools.openshift.express.ui | 3.1.0.Final-v20160414-0041-B272 |
3.3.1.v20161003-1104 |
Operating Systems:
| Linux | 3.13.0 | 3.13.0 |
| Windows | 6.1.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit
https://aer.ctrlflow.com/redhat/reviewers/#!/problems/56df0c0fe4b0e0c18a6... for the
latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)