[JBoss JIRA] (JBIDE-25862) Starting of devstudio introduce ArrayIndexOutOfBoundsException in Error Log from org.jboss.tools.jmx.jvmmonitor.tools
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25862:
-------------------------------------
Summary: Starting of devstudio introduce ArrayIndexOutOfBoundsException in Error Log from org.jboss.tools.jmx.jvmmonitor.tools
Key: JBIDE-25862
URL: https://issues.jboss.org/browse/JBIDE-25862
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.5.3.AM3
Reporter: Ondrej Dockal
{code:java}
eclipse.buildId=11.3.0.AM3-v20180322-1027-B2194
java.version=1.8.0_161
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.jmx.jvmmonitor.tools
Error
Mon Mar 26 23:57:42 CEST 2018
Update timer canceled.
java.lang.ArrayIndexOutOfBoundsException: 0
at org.jboss.tools.common.jdt.debug.JavaUtilities.getMajorMinor(JavaUtilities.java:55)
at org.jboss.tools.common.jdt.debug.JavaUtilities.isJigsawRunning(JavaUtilities.java:33)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:110)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:101)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:69)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:60)
at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:181)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25772) java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25772?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25772:
---------------------------------------
My config.json from ./minishift folder was corrupted and I got this on starting devstudio in new workspace:
Error Log showed error with message:
{code}
Error parsing /home/odockal/.minishift/config/config.json
{code}
and stack trace...
{code}
java.lang.IllegalArgumentException: Invalid character: b
at org.jboss.dmr.JSONParserImpl.invalid(JSONParserImpl.java:133)
at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:584)
at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:650)
at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1293)
at org.jboss.tools.openshift.cdk.server.core.internal.detection.UnifiedMinishiftRuntimeDetector.getHypervisor(UnifiedMinishiftRuntimeDetector.java:257)
at org.jboss.tools.openshift.cdk.server.core.internal.detection.UnifiedMinishiftRuntimeDetector.initializeServer(UnifiedMinishiftRuntimeDetector.java:237)
at org.jboss.tools.openshift.cdk.server.core.internal.detection.AbstractCDKRuntimeDetector.initializeRuntime(AbstractCDKRuntimeDetector.java:71)
at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149)
at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56)
at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36)
at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:98)
at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:56)
at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
User can detect where the problem is, I am satisfied. Thanks!
Verified on 11.3.0.AM3-v20180322-1027-B2194.
> java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25772
> URL: https://issues.jboss.org/browse/JBIDE-25772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, runtime-detection, server
> Affects Versions: 4.5.3.AM2
> Environment: DevStudio: 11.3.0.AM2-v20180301-2015-B2134
> CDK 3.3.0
> F27
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> {code:java}
> eclipse.buildId=11.3.0.AM2-v20180301-2015-B2134
> java.version=1.8.0_161
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.core.jobs
> Error
> Tue Mar 06 09:55:15 CET 2018
> An internal error occurred during: "Searching runtimes...".
> java.lang.IllegalArgumentException: JSON parser error
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1294)
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.getHypervisor(CDK3RuntimeDetector.java:142)
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.initializeServer(CDK3RuntimeDetector.java:123)
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.AbstractCDKRuntimeDetector.initializeRuntime(AbstractCDKRuntimeDetector.java:59)
> at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149)
> at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56)
> at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36)
> at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:98)
> at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:56)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25772) java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25772?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25772.
---------------------------------
> java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25772
> URL: https://issues.jboss.org/browse/JBIDE-25772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, runtime-detection, server
> Affects Versions: 4.5.3.AM2
> Environment: DevStudio: 11.3.0.AM2-v20180301-2015-B2134
> CDK 3.3.0
> F27
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> {code:java}
> eclipse.buildId=11.3.0.AM2-v20180301-2015-B2134
> java.version=1.8.0_161
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.core.jobs
> Error
> Tue Mar 06 09:55:15 CET 2018
> An internal error occurred during: "Searching runtimes...".
> java.lang.IllegalArgumentException: JSON parser error
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1294)
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.getHypervisor(CDK3RuntimeDetector.java:142)
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.initializeServer(CDK3RuntimeDetector.java:123)
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.AbstractCDKRuntimeDetector.initializeRuntime(AbstractCDKRuntimeDetector.java:59)
> at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149)
> at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56)
> at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36)
> at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:98)
> at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:56)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25832) Credentials composite doesn't update if underlying model changes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25832?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25832.
---------------------------------
Verified on devstudio 11.3.0.AM3-v20180322-1027-B2194.
> Credentials composite doesn't update if underlying model changes
> ----------------------------------------------------------------
>
> Key: JBIDE-25832
> URL: https://issues.jboss.org/browse/JBIDE-25832
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: foundation, runtime-detection
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> Credentials composite doesn't update if underlying model changes. Workflow for this is a bit complicated, but:
> 1) Start with a clean workspace
> 2) Open server view
> 3) Choose cdk 3.2+
> 4) Click "Download runtime..." (DO NOT add credentials before this!)
> 5) In the download runtime dialog, add the proper credentials
> 6) Complete the dl-rt wizard
> 7) Note the new server wizard is downloading the runtime and all widgets are frozen
> 8) The download completes, some fields get filled in
> 9) The credential combo does not get updated. They are disabled except for 'add'
> 10) If you try to add the same credentials again, it will tell you they already exist
> 11) You must cancel the wizard and start it over.
> Also as part of this patch, we should change all dl-rt strings that reference jboss.org credentials, as they have been replaced with redhat.com credentials.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25861) Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25861?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25861:
----------------------------------
Component/s: cdk
> Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25861
> URL: https://issues.jboss.org/browse/JBIDE-25861
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.5.3.AM3
> Environment: Fedora 27 x86_64
> Reporter: Ondrej Dockal
>
> After the docker connection is interrupted by force, there is written to console endless output from docker connection:
> {code}
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25861) Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25861:
-------------------------------------
Summary: Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
Key: JBIDE-25861
URL: https://issues.jboss.org/browse/JBIDE-25861
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: docker
Affects Versions: 4.5.3.AM3
Environment: Fedora 27 x86_64
Reporter: Ondrej Dockal
After the docker connection is interrupted by force, there is written to console endless output from docker connection:
{code}
Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->unix://localhost:80
Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->unix://localhost:80
Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->unix://localhost:80
Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-4682) CDK Sever monitoring 'Add...' button throws exception
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBDS-4682?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal closed JBDS-4682.
-------------------------------
Verified on 11.3.0.AM3-v20180322-1027-B2194
> CDK Sever monitoring 'Add...' button throws exception
> -----------------------------------------------------
>
> Key: JBDS-4682
> URL: https://issues.jboss.org/browse/JBDS-4682
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk
> Environment: Windows 10 Pro
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Fix For: 11.3.0.AM3
>
> Attachments: monitoring-exception.mp4
>
>
> !monitoring-exception.mp4|id=media!
> {code}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.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:585)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:996)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:701)
> at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1035)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:901)
> at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1078)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:664)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:612)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:604)
> at org.eclipse.jface.viewers.AbstractTableViewer.lambda$0(AbstractTableViewer.java:566)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1447)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1408)
> at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:566)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:286)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1685)
> at org.eclipse.wst.server.ui.internal.viewers.MonitorDialog.createDialogArea(MonitorDialog.java:123)
> at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:768)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.eclipse.wst.server.ui.internal.viewers.MonitorComposite$2.widgetSelected(MonitorComposite.java:135)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.view.servers.PropertiesAction.perform(PropertiesAction.java:49)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:64)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25860) CDK/Minishift Server Adapter - No monitoring port can be added
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25860:
-------------------------------------
Summary: CDK/Minishift Server Adapter - No monitoring port can be added
Key: JBIDE-25860
URL: https://issues.jboss.org/browse/JBIDE-25860
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.5.3.AM3
Reporter: Ondrej Dockal
Assignee: Rob Stryker
Priority: Minor
Was is monitoring good for in server adapters like CDK and/or Minishift if any monitoring is not available and cannot be added?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months