WebLogic 7.0sp4 - deploying EAR from 6.0 - Console Servlet causes OutOfMemoryError

Question

I downloaded various copies of WebLogic. I'm trying to work with WebLogic 7.0sp4
on a Windows 2000 Server machine, but it's not working well at all. I have a very
simple set-up - one JDBC connection pool to an Oracle database, and one EAR file.
This should work easily.
I have a WebLogic 6.0 produced EAR file. The EAR files contains about 110 Entity
BMP EJBs, about 35 Stateless Session EJBs, and 1 Stateful Session EJB, as well
as a collection of supporting Java classes.
WebLogic 6.0 imports the EAR and deploys the beans with no problem. AND after
deploying the beans, WebLogic 6.0 still lets you start a WebLogic Administrative
Console to interact with and manage the WebLogic server. WebLogic 6.0 doesn't
seem to have any problems.
WebLogic 7.0 imports the EAR file, recompiles the beans, and deploys them. If
you DON'T start an admin console, then you can ping the server, ask the server
for its state, etc. - and everything seems fine. Once you start an admin console
and try to get to the login page of the admin console, THEN WebLogic 7.0 runs
out of memory.
I've already bumped the minimum heapsize up to 350MB and maxsize to over 600MB.
The application never even uses more than 100MB of real memory before it crashes
with an out-of-memory error. Something about starting the admin console is crashing
the server. The console servlet runs out of memory. Why? Is there a separate setting
to increase the Heap Size used by the Console Servlet? I'm already using the "-Xms350m
-Xmx600m" options when starting WebLogic to set aside at least 350MB of heap space.
I'm including:
- log files
- config.xml
- startweblogic.cmd
all wrapped up in files.zip
[files.zip]

Answer 1

Rob,
Thanks! That solved the problem! Now I'm going to read http://java.sun.com/docs/hotspot/gc/index.html
to find out why...
Rob Woollen <[email protected]> wrote:
I suspect that you are hitting the JVM's MaxPermSize limitations.
Search on Sun's site or these newsgropus for -XX:MaxPermSize.
Let us know if this doesn't fix your problem.
-- Rob
Bill Horan wrote:
I downloaded various copies of WebLogic. I'm trying to work with WebLogic7.0sp4
on a Windows 2000 Server machine, but it's not working well at all.I have a very
simple set-up - one JDBC connection pool to an Oracle database, andone EAR file.
This should work easily.
I have a WebLogic 6.0 produced EAR file. The EAR files contains about110 Entity
BMP EJBs, about 35 Stateless Session EJBs, and 1 Stateful Session EJB,as well
as a collection of supporting Java classes.
WebLogic 6.0 imports the EAR and deploys the beans with no problem.AND after
deploying the beans, WebLogic 6.0 still lets you start a WebLogic Administrative
Console to interact with and manage the WebLogic server. WebLogic 6.0doesn't
seem to have any problems.
WebLogic 7.0 imports the EAR file, recompiles the beans, and deploysthem. If
you DON'T start an admin console, then you can ping the server, askthe server
for its state, etc. - and everything seems fine. Once you start anadmin console
and try to get to the login page of the admin console, THEN WebLogic7.0 runs
out of memory.
I've already bumped the minimum heapsize up to 350MB and maxsize toover 600MB.
The application never even uses more than 100MB of real memory beforeit crashes
with an out-of-memory error. Something about starting the admin consoleis crashing
the server. The console servlet runs out of memory. Why? Is there aseparate setting
to increase the Heap Size used by the Console Servlet? I'm alreadyusing the "-Xms350m
-Xmx600m" options when starting WebLogic to set aside at least 350MBof heap space.
I'm including:
- log files
- config.xml
- startweblogic.cmd
all wrapped up in files.zip