IBM Worklight Server 6.2 - 在Apache Tomcat上运行? “等待管理服务启动时超时” [英] IBM Worklight Server 6.2 - Running on Apache Tomcat? "Timeout while waiting for the management service to start up"

查看:166
本文介绍了IBM Worklight Server 6.2 - 在Apache Tomcat上运行? “等待管理服务启动时超时”的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我一直在尝试设置IBM Worklight环境。我想使用:

I've been trying to setup an IBM Worklight environment. I want to use:


  • Windows Server

  • Apache Tomcat 7(撰写本文时最新版本) )

  • IBM Worklight 6.2(撰写本文时最新版)

  • MySQL Server 5.6(撰写本文时最新)

  • Windows Server
  • Apache Tomcat 7 (latest at the time of writing)
  • IBM Worklight 6.2 (latest at the time of writing)
  • MySQL Server 5.6 (latest at the time of writing)

一切似乎都运转正常。我已经设置了Tomcat(默认配置),MySQL(默认配置)。然后我继续设置IBM Worklight。我指向Tomcat安装目录,放入MySQL Connector / J jar文件等等。我几乎把所有东西都默认了。

Everything seems to be working OK. I've setup Tomcat (default configuration), MySQL (default configuration). Then I continued setting up IBM Worklight. I pointed to the Tomcat installation directory, put in the MySQL Connector/J jar file, etc etc. I left virtually everything default.

完成后,我部署了一个应用程序。该应用程序是使用Eclipse使用IBM Worklight Studio 6.2插件制作的。在点击应用程序URL( http:// localhost:8080 / appname / console )时,出现以下错误:
HTTP状态500 - java.lang。 RuntimeException:等待管理服务启动时超时

Upon completion, I deployed an app. The app was made with Eclipse, using the IBM Worklight Studio 6.2 plugin. Upon hitting the app URL (http://localhost:8080/appname/console), I get the following error: HTTP Status 500 - java.lang.RuntimeException: Timeout while waiting for the management service to start up

type Exception report

message java.lang.RuntimeException: Timeout while waiting for the management service to start up

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up
    com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForInitialization(AuthenticationFilter.java:561)
    com.worklight.core.auth.impl.AuthenticationFilter.doFilter(AuthenticationFilter.java:130)
root cause

java.lang.RuntimeException: Timeout while waiting for the management service to start up
    com.worklight.core.init.WorklightServletInitializer$1.run(WorklightServletInitializer.java:133)
    java.lang.Thread.run(Unknown Source)
note The full stack trace of the root cause is available in the Apache Tomcat/7.0.54 logs.

Apache Tomcat/7.0.54

然而,当我这样做的时候使用IBM WebSphere Liberty服务器安装,一切正常。我们确实想使用Apache Tomcat而不是WebSphere Liberty。

However, when I do the same install using an IBM WebSphere Liberty server, everything works fine. We do want to use Apache Tomcat instead of WebSphere Liberty.

我做错了什么?什么是管理服务,我该如何启动或激活它?或者至少检查一下?它与JMX有关吗?

What am I doing wrong? What's this "management service" and how can I start it or activate it? Or at least check it? Does it have something to do with JMX?

推荐答案

我认为在你的情况下没有正确配置JMX。请参阅 https ://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_optional_config_app_server_tomcat.html

I think JMX is not properly configured in your case. See https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_optional_config_app_server_tomcat.html

当服务器启动时,Worklight运行时会尝试通过JMX与Worklight Admin Service进行通信。由于Web应用程序的启动顺序是任意的,因此可能会在Worklight运行时之后启动Worklight Admin Services。在这种情况下,Worklight运行时将一直等待Worklight Admin Services运行。异常中提到的超时意味着运行时在给定的时间内未找到正在运行的Worklight Admin Services。这可能意味着:

When the server starts, the Worklight runtime tries to communicate with the Worklight Admin Service through JMX. Since the start order of the web application is arbitrary, it can happen than the Worklight Admin Services start after the Worklight runtime. In this case, the Worklight runtime waits until the Worklight Admin Services are running. The timeout mentioned in the exception means that the runtime did not found the running Worklight Admin Services in a given amount of time. This can mean:


  1. JMX通信失败,因此Worklight运行时未检测到Worklight管理服务。

  2. Worklight管理服务在启动期间崩溃,例如在错误配置Worklight管理数据库时。

  3. 可以为Worklight指定不同的JNDI属性ibm.worklight.admin.environmentid运行时比Worklight管理服务。在这种情况下,运行时无法找到其管理服务。

另请参阅如何解决未在Worklight 6.2中启动的管理服务

这篇关于IBM Worklight Server 6.2 - 在Apache Tomcat上运行? “等待管理服务启动时超时”的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆