Is weblogic designed to be a 24/7 webserver?

Question

I am beginning to wonder if it was written for a specific business
market or if it is able to handle heavy loads of traffic for an
unlimited amount of time.
The scenario is thus...we start the webservers (4 of them on single CPU
sparc boxes roughly equivalent to a ultrasparc II ) and they are very
fast....
As time goes by, the servers get slower and slower and slower...until
our pages which were serving up in .00x time..are now taking 10-20
seconds
and then more times goes by and before we know it, it starts taking 60+
seconds to serve the same page that was previously served uner a second.
We stop the webserver and restart it..and presto! Its back to serving
the exact same page in under a second again...It doesnt look like a
memory
leak, but more of a CPU / other resource leak.
-Earl

Answer 1

Hi,
Don't get me wrong here... I really like this server, but 24 x 7... come
on!!! I don't consider a server to be a 24 x 7 solution when you have to
bounce it everytime you make a settings change or add a user.
Steve...
Guy Tal <[email protected]> wrote in message
news:860idj$bsq$[email protected]..
Until you know what's actually causing the performance degradation, youcan't
really blame Weblogic for it. Could be anything from leaky OS libraries
to zombie processes or threads that tie up the CPU. I even heard of a case
where static electricity was building up around the network interface
causing lots of dropped packets... do some investigation and find thesource.
If it's indeed Weblogic, I'm sure they'll fix it - it is definitelysupposed
to be a robust 24x7 mission-critical service.
Guy
Earl Q <[email protected]> wrote:
I am beginning to wonder if it was written for a specific business
market or if it is able to handle heavy loads of traffic for an
unlimited amount of time.
The scenario is thus...we start the webservers (4 of them on single CPU
sparc boxes roughly equivalent to a ultrasparc II ) and they are very
fast....
As time goes by, the servers get slower and slower and slower...until
our pages which were serving up in .00x time..are now taking 10-20
seconds
and then more times goes by and before we know it, it starts taking 60+
seconds to serve the same page that was previously served uner a second.
We stop the webserver and restart it..and presto! Its back to serving
the exact same page in under a second again...It doesnt look like a
memory
leak, but more of a CPU / other resource leak.
-Earl