HttpClusterServlet Provlems (5.1.0SP4)

3 WLAS 5.1.0SP4 running in a cluster, with an additional WLAS 5.1.0SP4
 running HttpClusterServlet as the default servlet. Very light load (single
 user).
 Everything starts out fine, but after a few minutes I start getting a
 SocketException: Socket write error. Then, session pinning breaks and a new
 server begins responding to requests. This of course breaks the application.
 The SocketExceptions keep repeating even with no load; I am guessing that
 this is the HttpClusterServlet checking server availablility.
 Tried __WebLogicBridgeConfig, but I am getting the following exception on
 the proxy:
 Tue Aug 08 13:59:06 GMT+00:00 2000:<E> <ServletContext-General> Servlet
 failed with Exception
 java.lang.NullPointerException
 at
 weblogic.servlet.internal.HttpClusterServlet.printDebugInfo(HttpClusterServl
 et.java:166)
 at
 weblogic.servlet.internal.HttpClusterServlet.service(HttpClusterServlet.java
 :106)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :124)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:744)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:692)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 Manager.java:251)
 at
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 at
 weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 Help!
 - Avi
 s/\be(\w+)/e-\1/g;

There was a problem with service pack 4. Service pack 5 is coming out very soon.
 You might want to give that a shot and see if you still have problems.
 Thanks
 - Prasad
 Avi Kivity wrote:
 > 3 WLAS 5.1.0SP4 running in a cluster, with an additional WLAS 5.1.0SP4
 > running HttpClusterServlet as the default servlet. Very light load (single
 > user).
 >
 > Everything starts out fine, but after a few minutes I start getting a
 > SocketException: Socket write error. Then, session pinning breaks and a new
 > server begins responding to requests. This of course breaks the application.
 >
 > The SocketExceptions keep repeating even with no load; I am guessing that
 > this is the HttpClusterServlet checking server availablility.
 >
 > Tried __WebLogicBridgeConfig, but I am getting the following exception on
 > the proxy:
 > Tue Aug 08 13:59:06 GMT+00:00 2000:<E> <ServletContext-General> Servlet
 > failed with Exception
 > java.lang.NullPointerException
 > at
 > weblogic.servlet.internal.HttpClusterServlet.printDebugInfo(HttpClusterServl
 > et.java:166)
 > at
 > weblogic.servlet.internal.HttpClusterServlet.service(HttpClusterServlet.java
 > :106)
 > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
 > at
 > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 > :124)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 > l.java:744)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 > l.java:692)
 > at
 > weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 > Manager.java:251)
 > at
 > weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 > at
 > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 >
 > Help!
 >
 > --
 > - Avi
 > --
 > s/\be(\w+)/e-\1/g;

Similar Messages

Will two httpclusterservlet in same web app (web.xml) work

I want to load balance multple web services (running on different weblogic managed servers) using multiple instance of httpclusterservlet.
I did experiment with defining two instances of httpclusterservlet but only the last one worked.
I want to work this with root context (/)

I want to load balance multple web services (running on different weblogic managed servers) using multiple instance of httpclusterservlet.
I did experiment with defining two instances of httpclusterservlet but only the last one worked.
I want to work this with root context (/)

Under which directory the HttpclusterServlet bging configured in an weblogic11g environment

Hello,
I am new to weblogic server and currently in the process of configuring a managed server (standalone) with HttpclusterServlet as a load balancer.As part of this I am unable to find under which directory the HttpclusterServlet being configured and the associated application to be deployed in the managed server.
Could any one help me on where to find the same,
Regarsd,
Saravanan

Hi bornesel /Aniket,
Thanks for the information.
It seems that a default HttpclusterServlet comes as part of weblogic server.I just want to make use of that as part of the deployment.Do you have any idea on the same?
Regards,
Saravanan

A problem with HttpClusterServlet

          Hi all.
          I have a cluster of two wls instances (working ok) and now I wish to put a third one in front of them.
          I've registered the HttpClusterServlet as the default servlet:
          weblogic.allow.execute.weblogic.servlet=everyone
          weblogic.httpd.register.cluster=\
          weblogic.servlet.internal.HttpClusterServlet
          weblogic.httpd.initArgs.cluster=\
          defaultServers=myserver1:7008:7009|myserver2:7008:7009,DebugConfigInfo=ON
          weblogic.httpd.defaultServlet=cluster
          but when I call it from my browser I get a 500 with this stack trace (if weblogic.debug.httpd.servlet is true):
          java.lang.NullPointerException
          at weblogic.servlet.internal.HttpClusterServlet$Server.(HttpClusterServlet.java:391)
          at weblogic.servlet.internal.HttpClusterServlet$2.next(HttpClusterServlet.java:257)
          at weblogic.servlet.internal.HttpClusterServlet.service(HttpClusterServlet.java:129)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:760)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
          at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
          at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
          at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
          Where is the mistake?
          I have a wls 5.1 SP5 running on a jvm 1.2.2 running on an hpux 11.00.
          Any help appreciated.
          Carlo Montanari


How about your properties in the backend of the servers in the cluster.
          - Prasad
          Carlo Montanari wrote:
          > Hi all.
          > I have a cluster of two wls instances (working ok) and now I wish to put a third one in front of them.
          > I've registered the HttpClusterServlet as the default servlet:
          >
          > weblogic.allow.execute.weblogic.servlet=everyone
          > weblogic.httpd.register.cluster=\
          > weblogic.servlet.internal.HttpClusterServlet
          > weblogic.httpd.initArgs.cluster=\
          > defaultServers=myserver1:7008:7009|myserver2:7008:7009,DebugConfigInfo=ON
          > weblogic.httpd.defaultServlet=cluster
          >
          > but when I call it from my browser I get a 500 with this stack trace (if weblogic.debug.httpd.servlet is true):
          >
          > java.lang.NullPointerException
          > at weblogic.servlet.internal.HttpClusterServlet$Server.(HttpClusterServlet.java:391)
          > at weblogic.servlet.internal.HttpClusterServlet$2.next(HttpClusterServlet.java:257)
          > at weblogic.servlet.internal.HttpClusterServlet.service(HttpClusterServlet.java:129)
          > at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:760)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:707)
          > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
          > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:369)
          > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:269)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
          >
          > Where is the mistake?
          > I have a wls 5.1 SP5 running on a jvm 1.2.2 running on an hpux 11.00.
          > Any help appreciated.
          > --
          >
          > Carlo Montanari

Problem working with HttpClusterServlet

hi:
 this is the first time i work with weblogic6.1(NT platform) cluster.
 i config the DefaultWebApp as web application which will proxy requests to
 my cluster which consists of two weblogic server running on the same host
 (http://localhost:7001 and http://localhost:7003).
 my web.xml before is as floowing(before it works as a proxy)
 <?xml version="1.0" ?>
 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
 <web-app>
 <welcome-file-list>
 <welcome-file>index.html</welcome-file>
 </welcome-file-list>
 </web-app>
 but when i modify it as following as a proxy to my cluster
 <?xml version="1.0" ?>
 <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
 <web-app>
 <welcome-file-list>
 <welcome-file>index.html</welcome-file>
 </welcome-file-list>
 <servlet>
 <servlet-name>HttpClusterServlet</servlet-name>
 <servlet-class>
 weblogic.servlet.internal.HttpClusterServlet
 </servlet-class>
 <init-param>
 <param-name>defaultServers</param-name>
 <param-value>
 bea:7003:7004
 </param-value>
 </init-param>
 </servlet>
 <servlet-mapping>
 <servlet-name>HttpClusterServlet</servlet-name>
 <url-pattern>/</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>HttpClusterServlet</servlet-name>
 <url-pattern>*.jsp</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>HttpClusterServlet</servlet-name>
 <url-pattern>*.htm</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
 <servlet-name>HttpClusterServlet</servlet-name>
 <url-pattern>*.html</url-pattern>
 </servlet-mapping>
 <init-param>
 <param-name>DebugConfigInfo</param-name>
 <param-value>ON</param-value>
 </init-param>
 </web-app>
 there's no response anymore , no error .
 there's little docs available and i need your help
 regards


Hi.
 A couple of suggestions:
 1. Clusters must use the same port number. If you are running a cluster on a
 single machine this means that your machine must be multihomed and each member
 of the cluster must bind to a unique IP address. Your other alternative is to
 use multiple machines. I don't believe your configuration will work for a
 cluster.
 2. you don't have yoru default servers listed correctly in your web.xml
 file. To specify 2 different servers you need to specify each server
 separated by a '|' character as follows:
 myserver1:70017001|myserver2:7001:7002 The second port number is for SSL
 communications. In your xml file you are only specifying a single server.
 Hope this helps,
 Michael
 daniel wang wrote:
 > hi:
 > this is the first time i work with weblogic6.1(NT platform) cluster.
 > i config the DefaultWebApp as web application which will proxy requests to
 > my cluster which consists of two weblogic server running on the same host
 > (http://localhost:7001 and http://localhost:7003).
 >
 > my web.xml before is as floowing(before it works as a proxy)
 >
 > <?xml version="1.0" ?>
 > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
 > 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
 > <web-app>
 > <welcome-file-list>
 > <welcome-file>index.html</welcome-file>
 > </welcome-file-list>
 >
 > </web-app>
 >
 > but when i modify it as following as a proxy to my cluster
 >
 > <?xml version="1.0" ?>
 > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
 > 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
 > <web-app>
 > <welcome-file-list>
 > <welcome-file>index.html</welcome-file>
 > </welcome-file-list>
 > <servlet>
 > <servlet-name>HttpClusterServlet</servlet-name>
 > <servlet-class>
 > weblogic.servlet.internal.HttpClusterServlet
 > </servlet-class>
 >
 > <init-param>
 > <param-name>defaultServers</param-name>
 > <param-value>
 > bea:7003:7004
 > </param-value>
 > </init-param>
 >
 > </servlet>
 >
 > <servlet-mapping>
 > <servlet-name>HttpClusterServlet</servlet-name>
 > <url-pattern>/</url-pattern>
 > </servlet-mapping>
 >
 > <servlet-mapping>
 > <servlet-name>HttpClusterServlet</servlet-name>
 > <url-pattern>*.jsp</url-pattern>
 > </servlet-mapping>
 >
 > <servlet-mapping>
 > <servlet-name>HttpClusterServlet</servlet-name>
 > <url-pattern>*.htm</url-pattern>
 > </servlet-mapping>
 >
 > <servlet-mapping>
 > <servlet-name>HttpClusterServlet</servlet-name>
 > <url-pattern>*.html</url-pattern>
 > </servlet-mapping>
 > <init-param>
 > <param-name>DebugConfigInfo</param-name>
 > <param-value>ON</param-value>
 > </init-param>
 >
 > </web-app>
 >
 > there's no response anymore , no error .
 >
 > there's little docs available and i need your help
 >
 > regards
 Michael Young
 Developer Relations Engineer
 BEA Support

HttpClusterServlet Proxy Plugin problem - Weblogic Express 10

Hi,
I am using Weblogic Express 10 version. I am trying to configure HttpClusterServelet in one of my test machine.
I have a Admin server and 3 Managed servers which are part of clusters. I have a test war file which is deployed on to the cluster.
I am able to open the test war file application by hitting Managed servers URL's & Port no's
for eg: http://hostname:portno/testapp
Now I have created a war file with httpclusterserver features and deployed it to Admin server. (created web.xml & weblogic.xml inside WEB-INF directory and built it as war file and deployed it to Admin server)
so practically whenever I hit the Admin server URL my request should be proxied to one of the three Managed server which are part of the cluster
But when I try to open the application through admin server hostname and port no, I get below 403 exception on browser
Error 403--Forbidden
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Below is the content of my web.xml & weblogic.xml war file
web.xml
-bash-3.00$ more web.xml
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd";>
<web-app>
<servlet>
<servlet-name>HttpClusterServlet</servlet-name>
<servlet-class>
weblogic.servlet.proxy.HttpClusterServlet
</servlet-class>
<init-param>
<param-name>WebLogicCluster</param-name>
<param-value>
ManagedSrv1_Hostname:PortNo|ManagedSrv2_Hostname:PortNo|ManagedSrv3_Hostname:PortNo
</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>
</web-app>
weblogic.xml
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/
weblogic 810-web-jar.dtd">
<weblogic-web-app>
<context-root>/</context-root>
</weblogic-web-app>
Kindly advise on this problem.
- - Weblogic Consultant

Hi,
 Did you configure the replication correctly in the weblogic.xml?
 Also fill in the correct cluster address in the weblogic configuration.
 http://edocs.bea.com/wls/docs90/cluster/setup.html#726973
 Schelstraete Bart
 [email protected]
 http://www.schelstraete.org
 http://www.linkedin.com/in/bschelst

HttpClusterServlet Proxy Load Balancing with Multiple Clusters

          How do I load balance JSPs and Servlets using the HttpClusterServlet proxy server
          approach when I have more than one cluster?
          It appears from the docs that there is a 1 to 1 relationship between the non-clustered
          managed proxy server that has the HttpClusterServlet and the cluster (1 proxy
          to 1 cluster).


Preferred method would be domain, domainhash, url or urlhash as described in:
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/bsccfggd/contrule.htm#xtocid2610122.
do not recommend to use round-robin method for load balancing internet proxies. It creates inefficient usage of the storage and bandwidth, as more proxies can have to cache the same objects.

HttpClusterServlet Load Balancing Problem

          Hi,
          I have a problem with LoadBalancing and HttpClusterServlet.
          I have 2 boxes, with a clustered application, deployed on 2 managed servers
          box 1 with adminServer and and a managed server (managed1)
          box 2 with second managed server (managed2)
          on box 1 I have another managed server, which hosts the HttpClusterServlet application
          The cluster is made up of managed1 & managed2, and httpClusterServlet is configured
          to send requests to boths the managed servers in the cluster.
          When I run some tests against the httpClusterServlet web application to see how
          it load-balances requests, I can see that all the requests are redirected just
          to managed1,
          on the same machine.
          If I stop managed1, and run some tests, I can see that httpCluster every time
          tries to contact managed1 first, and since it's down, sends the requests to managed2(handles
          failover correctly).
          If I move the httpClusterServlet application to another box, let's call it box
          3, and re run the tests, it will load-balances the requests between managed1 (box1)
          and managed2(box2) correctly.
          I would like to know if httpClusterServlet has some kind of "server affinity"
          logic (?) or I'm missing something in the cluster configuration (even if I can't
          see clearly how the cluster configuration could affect things, since HttpServlet,
          which is not in the cluster, just should route
          requests to the specified servers in round-robin fashion, I guess)
          Someone in previous posts pointed out http session issues, is it true? and so,
          why?
          Sorry for the far too long post,
          thanks in advance,
          Thomas


Only from load balancing point of view cluster is not really needed.
apart from session replication and failover capabilities, few more benefits are there with clustering only if you are using a web server also.
Stuck threads can be due to lot's of problems like application issues, load issues etc, So first make sure you are getting stuck thread on both servers or only on one, if on one, then in this case your load balancing not working properly and sending more load to that server, and if you are getting stuck threads on both then try to add one more managed server.
Regards
Mukesh Negi
http://weblogicserveradministration.blogspot.com

Proxying with HttpClusterServlet

Hi,
          I'm using a multihomed NT Server with WLS 6.0. I have one domain configured
          with an admin server and two managed servers which are clustered. I
          configured a second domain with one server and a web app deployed with
          HttpClusterServlet (I extracted the HttpClusterServlet classes from
          weblogic.jar and deployed them in the web app). I edited web.xml adding
          HttpClusterServlet and the associated parm (defaultServers) as described in
          the doc.
          I'm testing load balancing of a servlet deployed on both managed servers.
          Load balancing works fine as I see the servlet execution alternating from
          one server to the next.
          My problem is duplicating this set up on a second NT Server. With the
          exception of IP addresses, hardware and the WLS 6.0 installation, the boxes
          are identical. But, on this box the servlet is not load balanced. The
          servlet always runs on the first server in the list. I have to admit I'm
          stumped! Short of reinstalling WLS, I have tried everything I can think of
          without success.
          My question is how can I debug HttpClusterServlet to figure out why the
          servlet is not being load balanced?
          Your help would be much appreciated.
          Mike


          Ok, I did find and set the DebugConfigInfo to ON. When I run the servlet via the
          proxy I get the following
          results:
          Server with load balancing not working:
          Query String: __WebLogicBridgeConfig
          Dynamic Server List:
          Host: xxx.yy.zz.179 Port: 7019
          Static Server List:
          Host: xxx.yy.zz.179 Port: 7019
          Host: xxx.yy.zz.186 Port: 7019
          CookieName: JSESSIONID
          Server with load balancing working:
          Query String: __WebLogicBridgeConfig
          Dynamic Server List:
          Host: xxx.yy.zz.75 Port: 7019
          Host: xxx.yy.zz.74 Port: 7019
          Static Server List:
          Host: xxx.yy.zz.74 Port: 7019
          Host: xxx.yy.zz.75 Port: 7019
          CookieName: JSESSIONID
          Obviously, the second server is not in the dynamic server list. Any ideas????
          Mike
          >
          >

Load balancing with HttpClusterServlet

 Hi,
 Could someone plz tell me how HttpClusterServlet achieves
 load balancing?
 Suppose there are 3 servers A,B,C (ordered list) in a cluster.
 When the servlet the receives the request for the 1st time will
 direct it to server A and let B be the secondary. Now, when the
 same client makes a 2nd request the servlet reads the cookie and
 directs the request to server A.
 Where is load balancing been achieved here?
 Or is it this way LB ( load balancing ) is done:
 if any other client (other than the one mentioned above) makes a
 request it is directed to server B (since it is the 2nd server
 in the cluster)
 thanx


It is the second option you mention.
 -- Anand
 "pradeep bhat" <[email protected]> wrote in message
 news:3ca0409e$[email protected]..
 >
 > Hi,
 > Could someone plz tell me how HttpClusterServlet achieves
 > load balancing?
 >
 >
 > Suppose there are 3 servers A,B,C (ordered list) in a cluster.
 > When the servlet the receives the request for the 1st time will
 > direct it to server A and let B be the secondary. Now, when the
 > same client makes a 2nd request the servlet reads the cookie and
 > directs the request to server A.
 >
 >
 > Where is load balancing been achieved here?
 >
 >
 > Or is it this way LB ( load balancing ) is done:
 >
 > if any other client (other than the one mentioned above) makes a
 > request it is directed to server B (since it is the 2nd server
 > in the cluster)
 > thanx
 >
 >

WLS with the HttpClusterServlet or Apache with proxy plug-in?

I'm newbie with WebLogic Server cluster.
Please tell me which is better for load balancing for WLS cluster? WLS with the HttpClusterServlet or Apache HTTP Server Plug-In? And which is recommended for production environment?
Many thanks.

Apache with plug-in, as this is easier configurable.
For the HttpClusterServlet all the configuration goes into web.xml which has to be packaged as a war file and deployed to WebLogic.
When any change is needed you have to edit the web.xml file, package it again and redeploy it.
An example of the Apache plug-in set-up can be found here: http://middlewaremagic.com/weblogic/?p=7795 (the load balancing section)
Or if you want to use the Oracle Web-Tier (which includes a precompiled Apache HTTP server): http://middlewaremagic.com/weblogic/?p=7819 (the load balancer section)

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

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]

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

WebLogic 7.0sp4 - Console Servlet causes java.lang.OutOfMemoryError

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
[files.zip]

I do not think this is the right group for your issue. Please post it in the appropriate
one.
"Bill Horan" <[email protected]> wrote:
>
>
>
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

Serious HttpClusterServlet problem

Hi all,
 I have come across yet one more cluster problem.
 Here is as precise description as I can come up with; we are running
 WebLogic 5.1 SP6 on Solaris.
 Architecture
 Weblogic server (A) running as proxy to a cluster (configured with
 HttpClusterServlet) and
 2 Weblogic servers (B & C) running in cluster, the app is protected -
 sign-on required.
 Scenario:
 All 3 server are up and running.
 1) A client connects via proxy to server B, is authenticated and logged
 in. Session is established.
 2) Client interacts with server B, session gets populated with some
 basic objects.
 3) Server B is killed.
 4) Client attempts to send a request to server B. Problem #1 - Even
 though this request from browser gets
 to the proxy and the browser's status says "receiving data from
 ...", nothing gets propagated to server C.
 Now the user clicks Stop button on the browser and sees "Transfer
 interrupted..." page generated by the browser.
 Client hits back button, the previous page gets loaded fine. Now the
 client attempts to send the same request
 again and this time it gets through the proxy to the server C which
 has a replicated session. Things are fine but
 this initial failure troublesme as it happens ALL the time when
 scenario is repeated. If the user does not hit the
 stop button, "document conainted no data...." dialog is poped-up by
 the browser eventualy.
 5. Client interacts with the server C now for a while.
 6. Browser is killed (normal exit, shutdown will do too) when there is
 no activity.
 7. Browser is restarted and the user attempts to go to the root URL of
 the app.
 Now things go NUTS. The proxy server goes crazy, spitting out tons of
 messages and exceptions, including
 division by zero attempted .
 In addition to the proxy server spitting out all of that info, during
 several attempts to duplicate this I also
 had the clustered server C go nuts in parallel with the proxy as
 well.
 These is unrecoverable situation, it is necessary to kill both the
 proxy and the clustered server in order to stop the
 madness.
 I realize there was some fix to infinite loop problem in
 HttpClusterServlet in SP6 but I am using SP6 and it doesn't help.
 Here is a compilation of both the messages from the weblogic.log and
 stdout:
 Notice that up until 14:53:45 the Broken Pipe messages were - info
 but
 at 14:54:14 they all become <E> - Errors
 How is this for a bug????
 -Andrew
 weblogic.log:
 Wed Nov 08 14:52:05 EST 2000: <ServletContext-General> cluster: init
 Wed Nov 08 14:52:10 EST 2000: <proxy> IOException in proxy Broken
 pipe
 Wed Nov 08 14:52:48 EST 2000: <proxy> IOException in proxy Broken
 pipe
 Wed Nov 08 14:53:01 EST 2000: <proxy> IOException in proxy Broken
 pipe
 Wed Nov 08 14:53:02 EST 2000: <proxy> IOException in proxy Connection
 reset by peer: Connection reset by peer
 Wed Nov 08 14:53:02 EST 2000: <proxy> IOException in proxy Connection
 reset by peer: Connection reset by peer
 Wed Nov 08 14:53:45 EST 2000: <proxy> IOException in proxy Broken
 pipe
 Wed Nov 08 14:53:45 EST 2000: <proxy> IOException in proxy Broken
 pipe
 Wed Nov 08 14:53:45 EST 2000: <proxy> IOException in proxy Broken
 pipe
 Wed Nov 08 14:54:14 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:54:44 EST 2000: <proxy> IOException in proxy Connection
 reset by peer: Connection reset by peer
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:25 EST 2000:<E> <ServletContext-General> Servlet failed
 with Exception
 java.lang.ArithmeticException: / by zero
 at
 weblogic.servlet.internal.HttpClusterServlet$ServerList.next(Compiled
 Code)
 at weblogic.servlet.internal.HttpClusterServlet$2.next(Compiled Code)
 at weblogic.servlet.internal.HttpClusterServlet.service(Compiled Code)
 at javax.servlet.http.HttpServlet.service(Compiled Code)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
 Code)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
 at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 Wed Nov 08 14:55:25 EST 2000:<E> <ServletContext-General> Servlet failed
 with Exception
 java.lang.ArithmeticException: / by zero
 at
 weblogic.servlet.internal.HttpClusterServlet$ServerList.next(Compiled
 Code)
 at weblogic.servlet.internal.HttpClusterServlet$2.next(Compiled Code)
 at weblogic.servlet.internal.HttpClusterServlet.service(Compiled Code)
 at javax.servlet.http.HttpServlet.service(Compiled Code)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
 Code)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
 at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Broken pipe
 and here is stdout...............
 java.io.IOException: Broken pipe
 at java.net.SocketOutputStream.socketWrite(Native Method)
 at java.net.SocketOutputStream.socketWrite(Compiled Code)
 at java.net.SocketOutputStream.write(Compiled Code)
 at weblogic.servlet.internal.ChunkUtils.writeChunks(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletOutputStreamImpl.flush(Compiled Code)
 at
 weblogic.servlet.internal.ServletOutputStreamImpl.flush(Compiled Code)
 at
 weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(Compiled
 Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$Server.proxy(Compiled Code)
 at weblogic.servlet.internal.HttpClusterServlet.service(Compiled
 Code)
 at javax.servlet.http.HttpServlet.service(Compiled Code)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.socketConnect(Compiled Code)
 at java.net.PlainSocketImpl.doConnect(Compiled Code)
 at java.net.PlainSocketImpl.connectToAddress(Compiled Code)
 at java.net.PlainSocketImpl.connect(Compiled Code)
 at java.net.Socket.<init>(Compiled Code)
 at java.net.Socket.<init>(Compiled Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$3.newInstance(Compiled
 Code)
 at weblogic.utils.reuse.Pool.getInstance(Compiled Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$Server.getConnection(Compiled
 Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$Server.proxy(Compiled Code)
 at weblogic.servlet.internal.HttpClusterServlet.service(Compiled
 Code)
 at javax.servlet.http.HttpServlet.service(Compiled Code)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 server.proxy()....Connection refused
 java.net.ConnectException: Connection refused
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.socketConnect(Compiled Code)
 at java.net.PlainSocketImpl.doConnect(Compiled Code)
 at java.net.PlainSocketImpl.connectToAddress(Compiled Code)
 at java.net.PlainSocketImpl.connect(Compiled Code)
 at java.net.Socket.<init>(Compiled Code)
 at java.net.Socket.<init>(Compiled Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$3.newInstance(Compiled
 Code)
 at weblogic.utils.reuse.Pool.getInstance(Compiled Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$Server.getConnection(Compiled
 Code)
 at
 weblogic.servlet.internal.HttpClusterServlet$Server.proxy(Compiled Code)
 at weblogic.servlet.internal.HttpClusterServlet.service(Compiled
 Code)
 at javax.servlet.http.HttpServlet.service(Compiled Code)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 Code)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
 Code)
 at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 and a whole lot more of the same sequence of errors - too much too list


Contact support and see if they have a patch for this.
 - Prasad
 Andrzej Porebski wrote:
 > Hi all,
 >
 > I have come across yet one more cluster problem.
 > Here is as precise description as I can come up with; we are running
 > WebLogic 5.1 SP6 on Solaris.
 >
 > Architecture
 >
 > Weblogic server (A) running as proxy to a cluster (configured with
 > HttpClusterServlet) and
 > 2 Weblogic servers (B & C) running in cluster, the app is protected -
 > sign-on required.
 >
 > Scenario:
 >
 > All 3 server are up and running.
 >
 > 1) A client connects via proxy to server B, is authenticated and logged
 > in. Session is established.
 > 2) Client interacts with server B, session gets populated with some
 > basic objects.
 > 3) Server B is killed.
 > 4) Client attempts to send a request to server B. Problem #1 - Even
 > though this request from browser gets
 > to the proxy and the browser's status says "receiving data from
 > ...", nothing gets propagated to server C.
 > Now the user clicks Stop button on the browser and sees "Transfer
 > interrupted..." page generated by the browser.
 > Client hits back button, the previous page gets loaded fine. Now the
 > client attempts to send the same request
 > again and this time it gets through the proxy to the server C which
 > has a replicated session. Things are fine but
 > this initial failure troublesme as it happens ALL the time when
 > scenario is repeated. If the user does not hit the
 > stop button, "document conainted no data...." dialog is poped-up by
 > the browser eventualy.
 > 5. Client interacts with the server C now for a while.
 > 6. Browser is killed (normal exit, shutdown will do too) when there is
 > no activity.
 > 7. Browser is restarted and the user attempts to go to the root URL of
 > the app.
 > Now things go NUTS. The proxy server goes crazy, spitting out tons of
 > messages and exceptions, including
 > division by zero attempted .
 > In addition to the proxy server spitting out all of that info, during
 > several attempts to duplicate this I also
 > had the clustered server C go nuts in parallel with the proxy as
 > well.
 > These is unrecoverable situation, it is necessary to kill both the
 > proxy and the clustered server in order to stop the
 > madness.
 > I realize there was some fix to infinite loop problem in
 > HttpClusterServlet in SP6 but I am using SP6 and it doesn't help.
 >
 > Here is a compilation of both the messages from the weblogic.log and
 > stdout:
 > Notice that up until 14:53:45 the Broken Pipe messages were - info
 > but
 > at 14:54:14 they all become <E> - Errors
 >
 > How is this for a bug????
 >
 > -Andrew
 >
 > weblogic.log:
 > Wed Nov 08 14:52:05 EST 2000: <ServletContext-General> cluster: init
 > Wed Nov 08 14:52:10 EST 2000: <proxy> IOException in proxy Broken
 > pipe
 > Wed Nov 08 14:52:48 EST 2000: <proxy> IOException in proxy Broken
 > pipe
 > Wed Nov 08 14:53:01 EST 2000: <proxy> IOException in proxy Broken
 > pipe
 > Wed Nov 08 14:53:02 EST 2000: <proxy> IOException in proxy Connection
 > reset by peer: Connection reset by peer
 > Wed Nov 08 14:53:02 EST 2000: <proxy> IOException in proxy Connection
 > reset by peer: Connection reset by peer
 > Wed Nov 08 14:53:45 EST 2000: <proxy> IOException in proxy Broken
 > pipe
 > Wed Nov 08 14:53:45 EST 2000: <proxy> IOException in proxy Broken
 > pipe
 > Wed Nov 08 14:53:45 EST 2000: <proxy> IOException in proxy Broken
 > pipe
 > Wed Nov 08 14:54:14 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:54:44 EST 2000: <proxy> IOException in proxy Connection
 > reset by peer: Connection reset by peer
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:25 EST 2000:<E> <ServletContext-General> Servlet failed
 > with Exception
 > java.lang.ArithmeticException: / by zero
 > at
 > weblogic.servlet.internal.HttpClusterServlet$ServerList.next(Compiled
 > Code)
 > at weblogic.servlet.internal.HttpClusterServlet$2.next(Compiled Code)
 > at weblogic.servlet.internal.HttpClusterServlet.service(Compiled Code)
 > at javax.servlet.http.HttpServlet.service(Compiled Code)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
 > Code)
 > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
 > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 >
 > Wed Nov 08 14:55:25 EST 2000:<E> <ServletContext-General> Servlet failed
 > with Exception
 > java.lang.ArithmeticException: / by zero
 > at
 > weblogic.servlet.internal.HttpClusterServlet$ServerList.next(Compiled
 > Code)
 > at weblogic.servlet.internal.HttpClusterServlet$2.next(Compiled Code)
 > at weblogic.servlet.internal.HttpClusterServlet.service(Compiled Code)
 > at javax.servlet.http.HttpServlet.service(Compiled Code)
 > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
 > Code)
 > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
 > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 >
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:26 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 > Wed Nov 08 14:55:27 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Broken pipe
 >
 > and here is stdout...............
 >
 > java.io.IOException: Broken pipe
 > at java.net.SocketOutputStream.socketWrite(Native Method)
 > at java.net.SocketOutputStream.socketWrite(Compiled Code)
 > at java.net.SocketOutputStream.write(Compiled Code)
 > at weblogic.servlet.internal.ChunkUtils.writeChunks(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletOutputStreamImpl.flush(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletOutputStreamImpl.flush(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$Server.proxy(Compiled Code)
 >
 > at weblogic.servlet.internal.HttpClusterServlet.service(Compiled
 > Code)
 > at javax.servlet.http.HttpServlet.service(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > java.net.ConnectException: Connection refused
 > at java.net.PlainSocketImpl.socketConnect(Native Method)
 > at java.net.PlainSocketImpl.socketConnect(Compiled Code)
 > at java.net.PlainSocketImpl.doConnect(Compiled Code)
 > at java.net.PlainSocketImpl.connectToAddress(Compiled Code)
 > at java.net.PlainSocketImpl.connect(Compiled Code)
 > at java.net.Socket.<init>(Compiled Code)
 > at java.net.Socket.<init>(Compiled Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$3.newInstance(Compiled
 > Code)
 > at weblogic.utils.reuse.Pool.getInstance(Compiled Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$Server.getConnection(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$Server.proxy(Compiled Code)
 >
 > at weblogic.servlet.internal.HttpClusterServlet.service(Compiled
 > Code)
 > at javax.servlet.http.HttpServlet.service(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 > Wed Nov 08 14:55:25 EST 2000:<E> <proxy> IOException after
 > server.proxy()....Connection refused
 > java.net.ConnectException: Connection refused
 > at java.net.PlainSocketImpl.socketConnect(Native Method)
 > at java.net.PlainSocketImpl.socketConnect(Compiled Code)
 > at java.net.PlainSocketImpl.doConnect(Compiled Code)
 > at java.net.PlainSocketImpl.connectToAddress(Compiled Code)
 > at java.net.PlainSocketImpl.connect(Compiled Code)
 > at java.net.Socket.<init>(Compiled Code)
 > at java.net.Socket.<init>(Compiled Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$3.newInstance(Compiled
 > Code)
 > at weblogic.utils.reuse.Pool.getInstance(Compiled Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$Server.getConnection(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.HttpClusterServlet$Server.proxy(Compiled Code)
 >
 > at weblogic.servlet.internal.HttpClusterServlet.service(Compiled
 > Code)
 > at javax.servlet.http.HttpServlet.service(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
 > Code)
 > at
 > weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled
 > Code)
 > at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
 > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 > .......
 > and a whole lot more of the same sequence of errors - too much too list
 > ..........

Performance and HA for HttpClusterServlet

 Hi,
 I didn't see much information in the documentation about the HttpClusterServlet:
 - can it be (easily) set up in a HA configuration (to avoid it being a SPOF)?
 - how does it perform?
 - is it possible to cluster it?
 Regards,
 Frank Olsen
 Stonesoft


 "Cameron Purdy" <[email protected]> wrote:
 >You can run HttpClusterServlet on a whole slew of Weblogic Express servers
 >with a h/w load balancer in front and a cluster in back, for example.
 > That
 >gives you no SPOF (assuming secondary h/w load balancer etc.) and some
 >scale.
 >
 OK.
 >I don't know how the software load balancer fits in there ...
 >
 The answer is ... well, sorry for "plugging" our product -- (selling it would
 of course be nice); but getting feedback on what we can do better is also a good
 reason to tell yo about a possible alternative.
 As I see it, it could be an alternative to (i.e., it replaces) the dispatchers:
 - you run a cluster of WLS instances with in-memory replication to ensure failover
 of session state (or, JDBC persistence for a less performant alternative)
 - our StoneBeat WebCluster product can do this:
 . as I've explained in a thread on the in-memory replication group, this works
 fine in the major cases
 . I've been able to detect some scenarios that causes problems with sessions
 being lost, but it was in cases where the Dynamic Tcp feature of the WebCluster
 was not used (or keepalives where disabled)
 . I'm contacting BEA to see if they'd be willing to consider (certify) this
 as an alternative to the HW/SW dispacther solutions
 . of course, each have pros and cons, but if the choice is there...
 . one advantage of WebCluster would be that it is simple to set up and manage;
 it is distributed and has no inherent SPOF; it has a very good test subsystem
 to allow for dynamic load balancing
 . we also have a whole range of products from load balancing for firewalls (and
 soon our own firewall), to load balancing of web servers, ..., to a HA solution
 for databases and other applications based on shared storage
 Regards,
 Frank Olsen
 Stonesoft
 >--
 >Cameron Purdy
 >Tangosol, Inc.
 >http://www.tangosol.com
 >+1.617.623.5782
 >WebLogic Consulting Available
 >
 >
 >"Frank Olsen" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Hi,
 >>
 >> I didn't see much information in the documentation about the
 >HttpClusterServlet:
 >> - can it be (easily) set up in a HA configuration (to avoid it being
 >a
 >SPOF)?
 >> - how does it perform?
 >> - is it possible to cluster it?
 >>
 >> Regards,
 >> Frank Olsen
 >> Stonesoft
 >>
 >
 >

HttpClusterServlet Provlems (5.1.0SP4)

Similar Messages

Maybe you are looking for