0

环境细节:

1.操作系统Linux

2.Worklight 6.2在集群环境中

3.WAS ND 8.5.5

4.DB2 10.5

部署示例战争文件。

部署一个大小为 3mb 的 sample-common.wlapp 文件会给出“java 堆空间”。如果文件 (.wlapp) 小于 2 MB,则部署成功。

我尝试在服务器上将 JVM 堆大小设置为大约 2048mb。仍然没有运气。

Worklight 控制台活动日志上的错误

`事务 2 类型:UPLOAD_APPLICATION 状态:FAILURE dateCreated:2014-10-09T10:43:28.943Z dateUpdated:2014-10-09T10:44:07.932Z 服务器:WebSphere:ihsCell01/wl2Node01/worklight2 描述:appVersionsDeployed:1:applicationName: AppDelegate 环境:android 版本:1.0 文件名:AppDelegate-android-1.0.wlapp 错误:1:mbeanName:WebSphere:cell=ihsCell01,name=Dubai,node=wl1Node01,process=worklight1,type=ProjectManagement_RAK 日期:2014-10-09T10 :44:03.766Z 阶段:准备代码:失败异常:OutOfMemoryError 详细信息:Java 堆空间 2:mbeanName:WebSphere:cell=ihsCell01,name=Dubai,node=wl2Node01,process=worklight2,type=ProjectManagement_RAK 日期:2014-10-09T10:44:07.803Z 阶段:准备代码:FAILURE 异常:OutOfMemoryError 详细信息:Java 堆空间

`

服务器日志

[10/9/14 4:10:18:872 PDT] 0000010c BaseTransacti E   RuntimeMBeanCallable.call() exception
                             java.lang.OutOfMemoryError: Java heap space
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:948)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplateOnce(SOAPConnectorClient.java:916)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:682)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:672)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:658)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:480)
at com.sun.proxy.$Proxy85.invoke(Unknown Source)
at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:224)
at com.worklight.common.util.jmx.WASRuntimeMBeanHandler$AdminClientMBeanServerConnection.invoke(WASRuntimeMBeanHandler.java:524)
at com.sun.jmx.mbeanserver.MXBeanProxy$InvokeHandler.invoke(MXBeanProxy.java:146)
at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(MXBeanProxy.java:160)
at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:259)
at com.sun.proxy.$Proxy124.deployApplication(Unknown Source)
at com.ibm.worklight.admin.actions.ApplicationDeploymentTransaction.prepareMBean(ApplicationDeploymentTransaction.java:503)
at com.ibm.worklight.admin.actions.util.RuntimeMBeanWorkerThreadCaller$RuntimeMBeanCallable.call(RuntimeMBeanWorkerThreadCaller.java:75)
at com.ibm.worklight.admin.actions.util.RuntimeMBeanWorkerThreadCaller$RuntimeMBeanCallable.call(RuntimeMBeanWorkerThreadCaller.java:43)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931)
at java.lang.Thread.run(Thread.java:773)

[10/9/14 4:10:20:275 PDT] 0000010b BaseTransacti E RuntimeMBeanCallable.call() 异常 java.lang.OutOfMemoryError:com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault 处的 Java 堆空间( SOAPConnectorClient.java:948) 在 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplateOnce(SOAPConnectorClient.java:916) 在 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java: 682) 在 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:672) 在 com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:658) 在 com .ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:480) 位于 com.sun.proxy.$Proxy85。在 com.worklight.common.util.jmx.WASRuntimeMBeanHandler$AdminClientMBeanServerConnection.invoke(WASRuntimeMBeanHandler.java:524) 在 com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:224) 调用(未知来源)。 sun.jmx.mbeanserver.MXBeanProxy$InvokeHandler.invoke(MXBeanProxy.java:146) at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(MXBeanProxy.java:160) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java: 259) 在 com.sun.proxy.$Proxy124.deployApplication(Unknown Source) 在 com.ibm.worklight.admin.actions.ApplicationDeploymentTransaction.prepareMBean(ApplicationDeploymentTransaction.java:503) 在 com.ibm.worklight.admin.actions.util .RuntimeMBeanWorkerThreadCaller$RuntimeMBeanCallable.call(RuntimeMBeanWorkerThreadCaller.java:75),位于 com.ibm.worklight.admin。action.util.RuntimeMBeanWorkerThreadCaller$RuntimeMBeanCallable.call(RuntimeMBeanWorkerThreadCaller.java:43) 在 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) 在 java.util.concurrent.FutureTask.run(FutureTask.java: 149) 在 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) 在 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) 在 java.lang.Thread.run(Thread .java:773)在 java.lang.Thread.run(Thread.java:773) 处运行(ThreadPoolExecutor.java:931)在 java.lang.Thread.run(Thread.java:773) 处运行(ThreadPoolExecutor.java:931)

4

1 回答 1

1

这应该在最近的 IFIX 中修复,网址为https://www-947.ibm.com/support/entry/myportal/product/other_software/ibm_worklight?productContext=-1445909362#

于 2014-10-09T14:24:22.917 回答