Question

环境详情：

1.OS Linux

2.集群环境中的Worklight 6.2

3.WAS ND 8.5.5

4.DB2 10.5

已部署示例战争文件。

部署一个大小为3mb的sample-common.wlapp文件，可以得到＆＃34; java堆空间＆＃34;。如果文件（.wlapp）的大小小于2 MB，则成功部署。

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

Error on worklight console activity log

`交易2 类型：UPLOAD_APPLICATION 状态：失败 dateCreated：2014-10-09T10：43：28.943Z dateUpdated：2014-10-09T10：44：07.932Z server：WebSphere：ihsCell01 / wl2Node01 / worklight2 描述： appVersionsDeployed： 1： applicationName：AppDelegate 环境：android 版本：1.0 filename：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 阶段：PREPARE 代码：FAILURE 异常：OutOfMemoryError 细节：Java堆空间 2： mbeanName：WebSphere：cell = ihsCell01，name = Dubai，node = wl2Node01，process = worklight2，type = ProjectManagement_RAK 日期：2014-10-09T10：44：07.803Z 阶段：PREPARE 代码：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：Java堆空间在com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault（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） at 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） at com.sun.proxy。$ Proxy85.invoke（Unknown Source）在com.ibm.ws.management.AdminClientImpl.invoke（AdminClientImpl.java:224）在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）在javax.management.MBeanServerInvocationHandler.invoke（MBeanServerInvocationHandler.java:259）在com.sun.proxy。$ Proxy124.deployApplication（未知来源）在com.ibm.worklight.admin.actions.ApplicationDeploymentTransaction.prepareMBean（ApplicationDeploymentTransaction.java:503）在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）在java.lang.Thread.run（Thread.java:773）

Answer 1

这应该在https://www-947.ibm.com/support/entry/myportal/product/other_software/ibm_worklight?productContext=-1445909362#

的最近IFIX修复

Worklight 6.2 wlapp部署给出了java堆空间错误

1 个答案: