Java.OutOfMemory exception

Question

Hi, could somebody help me on the following issue, which is very weird and bothered
us for a long time:
Our application runs on WebLogic 6.1 sp2. Whenever we boot up our WebLogic server
instance, after running normally for about 8 or 9 days, it generates "java.OutOfMemoryError
<<no stack trace available>>" and becomes unfunctional. Currently our application
has about 6000 transaction per day, with totally about 600 users (100 concurrent
users might likely).
What confuse us are why it takes so many days for the problem to happen? Do you
have any idea about what the problem is? By the way, we didn't use any Profiler
software, and no budget to buy anyone right now.
Thanks!
Bill

Answer 1

Hello Bill,
In addition to the system "top" utility (just type top at the command prompt to
run this particular utility), you can also examine memory usage via the WebLogic
Admin Console. Refer to the following link for details:
http://edocs.bea.com/wls/docs70/ConsoleHelp/index.html
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Bill Yuan" <[email protected]> wrote:
>
Prakash,
You mentioned to "take a look at data from top utility periodically ...",
but
I don't know how to do that, could you recommend some tools available
to HP-Unix
which can monitor the memory use?
Thanks!
Bill
"Prakash Upadhyayula" <[email protected]> wrote:
My guess would be that your application is not releasing any memoryback
to the
jvm and hence the reason for out of memory.
If you are running on unix server then please take a look at data from
top utility
periodically and that should tell you how the memory size is changing
for that
java process.
You can try to implement some clean up in your java code to ensure that
you are
cleaning up resources once done using them.
This would require some time from your resources but since you cannot
get tool
you have to depend on the old technique of code reviews.
Thank You.
-Prakash
"Bill Yang" <[email protected]> wrote:
Hi, could somebody help me on the following issue, which is very weird
and bothered
us for a long time:
Our application runs on WebLogic 6.1 sp2. Whenever we boot up our WebLogic
server
instance, after running normally for about 8 or 9 days, it generates
"java.OutOfMemoryError
<<no stack trace available>>" and becomes unfunctional. Currently our
application
has about 6000 transaction per day, with totally about 600 users (100
concurrent
users might likely).
What confuse us are why it takes so many days for the problem to happen?
Do you
have any idea about what the problem is? By the way, we didn't use
any
Profiler
software, and no budget to buy anyone right now.
Thanks!
Bill