Hi Nagesh,I don't feel like logging onto the ejb book group to post this message. The following is what I found previously when I ran into out of memory error - I have had only about 20 beans and it turned out the problem was not caused by the number of ejbs in a jar. But yours sounded like one. Please keep me posted for whatever solution you came up with.Best regards, -Lu Huang================================================================================\ ==============================From the Sun debug database: THU MAR 07 06:20 A.M. 2002 Karthik9277 <mailto:pkkarthi@y...> We have encountered problems on Windows 2000 and NT when using the -hotspot option with the JVM. This is due to a Sun bug (http://developer.java.sun.com/developer/bugParade/bugs/4479571.html) and results in intermittent crashes of the server. To work around this problem, try setting:-XX:MaxPermSize=128mThis option allows you to increase the size of the area HotSpot uses for class representations. =============================================== 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>Kwhere <value> is some number of kilobytes. The JVM uses a default maximum value of 32 MB.This problem has been reported to Sun. From BEA support site: Take profiler outputs to see which objects are not being GCed. Run the server with the -verbose:gc option on. Are you creating a lot of EJbs? I would suggest you install RP2 over SP2 and use the following JVM option java ..... -XX:MaxPermSize=256m ..... weblogic.Server ================================================================================\ ============================== --- g_nageswar <g_nageswar@y...> wrote: > Hi > when i am trying to deploy the big jar file that > contains 100 > beans it is giving the error > > The System is in out of resources > java.lang.outofMemoryerror > <<no stack trace avaliable >> > for that I increased the hotspot virtual memeory > and i tried all > the combinations but still its giving the same > error. > > please help me. > > Thanks > Nagesh. > > __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com
2、重新做一个实例再启动看看。如果1,2也不行。重装WEBLOGIC7,再不能,查找系统原因:病毒等。
From: Lu Huang <lujhuang@y...>
Date: Thu Sep 5, 2002 1:14 pm
Subject: Re: [weblogic-workbook] java.lang.outofmemoryError
ADVERTISEMENT
Hi Nagesh,I don't feel like logging onto the ejb book group to
post this message. The following is what I found
previously when I ran into out of memory error - I
have had only about 20 beans and it turned out the
problem was not caused by the number of ejbs in a jar.
But yours sounded like one. Please keep me posted
for whatever solution you came up with.Best regards,
-Lu Huang================================================================================\
==============================From the Sun debug database:
THU MAR 07 06:20 A.M. 2002
Karthik9277 <mailto:pkkarthi@y...>
We have encountered problems on Windows 2000 and NT
when
using the -hotspot option with the JVM. This is due to a Sun bug
(http://developer.java.sun.com/developer/bugParade/bugs/4479571.html)
and results in intermittent crashes of the server. To
work
around this problem, try setting:-XX:MaxPermSize=128mThis option allows you to increase the size of the
area
HotSpot uses for class representations.
===============================================
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>Kwhere <value> is some number of kilobytes. The JVM
uses a
default maximum value of 32 MB.This problem has been reported to Sun.
From BEA support site:
Take profiler outputs to see which objects are not
being GCed.
Run the server with the -verbose:gc option on. Are you
creating a lot of EJbs? I would suggest you install
RP2 over SP2 and use the following
JVM option java ..... -XX:MaxPermSize=256m .....
weblogic.Server ================================================================================\
==============================
--- g_nageswar <g_nageswar@y...> wrote:
> Hi
> when i am trying to deploy the big jar file that
> contains 100
> beans it is giving the error
>
> The System is in out of resources
> java.lang.outofMemoryerror
> <<no stack trace avaliable >>
> for that I increased the hotspot virtual memeory
> and i tried all
> the combinations but still its giving the same
> error.
>
> please help me.
>
> Thanks
> Nagesh.
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
大家一起来整吧,我不想重装,我知道重装是可以,但能学到啥呢::)