Make sure sure you have the latest weblogic service packs applied (sp2). We
identified and reported some extremely poor performance
issues with IE browsers and WebLogic with the Netscape Enterprise Server Proxy. The
problem was caused by socket connections being
closed by the proxy in a way that IE was not designed to handle. IE5 would re-try the
conncetion x times before it could resolve
the page. Needless to say, this led to many socket error in the log and slow
performance under IE5.
Download Weblogic 5.1 Service Pack 2 from http://www.bea.com. SP2 resolved the
problem.
David Gecawich
Adaptive minds, Inc.
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Shiraz Wasim Zaidi
Sent: Friday, June 30, 2000 8:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Weblogic performance problem
This is an implementation issue and this list is not the right place to
discuss it.
Contact weblogic support or post to one of their newsgroups (check
http://www.bea.com)
for a resolution.
-Shiraz
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Soni, Anuraj
Sent: Friday, June 30, 2000 1:07 PM
To: [EMAIL PROTECTED]
Subject: Weblogic performance problem
The Symptoms:
After a request was sent thru' the browser (a jsp file), the weblogic would
not respond immediately but took as much
as 10-20 seconds before anything was seen on the screen. I tested this by
putting print statements at the top of my calling JSP. The last message I
saw was
Fri Jun 23 14:58:25 EDT 2000:<D> <PosixSocketMuxer> Registering socket:
'weblogic.socket.MuxableSocketHTTP@bfedd94e - idle timeout: '60', socket
timeout: '5000', fd: '23'
And then the "print" statement would get printed after almost 10-20 seconds.
The problem:
One of the test case that we prepared was to load about 160 classes in the
jsp and after we ran this jsp we found that even a simple jsp with few html
tags took about 6 seconds to execute (ofcourse we did not time its first run
when it compiles).
Conclusion
As you load more classes the weblogic response becomes poor.
So, is there a workaround? or is it a known problem with weblogic? Any help
will be greatly appreciated.
Thanks
Anu Soni
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
