was7发布应用程序报错

[heartche88]

Installing...
If there are enterprise beans in the application, the EJB deployment process can take several minutes. Do not save the configuration until the process completes.

Check the SystemOut.log on the deployment manager or server where the application is deployed for specific information about the EJB deployment process as it occurs.

ADMA5016I: Installation of MAXIMO started.

ADMA5067I: Resource validation for application MAXIMO completed successfully.

ADMA5058I: Application and module versions are validated with versions of deployment targets.

ADMA5018I: The EJBDeploy program is running on file D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\514564614\upload\maximo.ear.

Starting workbench.

EJB Deploy configuration directory: d:\Program Files\IBM\WebSphere\AppServer\deploytool\itp\configuration/

framework search path: d:\Program Files\IBM\WebSphere\AppServer\deploytool\itp\plugins

build: RAD7552-I20100915_1449

Creating the project.

Deploying jar mboejb

正在生成部署代码

正在调用 RMIC。

2014-11-12 16:14:24 RMICOperation invokeRMICInJVM

INFO: RMIC invoked with arguments: -extdirs D:\Program Files\IBM\WebSphere\AppServer\java\jre\bin\default\jclSC160\vm.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\annotation.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\beans.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\java.util.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\jndi.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\logging.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\security.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\sql.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmorb.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmorbapi.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmcfw.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\rt.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\charsets.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\resources.jar;D:\Program Files\IBM\WebS

phere\AppServer\java\jre\lib\ibmpkcs.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmcertpathfw.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjgssfw.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjssefw.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmsaslfw.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjcefw.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjgssprovider.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmjsseprovider2.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmcertpathprovider.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ibmxmlcrypto.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\management-agent.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\xml.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\jlm.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\javascript.jar;D:\Program Files\IBM\WebSphere\AppServer\deploytoo

l\itp\batchboot.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ext\iwsorbutil.jar;D:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ext;D:\Program Files\IBM\WebSphere\AppServer\eclipse\plugins\j2ee.javax_1.4.0;D:\Program Files\IBM\WebSphere\AppServer\eclipse\plugins\com.ibm.ws.runtime.eclipse_1.0.0;D:\Program Files\IBM\WebSphere\AppServer\dev\javaee5.jar;D:\Program Files\IBM\WebSphere\AppServer\plugins;D:\Program Files\IBM\WebSphere\AppServer\java\lib;D:\Program Files\IBM\WebSphere\AppServer\classes;D:\Program Files\IBM\WebSphere\AppServer\lib;D:\Program Files\IBM\WebSphere\AppServer\installedChannels;D:\Program Files\IBM\WebSphere\AppServer\lib\ext;D:\Program Files\IBM\WebSphere\AppServer\web\help;D:\Program Files\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime; -classpath D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\mboejb\build\classes;D:\Program Files\IBM\WebSphere\AppServer

\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\businessobjects.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\commonweb.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\properties.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\ldapbp.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\axis2.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\log4j-1.2.16.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\db2jcc.jar;D:\Program Files\IBM\We

bSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\db2jcc_license_cu.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\oraclethin.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\sqljdbc.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jdom.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\axis.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\axis-ant.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\commons-disc

[heartche88]

overy.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\commons-logging.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jaxrpc.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\saaj.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\remoteaccess.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\platform-model.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\ssh.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\m aximo.ear\EarContent\lib\maxcom.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\icu4j.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jython.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\commons-net-1.4.0.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jsr181.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\api-client.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\api-dep.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a310 4a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\oal-api.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\oal-topomgr.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\oal-common.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\edm-server.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\api-dl.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\json4j.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jviews-gantt.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr 01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jviews-diagrammer.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jviews-framework-lib.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jhbasic-2.0_05.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\contentloader.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\oslcquery.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\commons-codec.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\oauth.jar; D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\commons-httpclient.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\tdb-0.8.7-patched.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\jena-2.6.3-patched.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\slf4j-log4j12-1.6.4.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\slf4j-api-1.6.4.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\iri-0.8.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_ 149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\sdb-1.3.2.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\maximo.ear\EarContent\lib\xercesImpl-2.7.1.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\mboejb\ImportedClasses;D:\Program Files\IBM\WebSphere\AppServer\plugins\com.ibm.ws.wsadie\marshall.jar;D:\Program Files\IBM\WebSphere\AppServer\plugins\com.ibm.ws.wsadie\wsatlib.jar;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\mboejbclient\build\classes;D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\wstemp\app_149a3104a3b\dpl\dpl_MAXIMO._\mboejbclient\ImportedClasses -iiop -always -d C:\Windows\TEMP\ejb.1308785070775929531.tmp psdi.iface.gateway.EJSRemoteStatelessenterpriseserviceHome_9dde8a69 psdi.iface.gateway.EJSRemoteStatelessenterpriseservice_9dde8a69 psdi.iface.mos.EJSRemoteS tatelessmosserviceHome_43551b5c psdi.iface.mos.EJSRemoteStatelessmosservice_43551b5c psdi.iface.action.EJSRemoteStatelessactionserviceHome_05493ca6 psdi.iface.action.EJSRemoteStatelessactionservice_05493ca6 psdi.iface.workflow.EJSRemoteStatelesswfserviceHome_f547307a psdi.iface.workflow.EJSRemoteStatelesswfservice_f547307a psdi.iface.webservices.EJSRemoteStatelessjaxwsclientHome_85732b33 psdi.iface.webservices.EJSRemoteStatelessjaxwsclient_85732b33 psdi.security.ejb.EJSRemoteStatelessaccesstokenproviderHome_87daf10b psdi.security.ejb.EJSRemoteStatelessaccesstokenprovider_87daf10b 正在复制文件 正在复制文件

[heartche88]

Client Uri: mboejbclient.jar JVMDUMP006I 正在处理转储事件“systhrow”，详细信息“java/lang/OutOfMemoryError”- 请稍候。 JVMDUMP032I JVM 使用“D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\heapdump.20141112.161852.3236.0001.phd”来请求 Heap 转储以响应事件 JVMDUMP010I Heap 转储已写入 D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\heapdump.20141112.161852.3236.0001.phd JVMDUMP032I JVM 使用“D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\javacore.20141112.161852.3236.0002.txt”来请求 Java 转储以响应事件 JVMDUMP010I Java 转储已写入 D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\javacore.20141112.161852.3236.0002.txt JVMDUMP032I JVM 使用“D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\Snap.20141112.161852.3236.0003.trc”来请求 Snap 转储以响应事件 JVMDUMP010I Snap 转储已写入 D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\Snap.20141112.161852.3236.0003.trc JVMDUMP013I 已处理转储事件“systhrow”，详细信息：“java/lang/OutOfMemoryError”。 JVMDUMP006I 正在处理转储事件“systhrow”，详细信息“java/lang/OutOfMemoryError”- 请稍候。 JVMDUMP032I JVM 使用“D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\heapdump.20141112.161854.3236.0004.phd”来请求 Heap 转储以响应事件 JVMDUMP010I Heap 转储已写入 D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\heapdump.20141112.161854.3236.0004.phd JVMDUMP032I JVM 使用“D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\javacore.20141112.161854.3236.0005.txt”来请求 Java 转储以响应事件 JVMDUMP010I Java 转储已写入 D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\javacore.20141112.161854.3236.0005.txt JVMDUMP032I JVM 使用“D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\Snap.20141112.161854.3236.0006.trc”来请求 Snap 转储以响应事件 JVMDUMP010I Snap 转储已写入 D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\Snap.20141112.161854.3236.0006.trc JVMDUMP013I 已处理转储事件“systhrow”，详细信息：“java/lang/OutOfMemoryError”。 An unexpected exception was thrown. Halting execution. Shutting down workbench. Error executing deployment: java.lang.OutOfMemoryError. Error is null. java.lang.OutOfMemoryError at org.eclipse.emf.common.notify.impl.NotificationChainImpl.newData(NotificationChainImpl.java:57) at org.eclipse.emf.common.util.BasicEList.(BasicEList.java:73) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.createNotificationChain(NotifyingListImpl.java:258) at org.eclipse.emf.common.notify.impl.NotifyingListImpl.clear(NotifyingListImpl.java:1130) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.save(ArchiveImpl.java:1094) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl.save(ModuleFileImpl.java:161) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.extractTo(ArchiveImpl.java:473) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.getWarFileClasspath(BatchExtension.java:2305) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.processEjbReferences(BatchExtension.java:2809) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.runEarDeploy(BatchExtension.java:515) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.run(BatchExtension.java:338) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension$RunDeploy.execute(BatchExtension.java:303) at com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.run(BatchExtension.java:266) 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 org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) 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 com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:494) at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:114) at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:107) at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:348) at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:310) EJBDeploy level: @build@ ADMA5007I: The EJBDeploy program completed on file D:\Program Files\IBM\WebSphere\AppServer\profiles\ctgDmgr01\wstemp\514564614\upload\maximo.ear ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.websphere.management.exception.AdminException: ADMA0062E: The EJBDeploy program issued the following error messages: [An unexpected exception was thrown. Halting execution.] ADMA5011I: The cleanup of the temp directory for application MAXIMO is complete. ADMA5014E: The installation of application MAXIMO failed. The installation of application MAXIMO failed. To work with installed applications, click the "Manage Applications" link. Manage Applications PS：服务器上内存为64G，应用程序-进程-虚拟机里设置的 初始化，和最大的分别为 1024,2048 deployment manager 里 进程-虚拟机 设置的 也是 1024,2048 求高手指点！

[heartche88]

多核服务器哟！

[humanity]

那个 1024, 2048 的单位是 m 吧？ 你有 64G 内存，却只设定了 最多 2G 给它用？ 按理说如果上面当前只运行这一个程序，2G也是够的，毕竟这个程序还没有开始运行因此不会占太多的内存（运行之后可能有各种静态变量缓存占了内存嘛）。

[number1170196649]

兄弟，你也搞Maximo的？Maximo部署可是小心啊，不过我建议安装目录下不要有空格。如，Program Files

[u010968637]

不错不错，真的很好

[Giberson1]

常见原因的有以下几种： 1.内存中加载的数据量过于庞大，如一次从数据库取出过多数据； 2.集合类中有对对象的引用，使用完后未清空，使得JVM不能回收； 3.代码中存在死循环或循环产生过多重复的对象实体； 4.使用的第三方软件中的BUG； 5.启动参数内存值设定的过小； 常见错误提示： 1.tomcat:java.lang.OutOfMemoryError: PermGen space 2.tomcat:java.lang.OutOfMemoryError: Java heap space 3.weblogic:Root cause of ServletException java.lang.OutOfMemoryError 4.resin:java.lang.OutOfMemoryError 5.java:java.lang.OutOfMemoryError 解决； 1.应用服务器提示错误的解决： 把启动参数内存值设置足够大。 2.Java代码导致错误的解决： 重点排查以下几点： 1)检查代码中是否有死循环或递归调用。 2)检查是否有大循环重复产生新对象实体。 3)检查对数据库查询中，是否有一次获得全部数据的查询。一般来说，如果一次取十万条记录到内存，就可能引起内存溢出。这个问题比较隐蔽，在上线前，数据库中数据较少，不容易出问题，上线后，数据库中数据多了，一次查询就有可能引起内存溢出。因此对于数据库查询尽量采用分页的方式查询。 4 )检查List、MAP等集合对象是否有使用完后，未清除的问题。List、MAP等集合对象会始终存有对对象的引用，使得这些对象不能被GC回收。 案例： 1.hibernate查询数据时，一次查询过多的数据，后来调整了该部分的代码，每次只取出指定量的数据，成功的解决该问题。 2.在做压力测试时，出现OutOfMemoryError，发现session的资源一直没有被释放产生的，最好通过session的invalidate()方法将session的资源释放。 3.程序中出现死循环。 4.tomcat部署、运行出现OutOfMemoryError，加大内存参数值，解决此问题。 tomcat中java.lang.OutOfMemoryError: Java heap space异常处理 一、Heap size JVM堆的设置是指java程序运行过程中JVM可以调配使用的内存空间的设置.JVM在启动的时候会自动设置Heap size的值， 其初始空间(即-Xms)是物理内存的1/64，最大空间(-Xmx)是物理内存的1/4。可以利用JVM提供的-Xmn -Xms -Xmx等选项可 进行设置。Heap size 的大小是Young Generation 和Tenured Generaion 之和。 提示：在JVM中如果98％的时间是用于GC且可用的Heap size 不足2％的时候将抛出此异常信息。 提示：Heap Size 最大不要超过可用物理内存的80％，一般的要将-Xms和-Xmx选项设置为相同，而-Xmn为1/4的-Xmx值。 二、解决方法：手动设置Heap size 修改TOMCAT_HOME/bin/catalina.sh 在“echo "Using CATALINA_BASE: $CATALINA_BASE"”上面加入以下行： JAVA_OPTS="-server -Xms800m -Xmx800m -XX:MaxNewSize=256m" tomcat中java.lang.OutOfMemoryError: PermGen space异常处理 一、PermGen space PermGen space的全称是Permanent Generation space,是指内存的永久保存区域, 这块内存主要是被JVM存放Class和Meta信息的,Class在被Loader时就会被放到PermGen space中, 它和存放类实例(Instance)的Heap区域不同,GC(Garbage Collection)不会在主程序运行期对 PermGen space进行清理，所以如果你的应用中有很多CLASS的话,就很可能出现PermGen space错误, 这种错误常见在web服务器对JSP进行pre compile的时候。如果你的WEB APP下都用了大量的第三方jar, 其大小 超过了jvm默认的大小(4M)那么就会产生此错误信息了。 解决方法： 手动设置MaxPermSize大小 修改TOMCAT_HOME/bin/catalina.sh 在“echo "Using CATALINA_BASE: $CATALINA_BASE"”上面加入以下行： JAVA_OPTS="-server -XX:PermSize=64M -XX:MaxPermSize=128m 建议：将相同的第三方jar文件移置到tomcat/shared/lib目录下，这样可以达到减少jar 文档重复占用内存的目的。 weblogic中java.lang.OutOfMemoryError异常处理 错误提示： "Root cause of ervletException java.lang.OutOfMemoryError" 解决办法： 调整bea/weblogic/common中CommEnv中参数 　　 :sun 　　if "%PRODUCTION_MODE%" == "true" goto sun_prod_mode 　　set JAVA_VM=-client 　　set MEM_ARGS=-Xms256m -Xmx512m -XX:MaxPermSize=256m 　　set JAVA_OPTIONS=%JAVA_OPTIONS% -Xverify:none 　　goto continue 　　:sun_prod_mode 　　set JAVA_VM=-server 　　set MEM_ARGS=-Xms256m -Xmx512m -XX:MaxPermSize=256m 　　goto continue

[小龙在线]

我们一般都是先安装一个空的应用程序，然后再把实际应用程序覆盖过去

[lz_bobo]

不错不错，真的很好