我在从HelloWorld教程构建/运行first hybrid app应用程序时遇到了一些问题。
当我试图在HelloWorld开发服务器上运行默认MobileFirst应用程序时,服务器似乎会在MobileFirst应用程序生成器有机会完成运行之前再次停止(没有错误)。这将导致应用程序无法使用以下错误消息进行部署:
[2015-01-23 14:03:12] Failed to deploy application 'HelloWorld' to MobileFirst Server: org.apache.http.conn.HttpHostConnectException: Connect to 9.175.194.35:10080
[/9.175.194.35] failed: Connection refused: connect 我正在尝试使用7(64位)上的SR2 (64位)。我使用从Oracle下载的Java7JDK和从安装的(6.3.0)。
为了避免长/复杂的路径名,我已经将eclipse安装到C:\eclipsekepler,并且正在使用工作区目录C:\工作区。为了确保Eclipse正使用正确的JDK,我将以下内容放入我的eclipse.ini文件(vmargs之前):
-vm
C:\Program Files\Java\jdk1.7.0_75\bin\javaw.exe在服务器配置中,我将主机名设置为机器的IP地址9.175.194.35 (运行ipconfig时报告的)。
以下是完整的控制台日志:
MobileFirst Console output:
[2015-01-23 14:01:25] Starting build process: application 'HelloWorld', all environments
[2015-01-23 14:02:53] Application 'HelloWorld' with all environments build finished.
[2015-01-23 14:02:53] Deploying application 'HelloWorld' with all environments to MobileFirst Server...
[2015-01-23 14:03:12] Failed to deploy application 'HelloWorld' to MobileFirst Server: org.apache.http.conn.HttpHostConnectException: Connect to 9.175.194.35:10080
[/9.175.194.35] failed: Connection refused: connect
MobileFirst Development Server console output (corporate network info redacted):
Listening for transport dt_socket at address: 10777
Launching worklight (WebSphere Application Server 8.5.5.3/wlp-1.0.6.cl50320140731-0257) on Java HotSpot(TM) 64-Bit Server VM, version 1.7.0_75-b13 (en_US)
[AUDIT ] CWWKE0001I: The server worklight has been launched.
[AUDIT ] CWWKZ0058I: Monitoring dropins for applications.
[WARNING ] SRVE9967W: The manifest class path jaxb-api.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[WARNING ] SRVE9967W: The manifest class path activation.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[WARNING ] SRVE9967W: The manifest class path jsr173_1.0_api.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[WARNING ] SRVE9967W: The manifest class path jaxb1-impl.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://<machine-name>.<connection-specific-DNS-suffix>:10080/HelloWorldProject/
[AUDIT ] CWWKT0016I: Web application available (default_host): http://<machine-name>.<connection-specific-DNS-suffix>:10080/_MobileBrowserSimulator/
[AUDIT ] CWWKT0016I: Web application available (default_host): http://<machine-name>.<connection-specific-DNS-suffix>:10080/IBMJMXConnectorREST/
[AUDIT ] CWWKT0016I: Web application available (default_host): http://<machine-name>.<connection-specific-DNS-suffix>:10080/worklight-analytics/
[AUDIT ] CWWKZ0001I: Application _MobileBrowserSimulator started in 11.679 seconds.
[WARNING ] SRVE9967W: The manifest class path jaxb-api.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[WARNING ] SRVE9967W: The manifest class path activation.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[WARNING ] SRVE9967W: The manifest class path jsr173_1.0_api.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[WARNING ] SRVE9967W: The manifest class path jaxb1-impl.jar can not be found in jar file wsjar:file:/C:/workspace/MobileFirstServerConfig/servers/worklight/apps/worklight-management-ui.war!/WEB-INF/lib/jaxb-impl-2.1.12.osgi.jar or its parent.
[AUDIT ] CWWKZ0001I: Application WorklightAnalytics started in 19.007 seconds.
[AUDIT ] CWWKZ0001I: Application HelloWorldProject started in 21.164 seconds.
[AUDIT ] CWWKZ0022W: Application WorklightServices has not started in 30.003 seconds.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://<machine-name>.<connection-specific-DNS-suffix>:10080/worklightconsole/
[AUDIT ] CWWKZ0022W: Application WorklightConsole has not started in 30.015 seconds.
[AUDIT ] CWWKZ0001I: Application WorklightConsole started in 30.083 seconds.
[AUDIT ] CWWKZ0022W: Application WorklightAnalyticsServices has not started in 30.006 seconds.
[AUDIT ] CWWKF0015I: The server has the following interim fixes installed: PI23168.
[AUDIT ] CWWKF0011I: The server worklight is ready to run a smarter planet.
[AUDIT ] CWWKT0016I: Web application available (default_host): http://<machine-name>.<connection-specific-DNS-suffix>:10080/worklightadmin/
[WARNING ] CWNEN0070W: The javax.ws.rs.QueryParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.PathParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.CookieParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.HeaderParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.core.Context annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.
[WARNING ] CWNEN0070W: The javax.ws.rs.MatrixParam annotation class will not be recognized because it was loaded from the null location rather than from a product class loader.我能够使用MobileFirst CLI成功地运行以下等效操作:
cd C:\workspace\HelloWorldProject
mfp start
mfp build
mfp deploy
mfp console我尝试过重新安装JDK,使用Eclipse露娜和开普勒,重新安装MobileFirst工作室,从各种新的工作空间开始,但似乎没有什么不同。有谁知道会有什么问题吗?谢谢。
更新
为了尝试并强制MobileFirst使用本地主机,而不是将机器的IP地址解析为corportate网络上的主机名,我断开了网络连接,这确实导致服务器在127.0.0.1启动,而应用程序试图部署到127.0.0.1。然而,尽管如此,它还是失败了。
我确实注意到,任务似乎进展到了20%,然后一直坐在那里,直到服务器停止工作,然后任务完成,但由于服务器停止了自身,任务无法部署。
这会是性能问题吗?我正在一个带有4GB内存的Thinkpad T420上尝试这一点。
更新27/01/2015
我的一位同事在他的JDK7上安装了甲骨文MobileFirst、Eclipse露娜和IBM MobileFirst Platform Studio (6.3.0),这在硬件/企业软件/网络设置上都是相同的,而且运行良好。这使我远离公司软件或公司网络设置,并指出配置问题或其他一些软件干扰。我再次尝试卸载所有东西,包括JDK/JRE,用CCleaner清理注册表,重新安装JDK/JRE,用默认设置重新安装eclipse + mobilefirst。仍然没有成功的部署。
发布于 2015-01-23 15:48:51
我尝试了两个不同的Linux Ubuntu 14.04,32位,64位和1 Windows 7 64位.这就是我在站立MobileFirst开发服务器时所发现的和经验:
如果使用JDK1.7.0_75和error out,我会尝试使用旧版本的JDK。希望这能有所帮助。
发布于 2016-06-02 05:04:08
这对我起了作用:
发布于 2017-04-06 14:54:03
这显然是eclipse和jdk版本的一个问题。我也经历过这样的困难。MFP确实有这样的依赖性,这就是为什么您的mfp-cli运行良好的原因。尝试在JDK1.7中使用eclipse或露娜。应该管用的。
https://stackoverflow.com/questions/28112479
复制相似问题