OutofMemory at deployment
Hello
I wonder if anyone has a similar to the one I am experiencing.
When I deploy and ear file on production environment the ejb deploys but when
the war file tries to get deployed I get this error .
Start server side stack trace:
java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:105)
at java.util.jar.JarFile.<init>(JarFile.java:110)
at java.util.jar.JarFile.<init>(JarFile.java:52)
at weblogic.servlet.internal.WebAppServletContext.getRoot(WebAppServletContext.java:1088)
at weblogic.servlet.internal.WebAppServletContext.setActive(WebAppServletContext.java:4705)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:510)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1655)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1092)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:1514)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:34)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
Even when I restart the server I still get the same problem .I delete the .wlndelete
directory and restart . Sometimes this resolves the problem but not all the time
. It can take atleast three attempts to restart the server before the war file
is deployed . This only happens in the production environment . I have other environments
with the same configuration but I do not encounter any problems in the other environments
. The only difference between the production environment and the others is the
fact there are a few hundred users in production .
Any ideas how I can resolve this problem ?
Also I am looking for a memory profiler I have tried to use OptimizeIt and JProbe
which really slowed the system down to the point of no use.
thanks
Sarnie
Very difficult to say without more information. I'd start by running
the jvm with -verbose:gc. I'd first want to know if you were exhausing
the java heap.
If the heap space looks fine, I'd probably next try to bump of the perm
space and see if that helps.
-- Rob
sarnie wrote:
Hello
I wonder if anyone has a similar to the one I am experiencing.
When I deploy and ear file on production environment the ejb deploys but when
the war file tries to get deployed I get this error .
Start server side stack trace:
java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:105)
at java.util.jar.JarFile.<init>(JarFile.java:110)
at java.util.jar.JarFile.<init>(JarFile.java:52)
at weblogic.servlet.internal.WebAppServletContext.getRoot(WebAppServletContext.java:1088)
at weblogic.servlet.internal.WebAppServletContext.setActive(WebAppServletContext.java:4705)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:510)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1655)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1092)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:1514)
at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:34)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
Even when I restart the server I still get the same problem .I delete the .wlndelete
directory and restart . Sometimes this resolves the problem but not all the time
It can take atleast three attempts to restart the server before the war file
is deployed . This only happens in the production environment . I have other environments
with the same configuration but I do not encounter any problems in the other environments
The only difference between the production environment and the others is the
fact there are a few hundred users in production .
Any ideas how I can resolve this problem ?
Also I am looking for a memory profiler I have tried to use OptimizeIt and JProbe
which really slowed the system down to the point of no use.
thanks
Sarnie
Similar Messages
-
PermGen space Error in Weblogic Server
Hi,
I am facing problem with Premgen space; java.lang.outofMemory+, while deploying (Importing the jar file in the server) my service in the Server, I need to restart the Server each and every time due to this problem.
I am currently using Weblogic 10gR3(10.3). My deployment jar contains about 4000 classes, as java code in the jar cannot able to detect the necessary classes from the server library and even from the Java lib present in the Weblogic tool.
i am in need of immediate solution.What are the values you have used?
In my case I have set the values to PermSize=512m and MaxPermSize=1024m
Try increasing values but be careful when you are increasing these values. -
OutOfMemory Error when deploying application in WL10
I've got an application that I am able to deploy from the WL9 console without hickups. But when I try to deploy it through WL10 console, it hangs and eventualy throws an OutOfMemory error. I've tried doubling the memory I allocate to WL but this does nothing. I can manually edit the config.xml to deploy the application and it works but I am unable to expand or view it from the console without getting the same OutOfMemory error. Any ideas?
I ran a profiler on wl when getting the OutOfMemory error and the class weblogic.j2ee.descriptor.wl.WeblogicEjbJarBeanDConfig seems to be the culprit. Does WL10 load EJBs differently into memory than WL9?
Also, I added the -verbosegc option to my vm args and it looks like the eden space isnt getting released. Not sure what that is supposed to tell me...
1318.268: [Full GC {Heap before gc invocations=166:
def new generation total 56576K, used 56576K [0xccc00000, 0xd04e0000, 0xd04e0000)
eden space 54912K, 100% used [0xccc00000, 0xd01a0000, 0xd01a0000)
from space 1664K, 100% used [0xd01a0000, 0xd0340000, 0xd0340000)
to space 1664K, 0% used [0xd0340000, 0xd0340000, 0xd04e0000)
tenured generation total 466048K, used 466048K [0xd04e0000, 0xecc00000, 0xecc00000)
the space 466048K, 100% used [0xd04e0000, 0xecc00000, 0xecc00000, 0xecc00000)
compacting perm gen total 83456K, used 83263K [0xecc00000, 0xf1d80000, 0xf8c00000)
the space 83456K, 99% used [0xecc00000, 0xf1d4fdf0, 0xf1d4fe00, 0xf1d80000)
No shared spaces configured.
1318.268: [Tenured: 466048K->466048K(466048K), 6.4704001 secs] 522624K->513170K(522624K), [Perm : 83263K->83263K(83456K)]Heap after gc invocations=167:
def new generation total 56576K, used 47122K [0xccc00000, 0xd04e0000, 0xd04e0000)
eden space 54912K, 85% used [0xccc00000, 0xcfa04970, 0xd01a0000)
from space 1664K, 0% used [0xd01a0000, 0xd01a0000, 0xd0340000)
to space 1664K, 0% used [0xd0340000, 0xd0340000, 0xd04e0000)
tenured generation total 466048K, used 466048K [0xd04e0000, 0xecc00000, 0xecc00000)
the space 466048K, 100% used [0xd04e0000, 0xecc00000, 0xecc00000, 0xecc00000)
compacting perm gen total 83456K, used 83263K [0xecc00000, 0xf1d80000, 0xf8c00000)
the space 83456K, 99% used [0xecc00000, 0xf1d4fdf0, 0xf1d4fe00, 0xf1d80000)
No shared spaces configured.
Edited by kadire at 06/20/2008 7:41 AM -
While deploying EJB, OutOfMemory error occurred
While deploying & re-deploying EJB many times(maybe over 100 times), in admin-server, OutOfMemory error occurred.
Actually 7~8 people deployed several EJBs remotely.
After I increased heap memory size to 1G of admin-server, interval was more longer, but anyway OutOfMemory error occurred. I should restart admin-server after that error.
Log message as follows::
=========================================
[18/Sep/2003:12:38:54] INFO ( 9510): ADM1041:Sent the event to instance:[ModuleDeployEvent -- redeploy ejb/rh34]
[18/Sep/2003:12:38:54] WARNING ( 9510): ADM1046:Notification failed
[18/Sep/2003:12:38:57] INFO ( 9510): ADM1058:Restarting the server instance : [rhlfInstance]
[18/Sep/2003:12:46:08] INFO ( 9510): ADM6002:Received remote administration request
[18/Sep/2003:12:46:11] SEVERE ( 9510): CORE4007: Internal error: Unexpected Java exception thrown (unknown exception, no description), stack:
java.lang.OutOfMemoryError
[18/Sep/2003:12:46:27] INFO ( 9510): ADM6002:Received remote administration request
[18/Sep/2003:12:49:58] INFO ( 9510): ADM6002:Received remote administration request
[18/Sep/2003:12:52:18] INFO ( 9510): ADM6002:Received remote administration request
[18/Sep/2003:12:52:18] SEVERE ( 9510): StandardWrapperValve[AdminAPIEntryServlet]: Servlet.service() for servlet AdminAPIEntryServlet threw exception
javax.servlet.ServletException: Servlet execution threw an exception
at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:742)
at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
----- Root Cause -----
java.lang.OutOfMemoryErrorRepeated changes applied to any instance eventually results in an out of memory error.
The Admin Server keeps a record of all changes performed to the system, which requires memory. This change record (but not the changes themselves) is discarded during a reconfiguration, thus releasing the memory for use.
Use the asadmin reconfig command periodically to discard old change records which was being kept in memory. -
Geting "Incorrect client ID.The stub is not connected yet" during deploying
Hai all,
I am unable to deploy a J2EE application from Deploy Tool. The following trace is comg in defaultTrace.trc.2
#1.5#000D9D9FAF62003C0000000900000F080003FC0472DB309D#1121520967258#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Guest#2##sap_J2E_1009250#Guest#097b3220f5fd11d9b557000d9d9faf62#Finalizer##0#0#Error#1#/System/Server#Plain#ID:Can't send inform message.: Incorrect client ID. The stub is not connected yet.#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle##
#1.5#000D9D9FAF62003C0000000A00000F080003FC0472DB33DE#1121520967258#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Guest#2##sap_J2E_1009250#Guest#097b3220f5fd11d9b557000d9d9faf62#Finalizer##0#0#Error#1#/System/Server#Plain###Incorrect client ID. The stub is not connected yet.#
#1.5#000D9D9FAF62003C0000000B00000F080003FC0472DB3A15#1121520967258#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4.com.sap.engine.services.rmi_p4.StubImpl p4_finalize#Guest#2##sap_J2E_1009250#Guest#097b3220f5fd11d9b557000d9d9faf62#Finalizer##0#0#Error##Plain###
com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Incorrect client ID. The stub is not connected yet.
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:860)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:853)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.reply(P4SessionProcessor.java:169)
at com.sap.engine.services.rmi_p4.StubImpl.p4_finalize(StubImpl.java:221)
at com.sap.engine.services.rmi_p4.StubBase.finalize(StubBase.java:121)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
#1.5#000D9D9FAF62003C0000000C00000F080003FC0472DB3F36#1121520967258#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Guest#2##sap_J2E_1009250#Guest#097b3220f5fd11d9b557000d9d9faf62#Finalizer##0#0#Error#1#/System/Server#Plain#ID:Can't send inform message.: Incorrect client ID. The stub is not connected yet.#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle##
#1.5#000D9D9FAF62003C0000000D00000F080003FC0472DB423D#1121520967258#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Guest#2##sap_J2E_1009250#Guest#097b3220f5fd11d9b557000d9d9faf62#Finalizer##0#0#Error#1#/System/Server#Plain###Incorrect client ID. The stub is not connected yet.#
#1.5#000D9D9FAF62003C0000000E00000F080003FC0472DB47AA#1121520967258#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4.com.sap.engine.services.rmi_p4.StubImpl p4_finalize#Guest#2##sap_J2E_1009250#Guest#097b3220f5fd11d9b557000d9d9faf62#Finalizer##0#0#Error##Plain###
com.sap.engine.services.rmi_p4.exception.P4BaseIOException: Incorrect client ID. The stub is not connected yet.
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:860)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:853)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.reply(P4SessionProcessor.java:169)
at com.sap.engine.services.rmi_p4.StubImpl.p4_finalize(StubImpl.java:221)
at com.sap.engine.services.rmi_p4.StubBase.finalize(StubBase.java:121)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
#1.5#000D9D9FAF62003B0000000100000F080003FC047395DF47#1121520979492#com.sap.engine.compilation##com.sap.engine.compilation.ExternalCompiler.compile()#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Plain###Error while compiling :
java.io.IOException: CreateProcess: javac -encoding Cp1252 -d C:/usr/sap/J2E/JC00/j2ee/cluster/server0/apps/sap.com/onlyear/EJBContainer/temp/temp1121520967445 -classpath .;./bin/system/frame.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/jms/jms.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/tcsecssl/iaik_jsse.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/webservices_lib/saaj-api.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/tcsecssl/iaik_smime.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/add_ejb/add_ejb.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/servlet/servlet.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/services/naming/naming.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/webservices_lib/webservices_lib.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/interfaces/resourcecontext_api/resourcecontext_api.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/ext/tcsecssl/w3c_http.jar;C:/usr/sap/J2E/JC00/j2ee/cluster/server0/bin/interfaces/webservices/webservices_api.jar;C:/us?
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:66)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at java.lang.Runtime.exec(Runtime.java:491)
at java.lang.Runtime.exec(Runtime.java:457)
at com.sap.engine.compilation.ExternalCompiler.compile(ExternalCompiler.java:65)
at com.sap.engine.services.ejb.util.AdminUtils.compile(AdminUtils.java:449)
at com.sap.engine.services.ejb.deploy.DeployAdmin.deploySingleJar(DeployAdmin.java:625)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:266)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2093)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:1015)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:594)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:300)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:331)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2910)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:451)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:286)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:172)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:104)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
#1.5#000D9D9FAF62003B0000000900000F080003FC04739BCB45#1121520979883#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Plain###com.sap.engine.services.rmi_p4.DispatchImpl _runInternal Cannot deploy application sap.com/onlyear..
Reason: Exception during generation of components of application sap.com/onlyear in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/onlyear in container EJBContainer.#
#1.5#000D9D9FAF62003B0000000A00000F080003FC04739BD41D#1121520979883#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4.com.sap.engine.services.rmi_p4.DispatchImpl runInternal#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngineApplication_Thread[impl:3]_32##0#0#Error##Plain###
java.rmi.RemoteException: Cannot deploy application sap.com/onlyear..
Reason: Exception during generation of components of application sap.com/onlyear in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/onlyear in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:466)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1511)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:286)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:172)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:104)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/onlyear in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:1021)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:594)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:300)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:331)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2910)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:451)
... 10 more
Caused by: java.lang.NullPointerException
at com.sap.engine.compilation.ExternalCompiler.getErrorMessage(ExternalCompiler.java:123)
at com.sap.engine.services.ejb.util.AdminUtils.compile(AdminUtils.java:451)
at com.sap.engine.services.ejb.deploy.DeployAdmin.deploySingleJar(DeployAdmin.java:625)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:266)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2093)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:1015)
... 15 more
#1.5#000D9D9FAF62003B0000000D00000F080003FC04739BDA8D#1121520979883#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/Server#Plain#ID:011403: Cannot deploy application sap.com/onlyear..
Reason: Exception during generation of components of application sap.com/onlyear in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/onlyear in container EJBContainer.#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle##
#1.5#000D9D9FAF62003B0000000E00000F080003FC04739BDCAE#1121520979883#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#/System/Server#Plain###Cannot deploy application sap.com/onlyear..
Reason: Exception during generation of components of application sap.com/onlyear in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/onlyear in container EJBContainer.#
#1.5#000D9D9FAF62003B0000000F00000F080003FC04739BDEA3#1121520979883#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Plain###TraceException in DispatchImpl...#
#1.5#000D9D9FAF62003B0000001000000F080003FC04739BDFA7#1121520979883#com.sap.engine.services.rmi_p4##com.sap.engine.services.rmi_p4#Administrator#32###Administrator#8c8d9e90f5fe11d99d3d000d9d9faf62#SAPEngine_Application_Thread[impl:3]_32##0#0#Error##Plain###P4:SAPEngine_Application_Thread[impl:3]_32: TraceException in DispatchImpl...#
The above trace repeating all the time when I try to deploy.
Can any body tell whether is it a configuration problem or any application problem. Also on the same server another j2ee application is deploying successfully.
Thanks a lot,
Gangadhar.Hai,
Thanks Brandelik, actually the problem was coming because of java.lang.outOfMemory exception during compilation time.
As of now I am not able to fix that problem. I am changing all the available options for memory settings.
Anybody please help me how to set the memory parameters for deploying an application. My application needs minimum of -Xmx512m for deployment on oracle10g server.
Thanx,
Gangadhar. -
SSAS Tabular : MDX query goes OutOfMemory for a larger dataset
Hello all,
I am using SSAS 2012 Tabular to build the cube to support the organizational reporting requirements. Right now the server is Windows 2008 x64 with 16GB of Ram installed. I have the following MDX query. What this query does is get the member caption of the
“OrderGroupNumber” non-key attribute as a measure where order group numbers pertain to a specific day and which occurs in specific seconds of a day. As I want to find in which second I have order group numbers, I cross the time dimension’s members with a specific
day and filter the tuples using the transaction count. The transaction count is a non-zero value if an Order Group Number occurs within a specific second of a selected day.
At present “TransactionsInflight].[OrderGroupNumber].[OrderGroupNumber]” has 170+ million members (Potentially this could grow rapidly) and time dimension has 86400 members.
WITH
MEMBER [Measures].[OrderGroupNumber]
AS IIF([Measures].[Transaction Count] > 0, [TransactionsInflight].[OrderGroupNumber].CURRENTMEMBER.MEMBER_CAPTION,
NULL)
SELECT
NON EMPTY{[TransactionsInflight].[OrderGroupNumber].[OrderGroupNumber].MEMBERS}
ON COLUMNS,
{FILTER(([Date].[Calendar Hierarchy].[Date].&[2012-07-05T00:00:00], [Time].[Time].[Time].MEMBERS),
[Measures].[Transaction Count] > 0) } ON
ROWS
FROM [OrgDataCube]
WHERE [Measures].[OrderGroupNumber]
After I run this query it reaches to a dead-end and freezes the server (Sometimes SSAS server throws OutOfMemory exception but sometimes it does not). Even though I have 16GB of memory it uses all the memory and doing nothing. I have to do a hard-reset against
the server to get the server online. Even I limit the time members using the “:” range operator still the machine freeze. I have run out of solutions to fine-tune the design. Could you guys provide me some guidelines to optimize this query? I am willing to
do a design change if it is necessary.
Thanks and best regards,
ChandimaHi Greg,
Finally I found the problem why the query goes out of memory in tabular mode. I guess this information will helpful for others and I am posting my findings.
Some of the non-key attribute columns in the tabular model tables (mainly the tables which form dimensions) do not contain pretty names. So for the non-key attribute columns which I need to provide pretty names I renamed the columns to something else.
For an example, in my date dimension there is a non-key attribute named “DateAltKey”. This is the date column which I am using. As this is not pretty to the client tools I renamed this column as “Date” inside the designer (Dimension
design screen). I deployed the cube, processed the cube and no problem.
Now here comes the fun part. For every table, inside the Tables node (Tabular SSAS Database > Tables) you can view the partition details. You have single partition per dimension table if you do not create extra partitions. I opened the partitions screen
and clicked on the “Edit” icon and performed a Syntax Check. Surprisingly it failed. It complains about the renamed column. It complained “Date” cannot be found in source. So I realized that I cannot simply rename the columns like that.
After that I created calculated columns (with a pretty name) for all the columns which complained and all the source columns to the calculated columns were hid from the client tools. I deployed the cube, processed the cube and performed a
syntax check. No errors and everything were perfect.
I ran the query which gave me trouble and guess what... it executed within 5 seconds. My problem is solved. I really do not know who did this improve the performance but the trick worked for me.
Thanks a lot for your support.
Chandima -
Deploying a war file in weblogic7.0.1
Iam using lomboz as a plugin for web development . when i deploy from eclipse it creates a war file and drops it in to the weblogic application directory .but weblogic takes a lot of time to deploy , it keeps showing the following message
<Dec 13, 2004 2:45:38 PM IST> <Notice> <Application Poller> <149404> <Activate application _appsdrver - Running>
Is there any way we can reduce the deployment time .
Most of the time it shows OutOfMemory and that is it . i need to restart the server . Can any one help me to correct this in weblogic 7.0.1 serverBabu,
There are a lot of dependencies involved. app severes before 10g are not generic j2ee server. what kind of files are you putting in ur war file?
--Shiv -
Bad Performance/OutOfMemory Error in CMP Entity Bean with Large DB
Hello:
I have an CMP Entity deployed on WLS 7.0
The entity bean maps to a table that has 97,480 records.
It has a finder: findAll() -- SELECT OBJECT(e) FROM Equipment e
I have a JSP client that invokes the findALL()
The performance is very poor ~ 150 seconds just to perform the findAll() - (Benchmark
from within the JSP code)
If more than one simultaneous call is made then I get outOfMemory Error.
WLS is started with max memory of 512MB
EJB is deployed with <max-beans-in-cache>100000</max-beans-in-cache>
(without max-beans-in-cache directive the performance is worse)
Is there any documentation available to help us in deploying CMP Entity Beans
with very large number of records (instances) ?
Any help is greatly appreciated.
Regards
RajanHi
You should use a Select Method, it does support cursors.
Or a Home Select Method combination.
Regards
Thomas
WLS is started with max memory of 512MB
EJB is deployed with <max-beans-in-cache>100000</max-beans-in-cache>>
(without max-beans-in-cache directive the performance is worse)>
Is there any documentation available to help us in deploying CMP
Entity Beans with very large number of records (instances) ? Any help
is greatly appreciated.>
Regards>
Rajan>
>
"Rajan Jena" <[email protected]> schrieb im Newsbeitrag
news:3dadd7d1$[email protected]..
>
Hello:
I have an CMP Entity deployed on WLS 7.0
The entity bean maps to a table that has 97,480 records.
It has a finder: findAll() -- SELECT OBJECT(e) FROM Equipment e
I have a JSP client that invokes the findALL()
The performance is very poor ~ 150 seconds just to perform the findAll() -(Benchmark
from within the JSP code)
If more than one simultaneous call is made then I get outOfMemory Error.
WLS is started with max memory of 512MB
EJB is deployed with <max-beans-in-cache>100000</max-beans-in-cache>
(without max-beans-in-cache directive the performance is worse)
Is there any documentation available to help us in deploying CMP EntityBeans
with very large number of records (instances) ?
Any help is greatly appreciated.
Regards
Rajan -
Deploying simple HTML page to WLS 10.3.6 fails with HTTP response code: 502
- I created a simple HTML page and want to test deployment to WLS 10.3.6 on Linux. I created WAR file and when using JDev 11.1.1.4.0 to deploy to WebLogic Server, it fails to deploy. Full errors/messages are:
[04:40:56 PM] ---- Deployment started. ----
[04:40:56 PM] Target platform is (Weblogic 10.3).
[04:40:59 PM] Retrieving existing application information
[04:40:59 PM] Running dependency analysis...
[04:40:59 PM] Building...
[04:40:59 PM] Deploying profile...
[04:40:59 PM] Wrote Web Application Module to C:\JDeveloper\mywork\Simpe_HTML\Project1\deploy\SimpleHTML.war
[04:41:01 PM] Deploying Application...
[04:41:01 PM] Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\DOCUME~1\NGOLDR~1.LAT\LOCALS~1\Temp\SimpleHTML.war' for the application 'SimpleHTML' could not be loaded to the server 'http://dupe:7031/bea_wls_deployment_internal/DeploymentService'.
Server returned HTTP response code: 502 for URL: http://dupe:7031/bea_wls_deployment_internal/DeploymentService
[04:41:01 PM] See server logs or server console for more details.
[04:41:01 PM] weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'C:\JDeveloper\mywork\Simpe_HTML\Project1\deploy\SimpleHTML.war' to 't3://dupe:7031'
[04:41:01 PM] #### Deployment incomplete. ####
[04:41:01 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
- The Application Server connection is accessible within JDev. 'dupe' is my server name and it's running RH 5.4
- Any help or suggestions appreciated, although I've already asked Mr. Google without success.
Thanks in advance,
NevilleHTTP response code 502 means temporarily overloaded.
I would say that we have to check the deployment error on the weblogic server logs located at <Domain_Home>\servers\dupe\logs\dupe.log
Check for any errors like OutOfMemory etc OR any deployment failures.
If possible, try accessing the console at http://dupe:7031/console
Check if you are able to successfully deploy your application using the console.
From the error it looks like the "dupe" server might not be healthy. So, the log file would really help here to get clues into the root cause.
Arun -
Problem in deploying EJBs (More than 390) in weblogic-BEA says JDK issue!!!
Our application had 390 EJBs before the current build. It was running fine on Weblogic 6.1-SP4 with JDK 1.3.1_08.
In the current build, 3 EJBs were introduced and the Weblogic server started giving deployment problems. We then came across the Weblogic Bug stating the magic Number of 390 and delegating it to a SUN Bug. But, contrary to the SUN bug which says of a OutofMemory issue, we were not getting any OutOfMemory error.
Then, just to test the 390 number, we cut downed on the number of EJBs reducing the number to 388, in a test environment. EJBs got deployed without problem. Then we added 3 EJBs (increasing the EJB count to 391), and Weblogic server started giving Deployment problem in a EJB which was one of the 388 that were running fine earlier.But, now also there was no OutOfMemory error. Then we removed one of the newly added EJBs to bring the EJB count to 390. The Weblogic deployed the EJBs without error(even the one which was giving problem when EJB count was 391).
So, 390 seems to be the number but, contrary to BEA problem ID: 035884 which delegates the problem to SUN Bug ID:4390238 (Incidentally SUN has closed this bug as Non-reproducable), we are not getting any OutOfMemory error.
My questions to the JAVA community are:
1)Is the problem really related to JDK or Weblogic?
2)If it's a problem with JDK, then what should be done to fix it?
==========================================
A deployment error generated is pasted below:
==========================================
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException: Distributed Management [1 exceptions]
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:559)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Distributed update exception
- remote object: stellar:Location=primary-server,Name=primary-server,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@1d5ebc
- actionName: addDeployment
- params: [Ljava.lang.Object;@5f97ae
- signature: [Ljava.lang.String;@5f28a6
Distributed update exception
- remote object: stellar:Location=primary-server,Name=primary-server,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@1d5ebc
Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS]
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:367)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1087)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS]
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:367)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.management.DistributedOperationUpdateException:
Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:174)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy14.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy11.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
at weblogic.management.console.info.MBSo, 390 seems to be the number but, contrary to BEA
problem ID: 035884 which delegates the problem to SUN
Bug ID:4390238 (Incidentally SUN has closed this bug
as Non-reproducable), we are not getting any
OutOfMemory error.Did you check the server logs? There might be an OutOfMemoryError logged.
My questions to the JAVA community are:
1)Is the problem really related to JDK or Weblogic?Apparently, the problem is with the Weblogic. Did you try deploying the same number on some higher version of Weblogic? (7.0 for instance)
2)If it's a problem with JDK, then what should be
done to fix it?Check the bug database for the same bug id. There is a workaround posted. The evaluation comments are also hinting at using the suggested VM options.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4390238 -
JSF (RI) app hot-deploy memory leak
I have a standard JSF (RI) based web app that appears to be working just fine in terms of functionality. However, I believe that there is a memory leak associated with the sort of frequent hot-deploy cycles that are typical during a normal development cycle. I have been monitoring the app via the jvmstat 3.0 tools and have witnessed NO memory growth in the young or old generation areas - regardless of useage pattern. All of the growth seems to happen in the perm area of memory and be directly coincidental with the occurence of a deploy. Eventually, continued hot-deply cycles will result in an OutOfMemory error on the container - please note that continued and extensive use of the app WITHOUT the aforementioned hot-deploys does NOT result in the OutOfMemory error.
From my research so far, I have discovered the following thread:
http://forum.hibernate.org/viewtopic.php?t=935948&postdays=0&postorder=asc&start=75
It refers to a similar problem with hiberate (which I am NOT using) as well as a commons-logging and several others. From the looks of it, I strongly suspect that there may be an issue with JSF when it's implementation is bundled inside the WEB-INF/lib dir - i.e. inside the specific web app's ClassLoader.
Based on the above, I have implemented a SessionContextListener that invokes the org.apache.commons.logging.LogFactory.release() inside the contextDestroyed( ServletContextEvent e ) method. This does appear to free up some perm memory but there is still large growth that appears to be directly related to the FacesServlet initialization (navigation handlers, etc). I looked into calling the FacesContext.release() method which seems to have purpose similar to that of the LogFactory.release() method. However, at the time of the contextDestroyed() invocation, FacesContext.getCurrentInstance() always returns null, so I do not ever have an opportunity to invoke the release method that I am aware of. If my suspicions are correct, than I would likely be able to avoid this problem entirely by simply placing the JSF implementation jars in the conatiner's shared lib dir - instead of bundling it inside WEB-INF/lib. However, this is not an option for this container as multiple web apps (which require the flexibility to use differing JSF implementations and versions - i.e. RI vs MyFaces, etc) will run on this container.
I don't believe it is at all related to the problem at hand, but my container is JBoss 4.0.2.
Any and all assistance and suggestion will be greatly appreciated! Has anyone else seen this sort of behavior? Are there any work arounds or corrective actions?
TIAHas anyone else run into this? I'd greatly appreciate any assistance as I cannot seem to resolve this hot-deploy related leak.
-
Weblogic 8.1 SP4 getting Java.lang.outofMemory exception
Dear experts,
We are running WL8.1 SP4 on our Solaris 5.9 Server.
We want to do MQ implementatin on this server and for the same some kernel parameters were changed.
now our system has below parameters in /etc/system:
set semsys:seminfo_semmsl=1000
set semsys:seminfo_semvmx=32767
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmseg=2048
set shmsys:shminfo_shmmni=2048
set semsys:seminfo_semmni=1024
set semsys:seminfo_semaem=16384
set semsys:seminfo_semmap=1026
set semsys:seminfo_semmns=16384
set semsys:seminfo_semopm=100
set semsys:seminfo_semmnu=16384
set semsys:seminfo_semume=256
set msgsys:msginfo_msgmni=50
set msgsys:msginfo_msgmap=1026
set msgsys:msginfo_msgmax=4096
set msgsys:msginfo_msgmnb=65535
set msgsys:msginfo_msgtql=4096
set msgsys:msginfo_msgssz=16
set msgsys:msginfo_msgseg=8192
set rlim_fd_cur=10000
set rlim_fd_max=10000
and below in /etc/profile:
ulimit -s unlimited
ulimit -d unlimited
but as soon as server was rebooted and we tried to start the weblogic we got java.lang.outofmemory exception.
details as below:
admin_trace:
java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.zip.ZipFile.<init>(ZipFile.java:72)
at weblogic.servlet.internal.WebAppHelper.makeImplicitMapFromJars(WebAppHelper.java:479)
at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5436)
at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:5253)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:545)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:496)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:637)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:619)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3191)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1581)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.OutOfMemoryError]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2395)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
managed2_trace:
[java.lang.OutOfMemoryError].
java.lang.OutOfMemoryError
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:112)
at java.util.zip.ZipFile.<init>(ZipFile.java:72)
at weblogic.servlet.internal.WebAppHelper.makeImplicitMapFromJars(WebAppHelper.java:479)
at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5436)
at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:5253)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:545)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:496)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:637)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:619)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3191)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1581)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3029)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.OutOfMemoryError]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
need help to identify what exactly went wrong and where.
ThanksHi,
As you are using WLS8.1 It means your JDK will be JDK1.4 and there is a Bug already available with JDK1.4 for the Same issue ... Please find the below link:
http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4705373 (For Sun JDK1.4)
AND
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6373059 (For Sun JDK 1.5.0_05)
Please try to switch to JRockit JDK.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here) -
OutOfMemory issue with Axis 1.3 and Weblogic 10.3.6
Hi All,
We are facing OutofMemory issue (permGen memory) when we do hot deployment of a web application to Weblogic 10.3.6. We have hosted some webservices in this application using Axis 1.3. When i remove Axis configuration from application the issue is gone. Heap dump analysis is showing some weblogic ThreadLocale classes which are holding references to Axis generated classes. Did any one face this issue?. Or any patch provided by Oracle.
Thanks,
Arif.GlassFish V3 reports the following for the same issue - note: Illegal character ((CTRL-CHAR, code 31)):
SEVERE: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR, code 31))
at [row,col {unknown-source}]: [1,1]
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR, code 31))
at [row,col {unknown-source}]: [1,1]
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:292)
at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:93) -
OutOfMemory Exception. Please Help!
Hi,
We are deploying our application on Oracle10g AS , version 10.1.3. Very frequently we get OutOfMemory error even for a single user. We are using the default settings for Java Options. Please suggest a solution ASAP.
Regards,
SubhashiniYou can change the allocation of memory you give to OC4J when you start it up and increase it.
You should also try and identify which specific operation causes this - it might be that you are fetching too much info from the DB into the middle tier AS.
You can try and use the memory profiler in JDeveloper to track your application's memory allocation. -
OutOfMemoryError when many EJBs are deployed
WLS 7.0 fails frequently with this message:
"java.lang.OutOfMemoryError
<<no stack trace available>>"
My startup command includes these parameters:
-Xms256m -Xmx256m -XX:NewRatio=2 -verbose:gc
The output from the garbage collector indicates that only about 40-45MB of
the 256MB allocated to the VM is being used. The problem got much much worse
when I went from deploying ~5 CMP entity beans to about 100 CMP entity
beans. The entity beans aren't even used by the application -- it seems that
just deploying them gobbles up memory somehow. The Windows 2000 task manager
reports that the system has several hundred MB of free RAM (512MB physical
memory, 1GB virtual) when WLS dies, and the WLS java.exe process only uses
about 40-90MB. I've tried tweaking the -Xms, -Xmx, and -XX:NewRatio to no
avail. What can be going wrong? Please help!
Thanks,
Dave SmithHi all,
I'm using WLS5.1and also got the problem of "OutOfMemoryError".
Before the time of going crash, I saw in weblogic console that the "java heap
used" is nearly 100%, and some of ejb pool reach their max of 100.
For ejb pool reaching its maximun, I think this is no harm on it as it remains
very high even when system goes fine. They will be removed from cache(rather then
passivate) according to WLS doc.
However,my question is whether the "java heap used" shown in weblogic console
is the total heap or not AND am I falling into the problem of maxpermsize or newratio
stuff? How can I check it.
Any help will be highly appreciated.
Frank
"Praveen" <[email protected]> wrote:
>
Thank you for this useful information, this has helped us a lot even
with weblogic
5.1.
Regards,
Praveen.P
William Kemp <[email protected]> wrote:
There is a great article out on esupport that covers this in detail.
Search on
maxpermsize or OutOfMemory.
Bill
Cameron Purdy wrote:
Great! Sounds like a good item for an FAQ.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Dave Smith" <[email protected]> wrote in message
news:[email protected]...
Thank you Cameron! Increasing MaxPermSize works like a charm.
Here's more information for others who may be experiencing this
problem.
Follow these instructions from the WLS documentation. EditstartWebLogic.cmd
and add --XX:MaxPermSize=128m to the MEM_ARGS variable. The JVM
divides
its
memory into three generations: a part for young objects, a part
for
old
objects, and a part for permanent objects (objects that are never
garbage-collected, like Class objects) Based on this tip, I inferthat the
many class files for Entity beans are causing the permanent generationto
overflow. Increasing the size for permanent objects keeps WLS fromdying
when it loads a large number of classes.
Administration Guide : Starting and Stopping WebLogic Servers -
http://e-docs.bea.com/wls/docs70/adminguide/startstop.html
Informative JavaWorld article about garbage collection -
http://www.javaworld.com/javaworld/jw-01-2002/jw-0111-hotspotgc.html
From BEA docs:
Note: When starting WebLogic Server, JDK 1.3 may throw an OutOfMemoryerror
if you are trying to load a large number of classes. This error
occurs
even
though there appears to be plenty of memory available. If you encounter
a
java.lang.OutOfMemory error exception when you start WebLogic Server,
increase the value of the following JVM option:
java -XX:MaxPermSize=<value>
where <value> is some number in kilobytes.
For JDK1.3.1, the default value for MaxPermSize is 64m, where m
stands
for
megabytes.
"Cameron Purdy" <[email protected]> wrote in message
news:[email protected]...
Search on maxpermsize.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Dave Smith" <[email protected]> wrote in message
news:[email protected]...
WLS 7.0 fails frequently with this message:
"java.lang.OutOfMemoryError
<<no stack trace available>>"
My startup command includes these parameters:
-Xms256m -Xmx256m -XX:NewRatio=2 -verbose:gc
The output from the garbage collector indicates that only about
40-45MB
of
the 256MB allocated to the VM is being used. The problem got
much much
worse
when I went from deploying ~5 CMP entity beans to about 100
CMP
entity
beans. The entity beans aren't even used by the application
it
seems
that
just deploying them gobbles up memory somehow. The Windows 2000
task
manager
reports that the system has several hundred MB of free RAM (512MB
physical
memory, 1GB virtual) when WLS dies, and the WLS java.exe process
only
uses
about 40-90MB. I've tried tweaking the -Xms, -Xmx, and -XX:NewRatio
to
no
avail. What can be going wrong? Please help!
Thanks,
Dave Smith
Maybe you are looking for
-
How to set up 2 separate Game Center profiles on 2 separate iPads but same Apple ID
how can you set up 2 separate Game Center profiles on 2 different iPads with one Apple ID?
-
In the previous version of Firefox when I right clicked on a bookmark in the bookmark bar the IE Tab options would appear. They no longer do since I have moved to Version 4. It would be great to get this ability back.. Thanks
-
Conversion problem in condition records upload program (BDC tcode: XK15)
Hello everyone, I have downloaded few records from table A017 using key KUMNH (cond no), by the std program RVBTCI01 , i used three structures BRG00, BKOND1, BKOND2 and BKOND3 to download the records. into a file (.txt) on the server. now i upl
-
How to generate a new predefined PDF from certain form data?
Hi, I want to create a form (in either Word or PDF) with diffrerent sections for people to fill out. I then want them to easily turn some of the data from the form into a new predefined PDF template. For example, I have created a case study form for
-
What happened to ability to transfer files to mobile apps in iTunes?
I used to be able to transfer files from my Mac to my iPad app using iTunes. Since the ITunes update last Nov/Dec/ 2012, the process as explained in the help file no longer exists. Is there a new way to do it?