OutOfMemoryError during Startup

[HanMing Low]

Hi,
I'm having some problem with my domain startup.
I've been starting up this configured domain successfully while I'm testing a web-app/ejb-jar EAR.
There is only this EAR on the server.
After multiple restart, during one of the shutdown using the admin console, it experience an OutOfMemoryError.
Ever since, I can't start my server
and it always stuck at the following line
<Oct 17, 2002 12:07:31 AM SGT> <Notice> <Management> <140005> <Loading configuration D:\AppServer\Weblogic\7.0\user_projects\mydomain\.\config.xml>
java.lang.OutOfMemoryError
<<no stack trace available>>
Starting the server at debug mode give slightly more information
<Oct 17, 2002 12:09:01 AM SGT> <Notice> <Management> <140005> <Loading configuration D:\AppServer\Weblogic\7.0\user_projects\mydomain\.\config.xml>
java.lang.OutOfMemoryError
at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:206)
I can't find much information at support.bea.com and editing my config.xml by removing the EAR entry there doesn't seems to help.
Can anyone please help me on troubleshooting the problem?
Thanks for any advice.
Cheers.

Han Ming

[Chris Mathews]

Are you doing anything strange in your application? Is it a very high traffic app or are you extensively load-testing it? Does your box have enough physical memory? Do you have enough memory allocated for the JVM that WebLogic is running under? Are you using JMS? If so, are the filestores getting extremely large? Sorry, I have many more questions for you than I have answers.

[HanMing Low]

Hi Chris,
Thanks for your questions.
I think it help me to nail down the cause of it.
As the error suggest "OutOfMemoryError", it rather silly for me to ask what causes it, isn't it?

Anyway, I try to increase the MEM_AGRS, and this time it sort of run to the same line but remain there with prolonged harddisk activity.
So, I presume it is swapping heavily in and out as I'm running out of memory.
I'm sorry to ask a redundant question here as the Error has already indicated to me what is the possible cause.
But really thanks for the suggestion.
It's by trying to answer every of your question that I managed to find the problem.
Cheers.

Han Ming

[Dave Landers]

This looks familiar, but I am not sure. I think this is a bug with WLS 7.0. It may have been fixed in the platform release or SP1, but I am not sure.
Support should know - try contacting them for SP information or a patch.
In the mean time, I think you can remove the directory called userConfig and the server should startup again. This directory contains the data store used by WLS security (users, groups, roles, and policies), so if you have messed with alot of those settings (like creating users or groups), you may loose that work.
Sorry in advance if it doesn't work - my memory is clogged with lots of tiny things like this and sometimes they collide with each other