在Worklight 6.2环境中部署war文件后,控制台不会显示关联的运行时环境:无法找到运行时。这是Worklight 6.2的基本用法,但我不知道如何解决它!
我做了什么:
我在路径〜/ worklightconsole中有worklight控制台但没有运行时! 并在自由日志中:
[6/24/14 15:28:00:978 CEST] 00000021 com.worklight.common.util.jmx.LibertyRuntimeMBeanHandler I Bean'*'不存在。 [2014年6月24日15:28:00:979 CEST] 00000021 com.ibm.worklight.admin.services.RuntimeService I未找到mxbeans
这是我的server.xml自由文件的摘录:
上下文根'/ myapp'的ant任务。 - &GT;<!-- 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'. -->
答案 0 :(得分:1)
Liberty 8.5.5.2类加载器中存在一个缺陷,它可以影响Worklight(不仅是6.2版本,而且是所有版本),甚至是在server.xml文件中定义类加载策略规则的现有非Worklight应用程序。 解决方法是删除Liberty服务器工作区目录的内容,并使用--clean选项启动服务器(每次重新启动时)。