本文的目的是介绍无法连接到EclipseLuna市场的详细情况,特别关注eclipse无法连接到vm的相关信息。我们将通过专业的研究、有关数据的分析等多种方式,为您呈现一个全面的了解无法连接到Ecli
本文的目的是介绍无法连接到Eclipse Luna市场的详细情况,特别关注eclipse无法连接到vm的相关信息。我们将通过专业的研究、有关数据的分析等多种方式,为您呈现一个全面的了解无法连接到Eclipse Luna市场的机会,同时也不会遗漏关于Android ADB端口号发生更改,Eclipse无法连接到设备、android – Eclipse无法连接到模拟器上的活动管理器 – HelloWorld不会出现、configuration for eclipseME plugin in eclipse 3.1[eclipse ME 在eclipse 3.1中的配置(以MOTO为例)]、Docker上的Kibana无法连接到Elasticsearch的知识。
本文目录一览:- 无法连接到Eclipse Luna市场(eclipse无法连接到vm)
- Android ADB端口号发生更改,Eclipse无法连接到设备
- android – Eclipse无法连接到模拟器上的活动管理器 – HelloWorld不会出现
- configuration for eclipseME plugin in eclipse 3.1[eclipse ME 在eclipse 3.1中的配置(以MOTO为例)]
- Docker上的Kibana无法连接到Elasticsearch
无法连接到Eclipse Luna市场(eclipse无法连接到vm)
我无法将Eclipse Luna发行版连接到市场以安装Maven 2 Pluggin。这是我的配置:
Eclipse:-Eclipse Luna M5版本,我配置了一个代理
我的电脑:-Windows XP 32位
这是错误消息:
!SESSION 2014-03-03 14:55:53.568 -----------------------------------------------eclipse.buildId=4.4.0.I20140123-1600java.version=1.6.0_29java.vendor=Sun Microsystems Inc.BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FRFramework arguments: -product org.eclipse.epp.package.standard.productCommand-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.standard.product!ENTRY org.eclipse.core.net 1 0 2014-03-03 14:56:01.676!MESSAGE System property http.proxyHost is not set but should be <myProxy_url>.!ENTRY org.eclipse.core.net 1 0 2014-03-03 14:56:01.692!MESSAGE System property http.proxyPort is not set but should be <myProxy_port>.!ENTRY org.eclipse.core.net 1 0 2014-03-03 14:56:01.692!MESSAGE System property https.proxyHost is not set but should be <myProxy_url>.!ENTRY org.eclipse.core.net 1 0 2014-03-03 14:56:01.692!MESSAGE System property https.proxyPort is not set but should be <myProxy_port>.!ENTRY org.eclipse.core.net 1 0 2014-03-03 14:56:01.692!MESSAGE System property https.proxyHost is not set but should be <myProxy_url>.!ENTRY org.eclipse.core.net 1 0 2014-03-03 14:56:01.708!MESSAGE System property https.proxyPort is not set but should be <myProxy_port>.!ENTRY org.eclipse.epp.mpc.ui 4 0 2014-03-03 14:56:14.988!MESSAGE Cannot open Eclipse Marketplace!STACK 1org.eclipse.core.runtime.CoreException: Cannot install remote marketplace locations: Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/p at org.eclipse.epp.internal.mpc.ui.commands.MarketplaceWizardCommand.execute(MarketplaceWizardCommand.java:101) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:163) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:222) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:776) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:668) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$6(HandledContributionItem.java:652) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:584) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450)Caused by: org.eclipse.core.runtime.CoreException: Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/p at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35) at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:69) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:131) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:85) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:72) at org.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.listCatalogs(DefaultCatalogService.java:36) at org.eclipse.epp.internal.mpc.ui.commands.MarketplaceWizardCommand$5.run(MarketplaceWizardCommand.java:254) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)Caused by: org.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:665) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:273) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172) ... 12 moreContains: Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/porg.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:665) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:273) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35) at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:69) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:131) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:85) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:72) at org.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.listCatalogs(DefaultCatalogService.java:36) at org.eclipse.epp.internal.mpc.ui.commands.MarketplaceWizardCommand$5.run(MarketplaceWizardCommand.java:254) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)!SUBENTRY 1 org.eclipse.epp.mpc.ui 4 0 2014-03-03 14:56:14.988!MESSAGE Cannot install remote marketplace locations: Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/p!STACK 1org.eclipse.core.runtime.CoreException: Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/p at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35) at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:69) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:131) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:85) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:72) at org.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.listCatalogs(DefaultCatalogService.java:36) at org.eclipse.epp.internal.mpc.ui.commands.MarketplaceWizardCommand$5.run(MarketplaceWizardCommand.java:254) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)Caused by: org.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:665) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:273) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172) ... 12 more!SUBENTRY 2 org.eclipse.equinox.p2.transport.ecf 4 1002 2014-03-03 14:56:14.988!MESSAGE Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/p!STACK 1org.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:665) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:273) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35) at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:69) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:131) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:85) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:72) at org.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.listCatalogs(DefaultCatalogService.java:36) at org.eclipse.epp.internal.mpc.ui.commands.MarketplaceWizardCommand$5.run(MarketplaceWizardCommand.java:254) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)!SUBENTRY 3 org.eclipse.ecf.identity 4 0 2014-03-03 14:56:14.988!MESSAGE HttpComponents connection error response code 400.!SUBENTRY 2 org.eclipse.equinox.p2.transport.ecf 4 1002 2014-03-03 14:56:14.988!MESSAGE Bad HTTP Request: http://marketplace.eclipse.org/catalogs/api/p!STACK 1org.eclipse.ecf.filetransfer.IncomingFileTransferException: HttpComponents connection error response code 400. at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.openStreams(HttpClientRetrieveFileTransfer.java:665) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879) at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570) at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.read(FileReader.java:273) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.stream(RepositoryTransport.java:172) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.epp.internal.mpc.core.util.AbstractP2TransportFactory.invokeStream(AbstractP2TransportFactory.java:35) at org.eclipse.epp.internal.mpc.core.util.TransportFactory$1.stream(TransportFactory.java:69) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:131) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:85) at org.eclipse.epp.internal.mpc.core.service.RemoteMarketplaceService.processRequest(RemoteMarketplaceService.java:72) at org.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.listCatalogs(DefaultCatalogService.java:36) at org.eclipse.epp.internal.mpc.ui.commands.MarketplaceWizardCommand$5.run(MarketplaceWizardCommand.java:254) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)!SUBENTRY 3 org.eclipse.ecf.identity 4 0 2014-03-03 14:56:14.988!MESSAGE HttpComponents connection error response code 400.!ENTRY org.eclipse.egit.ui 2 0 2014-03-03 14:56:17.457!MESSAGE Warning: EGit couldn''t detect the installation path "gitPrefix" of native Git. Hence EGit can''t respect system levelGit settings which might be configured in ${gitPrefix}/etc/gitconfig under the native Git installation directory.The most important of these settings is core.autocrlf. Git for Windows by default sets this parameter to true inthis system level configuration. The Git installation location can be configured on theTeam > Git > Configuration preference page''s ''System Settings'' tab.This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.!ENTRY org.eclipse.egit.ui 2 0 2014-03-03 14:56:17.472!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Gituser global configuration and to define the default location to store repositories: ''C:\Documents and Settings\ombinte''. If this isnot correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows andEGit might behave differently since they see different configuration options.This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
答案1
小编典典我找到了解决方案。我更改了Eclipse版本。我现在使用Eclipse
Indigo,因为所有4.x版本都无法在我的计算机上运行。提醒一下,我使用Windows XP 32位…史前机器。
Android ADB端口号发生更改,Eclipse无法连接到设备
我使用Windows 7升级到了新的电脑。Eclipse无法连接到ADB。 永远。 任务pipe理器显示ADB端口号在3180到5452之间,从不在5555到5585之间。 进入命令提示符input“kill-server”,然后“start-server”重置最后显示“守护进程没有运行,现在在端口5037 *守护进程启动成功”,但下一个命令“adb devices”没有显示任何附加。 端口号改变,DDMS显示ADB被强制closures,所以有一个连接的地方。
我尝试更新驱动程序,并强制端口号连接使用'adb端口xxxx',但显然它没有奏效,否则我不会在这里发布。 使用WinXP我的最后一台电脑,我能够强制端口号,如果需要使其工作,但这不是在这里发生。
有什么build议么?
触摸屏模拟器:是否有任何Windows模拟器在触摸屏环境中testing应用程序
使用SimpleScalar运行基本代码时出错
在浏览器中模拟linuxterminal
在没有networking摄像头对话框的情况下启动Android模拟器
是否有可能在Windows上的iPhone模拟器中运行IPA文件?
如何在Windows平板电脑上testing我的网站兼容性
VirtualKeyCode.MEDIA_PLAY_PAUSE不起作用
无法更改虚拟机的内存:错误代码32775
networking模拟器
调度程序模拟器linsched
android – Eclipse无法连接到模拟器上的活动管理器 – HelloWorld不会出现
这似乎与:
Android application doesn’t start from Eclipse
即使使用Android 2.2平台,这仍然是操作模拟器的可接受方式吗?即上述帖子中描述的1,2,3个启动/终止过程?我在使用Eclipse w / ADT插件的WinXP上遇到了类似的问题.为什么活动无法在模拟器上启动?如果这可能是问题,计算机有756MB RAM.部署正在进行,直到Eclipse尝试部署活动.模拟器以文本“ANDROID_”开头,然后最终只显示ANDROID徽标,尽管看起来仍然运行得很好.有任何想法吗?谢谢.代码是从HelloWorld教程中复制的.这是Eclipse控制台日志,包括最后的错误消息:
[2010-06-23 15:43:26 – myHelloWorldProject] ——————————
[2010-06-23 15:43:26 – myHelloWorldProject] Android Launch!
[2010-06-23 15:43:26 – myHelloWorldProject] adb is running normally.
[2010-06-23 15:43:27 – myHelloWorldProject] Performing net.concentricllc.HelloWorld.HelloAndroid activity launch
[2010-06-23 15:43:27 – myHelloWorldProject] Automatic Target Mode: using existing emulator ’emulator-5554′ running compatible AVD ‘myHelloWorldAVD’
[2010-06-23 15:43:27 – myHelloWorldProject] WARNING: Application does not specify an API level requirement!
[2010-06-23 15:43:27 – myHelloWorldProject] Device API version is 8 (Android 2.2)
[2010-06-23 15:43:27 – myHelloWorldProject] Uploading myHelloWorldProject.apk onto device ’emulator-5554′
[2010-06-23 15:43:32 – myHelloWorldProject] Installing myHelloWorldProject.apk…
[2010-06-23 15:48:29 – myHelloWorldProject] Success!
[2010-06-23 15:48:37 – myHelloWorldProject] Starting activity net.concentricllc.HelloWorld.HelloAndroid on device
[2010-06-23 15:51:35 – myHelloWorldProject] Device not ready. Waiting 3 seconds before next attempt.
[2010-06-23 15:51:36 – myHelloWorldProject] ActivityManager: android.util.AndroidException: Can’t connect to activity manager; is the system running?
[2010-06-23 15:51:38 – myHelloWorldProject] Starting activity net.concentricllc.HelloWorld.HelloAndroid on device
[2010-06-23 15:53:36 – myHelloWorldProject] Device not ready. Waiting 3 seconds before next attempt.
[2010-06-23 15:53:36 – myHelloWorldProject] ActivityManager: android.util.AndroidException: Can’t connect to activity manager; is the system running?
[2010-06-23 15:53:39 – myHelloWorldProject] Starting activity net.concentricllc.HelloWorld.HelloAndroid on device
[2010-06-23 15:55:41 – myHelloWorldProject] Device not ready. Waiting 3 seconds before next attempt.
[2010-06-23 15:55:41 – myHelloWorldProject] ActivityManager: android.util.AndroidException: Can’t connect to activity manager; is the system running?
[2010-06-23 15:55:44 – myHelloWorldProject] Starting activity net.concentricllc.HelloWorld.HelloAndroid on device
[2010-06-23 15:57:15 – myHelloWorldProject] Device not ready. Waiting 3 seconds before next attempt.
[2010-06-23 15:57:15 – myHelloWorldProject] ActivityManager: android.util.AndroidException: Can’t connect to activity manager; is the system running?
[2010-06-23 15:57:18 – myHelloWorldProject] Starting activity net.concentricllc.HelloWorld.HelloAndroid on device
[2010-06-23 15:58:51 – myHelloWorldProject] ActivityManager: Error type 2
[2010-06-23 15:58:52 – myHelloWorldProject] ActivityManager: android.util.AndroidException: Can’t connect to activity manager; is the system running?
解决方法:
转到命令提示符并运行以下命令:
adb kill-server
adb start-server
现在运行模拟器,然后运行您的应用程序:
adb install -r myApp.apk
这解决了我的问题
configuration for eclipseME plugin in eclipse 3.1[eclipse ME 在eclipse 3.1中的配置(以MOTO为例)]
- install eclipseME plugin
- install sun''s wireless tool kit 2.1 or other compatible toolkits
- enter windows->preference->platform components, right click wireless ToolKits and select add..... Select the right directory(sample: C:/WTK21)
- for Moto SDK,
- you may choose to add one profile. sample(MOTOM1--add midp.zip in M1 lib as external jar)
- Add platform definition. Sample(MOTOM1--select the profile MOTOM1)
- Enter Run->External Tools->External Tools.. and create a new configuration by clicking button(NEW) Parameters are set as below sample for V600(j2me-v600):
- Location: C:/Program Files/Motorola/SDK v4.3 for J2ME/EmulatorA.1/bin/emujava.exe
- working directory: c:/Program Files/Motorola/SDK v4.3 for J2ME/EmulatorA.1/bin
- arguments: ${project_loc}/deployed/${project_name}.jad -deviceFile resources/V600.props
- you may get working information by run "C:/Program Files/Motorola/SDK v4.3 for J2ME/launchpad.exe"
- To create a new J2ME project, you may first create a j2me project and then create a midlet
- To test it with MOTO V600 simulator, you need to create the package first and then select run->external tools->j2me-v600
- To test it with sun''s simulator, just enter run->run as->Emulated J2ME Midlet
原文链接: http://blog.csdn.net/swingseagull/article/details/313114
Docker上的Kibana无法连接到Elasticsearch
如何解决Docker上的Kibana无法连接到Elasticsearch?
关于在容器内运行命令时的含义localhost
或127.0.0.1
含义存在一些误解。因为每个容器都有自己的网络,localhost
所以不是您的真正主机系统,而是容器本身。因此,当您运行kibana并将ELASTICSEARCH_URL
变量指向localhost:9200
kibana进程时,它会在kibana容器中寻找当然不是在其中运行的elasticsearch。
您已经引入了一些在启动容器时引用的自定义网络。在同一网络中运行的所有容器都可以通过其expose
d端口上的名称相互引用(请参阅Dockerfiles)。在为elasticsearch容器命名时elasticsearch_2_4
,可以将elasticsearch
的http端点引用为http://elasticsearch_2_4:9200
。
docker run -d --network mynetwork -e ELASTICSEARCH_URL=http://elasticsearch_2_4:9200 -p 5601:5601 kibana:4.6
只要您不需要直接访问elasticsearch实例,您甚至可以忽略将端口9200和9300映射到您的主机。
除了建议自己启动所有容器之外,我还建议使用docker-
compose
来管理所有服务和参数。您还应该考虑将本地文件夹作为卷安装,以使数据持久化。这可能是您的撰写文件。networks
如果需要外部网络,请添加,否则此设置只会为您创建一个网络。
version: "2"
services:
elasticsearch:
image: elasticsearch:2.4
ports:
- "9200:9200"
volumes:
- ./esdata/:/usr/share/elasticsearch/data/
kibana:
image: kibana:4.6
ports:
- "5601:5601"
environment:
- ELASTICSEARCH_URL=http://elasticsearch:9200
解决方法
我尝试创建Kibana和Elasticsearch,看来Kibana在识别Elasticsearch时遇到了麻烦。
这是我的步骤:
1)建立网络
docker network create mynetwork --driver=bridge
2)运行Elasticsearch容器
docker run -d -p 9200:9200 -p 9300:9300 --name elasticsearch_2_4 --network mynetwork elasticsearch:2.4
3)运行Kibana容器
docker run -i --network mynetwork -p 5601:5601 kibana:4.6
通过浏览器通过http:// localhost:9200
/连接到Elasticsearch时,我得到JSON输出。
但是,当我打开HTTP://本地主机:5601 /我得到
Unable to connect to Elasticsearch at http://elasticsearch:9200.
替代方法
我尝试时仍然出现类似的错误
docker run -d -e ELASTICSEARCH_URL=http://127.0.0.1:9200 -p 5601:5601 kibana:4.6
我在哪里得到错误
Unable to connect to Elasticsearch at http://127.0.0.1:9200.
今天关于无法连接到Eclipse Luna市场和eclipse无法连接到vm的讲解已经结束,谢谢您的阅读,如果想了解更多关于Android ADB端口号发生更改,Eclipse无法连接到设备、android – Eclipse无法连接到模拟器上的活动管理器 – HelloWorld不会出现、configuration for eclipseME plugin in eclipse 3.1[eclipse ME 在eclipse 3.1中的配置(以MOTO为例)]、Docker上的Kibana无法连接到Elasticsearch的相关知识,请在本站搜索。
本文标签: