• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3864
  • Last Modified:

OutOfMemory Excpetion when deploying ejb.jar

Hi i have problem deploying EJB, i wonder if someone can help.

Iam using Weblogic 7 SP 1, after i have compiled and built my project, i go to
deploy it and i get the following error message !! I have tried increasing memory
allocated to EJBC to 512Mb, but this made no difference.

--------------------------------------------------------------------------------
        <java classname="weblogic.ejbc" fork="true" failonerror="yes">
            <classpath refid="classpath"/>
          <!--INCREASED MEMORY ALLOCATED HERE -->
            <arg line="-J-mx512M"/>  
            <arg value="${build.classes}\ejb-temp.jar"/>
            <arg value="${dist.dir}\ejb.jar"/>
        </java>
--------------------------------------------------------------------------------

Below is the error message i get.

Can someone please advise as to what the
problem might be, and how i can resolve it !!!

Thanks



<25-Oct-03 13:43:28 BST> <Notice> <Application Poller> <149404> <Activate applic
ation _appsdir_molko_ear on molko_server - Running>
<25-Oct-03 13:43:30 BST> <Notice> <Application Poller> <149404> <Activate applic
ation _appsdir_molko_ear on molko_server - Running>


The system is out of resources.
Consult the following stack trace for details.

java.lang.OutOfMemoryError
        <<no stack trace available>>
<25-Oct-03 13:43:31 BST> <Error> <EJB> <010069> <Error preparing EJB Module : ej
b.jar
Exception is :

Unable to deploy EJB: ejb.jar from ejb.jar:


Compiler failed executable.exec(java.lang.String[C:\bea\jdk131_03\bin\javac.exe,
 -nowarn, -classpath, C:\bea\user_projects\molko_domain\tmp_ejbhomepc-f43w7e9r70
01molko_server\-slhln7dvzvjt;C:\bea\user_projects\molko_domain\.\molko_server\st
age\_appsdir_molko_ear\ejb.jar;C:\bea\user_projects\molko_domain\.\molko_server\
stage\_appsdir_molko_ear\log4j-1_2_6.jar;C:\bea\user_projects\molko_domain\.\oas
ys_server\stage\_appsdir_molko_ear\commons-logging.jar;C:\bea\user_projects\oasy
s_domain\.\molko_server\stage\_appsdir_molko_ear\ftp.jar;C:\bea\user_projects\oa
sys_domain\.\molko_server\stage\_appsdir_molko_ear\jdom.jar;C:\bea\user_projects
\molko_domain\.\molko_server\stage\_appsdir_molko_ear\connxjdbc.jar;C:\bea\user_
projects\molko_domain\.\molko_server\stage\_appsdir_molko_ear\jakarta-regexp-1.2
.jar;C:\bea\user_projects\molko_domain\.\molko_server\stage\_appsdir_molko_ear\l
og4j.jar;C:\bea\user_projects\molko_domain\.\molko_server\stage\_appsdir_molko_e
ar\log4j-core.jar;C:\bea\user_projects\molko_domain\.\molko_server\stage\_appsdi
r_molko_ear\..\lib\xerces.jar;C:\bea\user_projects\molko_domain\.\molko_server\s
tage\_appsdir_molko_ear\xerces.jar;C:\bea\jdk131_03\jre\lib\rt.jar;C:\bea\jdk131
_03\jre\lib\i18n.jar;C:\bea\jdk131_03\jre\lib\sunrsasign.jar;C:\bea\jdk131_03\jr
e\classes;C:\bea\jdk131_03\lib\tools.jar;C:\bea\weblogic700\server\lib\weblogic_
sp.jar;C:\bea\weblogic700\server\lib\weblogic.jar;, -d, tmp_ejbhomepc-f43w7e9r70
01molko_server\-slhln7dvzvjt, tmp_ejbbonnar-f43w7e9r7001molko_server\-slhln7dvzv
jt\com\eds\molko\ejb\application\*.java, tmp_ejbhomepc-f43w7e9r7001molko_server\
-slhln7dvzvjt\com\eds\molko\ejb\persistence\*.java])

        at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:301)
        at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)
        at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:490)
        at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:793)
        at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1242)
        at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:242)
        at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationC
ontainer.java:1504)
        at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
er.java:690)
        at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
er.java:576)
        at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
veDeployer.java:1064)
        at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
loyer.java:732)
        at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
dler.java:24)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
0
Molko
Asked:
Molko
1 Solution
 
ja_jamalCommented:
remove this line

<arg line="-J-mx512M"/>  

then try to compile.... it will take default memory
0
 
boxy73Commented:
Here is what BEA says about this:

Due to a Sun bug, a java lang.OutOfMemory error my occur when starting WebLogic Server if the number of classes being loaded is too high.

As a workaround, increase the value of the JVM option -XXMaxPermSize when initializing WebLogic Server, using this syntax:

java -XX:MaxPermSize=<value>K

where <value> is some number of kilobytes. The JVM uses a default maximum value of 32 MB.

This problem has been reported to Sun.

Hope this helps you
0
 
MolkoAuthor Commented:
Its ok now, i found out the problem, i was packing a up a different version of the weblogi.jar (i had two different versions)..

its ok now
0
 
Computer101Commented:
PAQed, with points refunded (250)

Computer101
E-E Admin
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now