Worklight应用程序运行时错误

Question

我们在PROD环境中遇到问题，它显示以下错误消息：

主页显示运行时包含项目文件：

WAS上的错误是：

[5/1/15 12:38:29:901 EDT] 0000009f ApplicationMa E 

com.worklight.mgmt.impl.ApplicationManagementImpl getApplicationRuntimeInformation FWLSE0023E: application 'MobileBanking' not found, please redeploy. [project MobileBanking] 
[5/1/15 12:38:29:947 EDT] 0000009f DMAdapter     I com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis Engine using data base: /wl62/profiles/node1/properties/logbr/ffdc/adv/ffdcdb.xml 
[5/1/15 12:38:30:069 EDT] 0000009f FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /wl62/profiles/node1/logs/ffdc/server11_wl_3e94673b_15.05.01_12.38.29.9336586937544274552029.txt com.ibm.ws.management.AdminServiceImpl.invoke 693 
[5/1/15 12:38:30:573 EDT] 00000100 ApplicationSe E   FWLSE3000E: A server error was detected. 
                                 java.lang.IllegalArgumentException: FWLSE0023E: application 'MobileBanking' not found, please redeploy. [project MobileBanking] 
        at com.worklight.mgmt.impl.ApplicationManagementImpl.getApplicationRuntimeInformation(ApplicationManagementImpl.java:165) 
        at com.worklight.core.jmx.ProjectManagementMXBeanImpl.getApplicationRuntimeInformation(ProjectManagementMXBeanImpl.java:673) 
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:76) 
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
        at java.lang.reflect.Method.invoke(Method.java:607) 
        at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75) 
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source) 
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
        at java.lang.reflect.Method.invoke(Method.java:607) 
        at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279) 
        at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193) 
        at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175) 
        at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117) 
        at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54) 
        at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) 
        at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) 
        at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) 
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) 
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) 
        at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1335) 
        at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) 
        at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1228) 
        at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:181) 
        at com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.java:247) 
        at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWork(IPCConnectorInboundLink.java:360) 
        at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCConnectorReadCallback.complete(IPCConnectorInboundLink.java:602) 
        at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784) 
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) 
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) 
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) 
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) 
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) 
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) 
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) 
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862)

我们不止一次重新安装了运行时，它说成功了，我们还回收了dmgr，节点，cluser，服务器和运行时，并且所有显示绿色箭头都有成功的启动消息。

我们的Dev，QAT和UAT使用相同的WAR文件，它们都没有问题。

Worklight版本6.2.0.1

WAS版本8.5.5.1

任何帮助解决它，谢谢。

Answer 1

我们能够解决应用程序问题和Worklight服务问题。有许多部分需要修复。在大多数情况下，这些问题是Worklight实现安全性的复杂性的结果。现在所有环境都已启动并运行。

我们遵循以解决问题的步骤：

• 确保两个节点上都运行完全相同的配置。
• 确保JVM配置匹配。
• 查看每个节点上的安全配置（SSL证书 - SLL别名和SSL密钥库）。