android studio 2.x 升级到3.0之后 android device monitor 报错不能打开

平台: Win7x64bit

运行环境: JDK9.0.1, JRE9.0.1

现象:前期使用AS 2.2版本,可以正常打开android device monitor,删除低版本升级为3.0并使用原先的配置文件后,无法打开android device monitor并弹出窗口显示打印错误到日志文件,内容如下所示:

!SESSION 2018-03-15 21:27:22.759 -----------------------------------------------
eclipse.buildId=unknown
java.version=9.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN

Command-line arguments:  -os win32 -ws win32 -arch x86_64 -data @noDefault

!ENTRY org.eclipse.osgi 4 0 2018-03-15 21:27:23.867
!MESSAGE Bundle reference:file:org.apache.ant_1.8.3.v201301120609/@4 not found.
!ENTRY org.eclipse.osgi 4 0 2018-03-15 21:27:23.883
!MESSAGE Bundle reference:file:org.apache.jasper.glassfish_2.2.2.v201205150955.jar@4 not found.
//中间还有若干行已删除...
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

at org.eclipse.equinox.launcher.Main.main(Main.java:1414)

解决方法: 

1.先删除JDK9.0及JRE9.0(可以清理一下注册表, 查看当前版本可以在DOS命令行窗口输入: java -version );

2.去Oracle官网下载java se development kit 8并安装(可能需要重新配置环境变量,同时重新开启命令行窗口查看版本是否更改成功);

3.重新运行AS便可以正常打开android device monitor了.

说明:

1.更改JDK版本时,系统的JRE也需要同步更改;

2.网上有很多人说使用管理员权限去运行AS,我尝试该方法后并没有效果,在stackoverflow上也有人解释了该方式只适应于错误日志中有提示权限被限制(比如出现"... read only ..."之类的字符串)的情形.