Worklight 6.2控制台上没有运行时 [英] No runtime on my Worklight 6.2 Console

问题描述

在Worklight 6.2环境中部署war文件后，控制台不会显示关联的运行时环境：无法找到运行时。这是Worklight 6.2的基本用法，但我不知道如何解决它！

After deploying an war file in a Worklight 6.2 environment, the console doesn't show the associated runtime environment : No runtime can be found. It's a basic usage of Worklight 6.2, but I don't know how to fix it !

我做了什么：

1. 在WebSphere Liberty 8.5.5.2 + DB2 V10.5上安装Worklight Entreprise 6.2


2. 自定义配置 - liberty-db2.xml我的设置


3. ant -f myxmlfile admdatabases


4. ant -f myxmlfile adminstall


5. ant -f myxmlfile数据库


6. ant -f myxmlfile install

1. Installation of Worklight Entreprise 6.2 on WebSphere Liberty 8.5.5.2 + DB2 V10.5
2. customisation of the configuration-liberty-db2.xml with my settings
3. ant -f myxmlfile admdatabases
4. ant -f myxmlfile adminstall
5. ant -f myxmlfile databases
6. ant -f myxmlfile install

我在路径中有worklight控制台〜/ worklightconsole但没有运行时！
并在自由日志中：

I have the worklight console in the path ~/worklightconsole but no runtime ! and in the liberty log :

[6/24/14 15：28：00：978 CEST ] 00000021 com.worklight.common.util.jmx.LibertyRuntimeMBeanHandler I Bean'*'不存在。
[6/24/14 15：28：00：979 CEST] 00000021 com.ibm.worklight.admin.services.RuntimeService I未找到mxbeans

[6/24/14 15:28:00:978 CEST] 00000021 com.worklight.common.util.jmx.LibertyRuntimeMBeanHandler I Bean '*' does not exist. [6/24/14 15:28:00:979 CEST] 00000021 com.ibm.worklight.admin.services.RuntimeService I No mxbeans found

这是一个摘录我的server.xml自由文件：

And here is an extract of my server.xml liberty file :

<!-- Declare the IBM Worklight project runtime application. -->
<application id="myapp" name="myapp" location="MyProject.war" context-root="/myapp" type="war">
    <classloader delegation="parentLast">
        <privateLibrary>
            <fileset dir="${shared.resource.dir}/myapp/lib" includes="worklight-jee-library.jar"/>
        </privateLibrary>
    </classloader>
</application>

<!-- Declare the JNDI properties for the IBM Worklight project runtime. -->
<jndiEntry jndiName="myapp/publicWorkLightProtocol" value='"http"'/>
<jndiEntry jndiName="myapp/publicWorkLightPort" value='"9080"'/>


<!-- Declare the jar files for DB2 access through JDBC. -->
<library id="myapp/DB2Lib">
    <fileset dir="${shared.resource.dir}/myapp/db2" includes="db2jcc4.jar,db2jcc_license_cu.jar"/>
</library>

<!-- Declare the IBM Worklight Server database. -->
<dataSource jndiName="myapp/jdbc/WorklightDS" transactional="false">
    <jdbcDriver libraryRef="myapp/DB2Lib"/>
    <properties.db2.jcc databaseName="WRKLGHT" serverName="localhost" portNumber="50001" user="db2inst1" password="db2inst1" currentSchema="WRKLGHT"/>
</dataSource>

<!-- Declare the IBM Worklight Server reports database. -->
<dataSource jndiName="myapp/jdbc/WorklightReportsDS" transactional="false">
    <jdbcDriver libraryRef="myapp/DB2Lib"/>
    <properties.db2.jcc databaseName="WRKLGHT" serverName="localhost" portNumber="50001" user="db2inst1" password="db2inst1" currentSchema="WLREPORT"/>
</dataSource>

<!-- End of configuration added by IBM Worklight <configureApplicationServer> ant task for context root '/myapp'. -->

推荐答案

Liberty 8.5.5.2类加载器存在缺陷这可能会影响Worklight（不仅是6.2版本，还包括所有版本），甚至是在server.xml文件中定义类加载策略规则的现有非Worklight应用程序。
解决方法是删除Liberty服务器工作区目录的内容，并使用--clean选项启动服务器（每次重新启动时）。

There is a defect in the Liberty 8.5.5.2 classloader that can affect Worklight (not only the 6.2 version but all versions) and even existing non Worklight applications that define classloading policy rule in the server.xml file. The workaround is to delete the content of the Liberty server workarea directory and start the server with the --clean option (each time you restart also).

这篇关于Worklight 6.2控制台上没有运行时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！