Websphere正在上传EAR文件,堆问题

时间:2017-11-24 13:05:15

标签: java websphere heap-memory ear

首先要说我是java和websphere的新手,因此我的知识非常低。

我正在尝试从full name

安装应用程序

因此,在我单击“安装”并选择要上载的EAR文件并转到“下一步”之后,Websphere就停止了,并且它不再响应了。

Websphere进程的CPU使用率高达100%,我必须将其杀死并再次启动Websphere。

我在日志中发现的错误是:

Application Types -> WebSphere enterprise applications

我有两个集群。每个群集有两个成员。我正在尝试使用其中一个集群设置应用程序。

在设置FFDC Exception:java.lang.OutOfMemoryError SourceId:com.ibm.ws.management.AdminServiceImpl.queryNames ProbeId:284 Reporter:javax.management.ObjectName@44376c54 java.lang.OutOfMemoryError: Java heap space at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:295) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1135) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at javax.management.ObjectName.writeObject(ObjectName.java:1263) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1020) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1502) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1433) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1179) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1555) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1516) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1433) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1179) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at com.ibm.ws.management.connector.ipc.ClientAccessor.request(ClientAccessor.java:112) at com.ibm.ws.management.connector.ipc.IPCConnectorClient.sendReceive(IPCConnectorClient.java:484) at com.ibm.ws.management.connector.ipc.IPCConnectorClient.queryNames(IPCConnectorClient.java:828) at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:108) at com.ibm.ws.management.AdminServiceImpl.queryNames(AdminServiceImpl.java:684) at com.ibm.ws.management.status.AbstractStatusCache.getMBean(AbstractStatusCache.java:672) at com.ibm.ws.management.status.DeploymentManagerStatusCache.requestReport(DeploymentManagerStatusCache.java:336) at com.ibm.ws.management.status.DeploymentManagerStatusCache.requestReport(DeploymentManagerStatusCache.java:368) at com.ibm.ws.management.status.DeploymentManagerStatusCache.addToCache(DeploymentManagerStatusCache.java:251) at com.ibm.ws.management.status.DeploymentManagerStatusCache.childAdded(DeploymentManagerStatusCache.java:921) at com.ibm.ws.management.RoutingTable$AddChildThread.run(RoutingTable.java:1561) 下的群集的每个成员中,设置堆的下一个设置:

Java and Process Management -> Process definition -> Java Virtual Machine

任何人都可以帮我解决这个问题。

1 个答案:

答案 0 :(得分:1)

如果您有群集,则使用的是网络部署版。在这种情况下,安装通过Deployment Manager完成。您需要增加Deployment Manager JVM的堆大小。在Web管理控制台中,转到System administration > Deployment manager,您应该还有Java and Process Management选项。增加堆大小,重新启动dmgr,然后重新安装应用程序。您可能还需要增加节点代理的堆大小,但从Dmgr开始。