6 Replies Latest reply on May 5, 2003 6:43 PM by 3004

    WebLogic web server plug-in problem

    3004
      I am using WebLogic 7 sp2, with one cluster contains 4 managed servers.
                
                Now the failover works, which means if I stop any 3 servers, the proxy
                server can dispatch the request to the last managed server.
                
                But, if all 4 server ups and running, the proxy server always dispatch all
                requests to one server. Attached is the web.xml of the proxy app. Please
                help. Thanks!
                
                <servlet>
                <servlet-name>HttpClusterServlet</servlet-name>
                <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                <init-param>
                <param-name>WebLogicCluster</param-name>
                <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                </init-param>
                <init-param>
                
                Joe
                
                
                
        • 1. Re: WebLogic web server plug-in problem
          3004
          How do you send your requests to the server? If its from a browser - try
                    using two different browsers and see where the request goes.
                    
                    /
                    sree
                    
                    "joe" <smartgege@yahoo.com> wrote in message
                    news:3eaa0c48@newsgroups.bea.com...
                    > I am using WebLogic 7 sp2, with one cluster contains 4 managed servers.
                    >
                    > Now the failover works, which means if I stop any 3 servers, the proxy
                    > server can dispatch the request to the last managed server.
                    >
                    > But, if all 4 server ups and running, the proxy server always dispatch
                    all
                    > requests to one server. Attached is the web.xml of the proxy app. Please
                    > help. Thanks!
                    >
                    > <servlet>
                    > <servlet-name>HttpClusterServlet</servlet-name>
                    >
                    <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                    > <init-param>
                    > <param-name>WebLogicCluster</param-name>
                    > <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                    > </init-param>
                    > <init-param>
                    >
                    > Joe
                    >
                    >
                    
                    
                    
          • 2. Re: WebLogic web server plug-in problem
            3004

                      Hi,
                      
                      I am using the same setup as yours, such as WLS 7 sp2 and WebLogic Proxy Plugin.
                      I am getting the opposite result to yours.
                      
                      For my case, the http request is not sticky to one particular server within one
                      session. That means it actually randomly goes to other server while it is in
                      one session. Since my application is not implementing HTTP session replication,
                      my application won't work once it is load balanced to another server at runtime.
                      
                      
                      Note, you have to tested for long enough. It doesn't always happen. It randomly
                      goes to another server. That is not good for our application. Did you do anything
                      special to keep a sticky connection to a particular server? I guess not, right?
                      Since your HTTPClusterServlet looked the same as mine.
                      
                      
                      
                      --Carole
                      
                      "joe" <smartgege@yahoo.com> wrote:
                      >I am using WebLogic 7 sp2, with one cluster contains 4 managed servers.
                      >
                      >Now the failover works, which means if I stop any 3 servers, the proxy
                      >server can dispatch the request to the last managed server.
                      >
                      >But, if all 4 server ups and running, the proxy server always dispatch
                      >all
                      >requests to one server. Attached is the web.xml of the proxy app. Please
                      >help. Thanks!
                      >
                      > <servlet>
                      > <servlet-name>HttpClusterServlet</servlet-name>
                      > <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                      > <init-param>
                      > <param-name>WebLogicCluster</param-name>
                      > <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                      > </init-param>
                      > <init-param>
                      >
                      >Joe
                      >
                      >
                      
                      
            • 3. Re: WebLogic web server plug-in problem
              3004
              I am using LoadRunner to do the stress test. In a 800 users test, I noticed
                        all the requests were dispatched to one server, the other 3 servers had no
                        load at all.
                        
                        But the fail over works, which means if I stop the first server, the other 3
                        servers can handle new requests.
                        
                        No we are not doing anything to stick to a particular server, that is also
                        the reason why the websphere 5.0 clustering works with our application.
                        
                        Joe
                        "Carole Yang" <shaoxian_yang@yahoo.com> wrote in message
                        news:3ead92c3@newsgroups.bea.com...
                        >
                        > Hi,
                        >
                        > I am using the same setup as yours, such as WLS 7 sp2 and WebLogic Proxy
                        Plugin.
                        > I am getting the opposite result to yours.
                        >
                        > For my case, the http request is not sticky to one particular server
                        within one
                        > session. That means it actually randomly goes to other server while it is
                        in
                        > one session. Since my application is not implementing HTTP session
                        replication,
                        > my application won't work once it is load balanced to another server at
                        runtime.
                        >
                        >
                        > Note, you have to tested for long enough. It doesn't always happen. It
                        randomly
                        > goes to another server. That is not good for our application. Did you do
                        anything
                        > special to keep a sticky connection to a particular server? I guess not,
                        right?
                        > Since your HTTPClusterServlet looked the same as mine.
                        >
                        >
                        >
                        > --Carole
                        >
                        > "joe" <smartgege@yahoo.com> wrote:
                        > >I am using WebLogic 7 sp2, with one cluster contains 4 managed servers.
                        > >
                        > >Now the failover works, which means if I stop any 3 servers, the proxy
                        > >server can dispatch the request to the last managed server.
                        > >
                        > >But, if all 4 server ups and running, the proxy server always dispatch
                        > >all
                        > >requests to one server. Attached is the web.xml of the proxy app. Please
                        > >help. Thanks!
                        > >
                        > > <servlet>
                        > > <servlet-name>HttpClusterServlet</servlet-name>
                        > >
                        <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                        > > <init-param>
                        > > <param-name>WebLogicCluster</param-name>
                        > > <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                        > > </init-param>
                        > > <init-param>
                        > >
                        > >Joe
                        > >
                        > >
                        >
                        
                        
                        
              • 4. Re: WebLogic web server plug-in problem
                3004
                Its from an embeded ie browser in loadrunner.
                          
                          I wrote a test jsp page to display the ip address. Each time I open a new
                          browser window and point it to http://proxyserver:8300/test.jsp
                          it will return the same ip address.
                          
                          
                          Joe
                          "Sree Bodapati" <post@bea.newsgroup.iwillreply> wrote in message
                          news:3ead3a6a$1@newsgroups.bea.com...
                          > How do you send your requests to the server? If its from a browser - try
                          > using two different browsers and see where the request goes.
                          >
                          > /
                          > sree
                          >
                          > "joe" <smartgege@yahoo.com> wrote in message
                          > news:3eaa0c48@newsgroups.bea.com...
                          > > I am using WebLogic 7 sp2, with one cluster contains 4 managed servers.
                          > >
                          > > Now the failover works, which means if I stop any 3 servers, the proxy
                          > > server can dispatch the request to the last managed server.
                          > >
                          > > But, if all 4 server ups and running, the proxy server always dispatch
                          > all
                          > > requests to one server. Attached is the web.xml of the proxy app.
                          Please
                          > > help. Thanks!
                          > >
                          > > <servlet>
                          > > <servlet-name>HttpClusterServlet</servlet-name>
                          > >
                          > <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                          > > <init-param>
                          > > <param-name>WebLogicCluster</param-name>
                          > > <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                          > > </init-param>
                          > > <init-param>
                          > >
                          > > Joe
                          > >
                          > >
                          >
                          >
                          
                          
                          
                • 5. Re: WebLogic web server plug-in problem
                  3004
                  This problem is fixed by setting DynamicServerList to OFF.
                            
                            "joe" <smartgege@yahoo.com> wrote in message
                            news:3eade3a1@newsgroups.bea.com...
                            > I am using LoadRunner to do the stress test. In a 800 users test, I
                            noticed
                            > all the requests were dispatched to one server, the other 3 servers had no
                            > load at all.
                            >
                            > But the fail over works, which means if I stop the first server, the other
                            3
                            > servers can handle new requests.
                            >
                            > No we are not doing anything to stick to a particular server, that is also
                            > the reason why the websphere 5.0 clustering works with our application.
                            >
                            > Joe
                            > "Carole Yang" <shaoxian_yang@yahoo.com> wrote in message
                            > news:3ead92c3@newsgroups.bea.com...
                            > >
                            > > Hi,
                            > >
                            > > I am using the same setup as yours, such as WLS 7 sp2 and WebLogic Proxy
                            > Plugin.
                            > > I am getting the opposite result to yours.
                            > >
                            > > For my case, the http request is not sticky to one particular server
                            > within one
                            > > session. That means it actually randomly goes to other server while it
                            is
                            > in
                            > > one session. Since my application is not implementing HTTP session
                            > replication,
                            > > my application won't work once it is load balanced to another server at
                            > runtime.
                            > >
                            > >
                            > > Note, you have to tested for long enough. It doesn't always happen. It
                            > randomly
                            > > goes to another server. That is not good for our application. Did you
                            do
                            > anything
                            > > special to keep a sticky connection to a particular server? I guess
                            not,
                            > right?
                            > > Since your HTTPClusterServlet looked the same as mine.
                            > >
                            > >
                            > >
                            > > --Carole
                            > >
                            > > "joe" <smartgege@yahoo.com> wrote:
                            > > >I am using WebLogic 7 sp2, with one cluster contains 4 managed servers.
                            > > >
                            > > >Now the failover works, which means if I stop any 3 servers, the proxy
                            > > >server can dispatch the request to the last managed server.
                            > > >
                            > > >But, if all 4 server ups and running, the proxy server always dispatch
                            > > >all
                            > > >requests to one server. Attached is the web.xml of the proxy app.
                            Please
                            > > >help. Thanks!
                            > > >
                            > > > <servlet>
                            > > > <servlet-name>HttpClusterServlet</servlet-name>
                            > > >
                            > <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                            > > > <init-param>
                            > > > <param-name>WebLogicCluster</param-name>
                            > > > <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                            > > > </init-param>
                            > > > <init-param>
                            > > >
                            > > >Joe
                            > > >
                            > > >
                            > >
                            >
                            >
                            
                            
                            
                  • 6. Re: WebLogic web server plug-in problem
                    3004
                    If that makes it work, then it means clustering is not working correctly.
                              When setting DynamicServerList off, the list returned from WebLogic to the
                              plugin is not used.
                              
                              When it is set to ON, then it will use the list from WLS.
                              
                              Now, if all requests went to only the 1st server, that means that the
                              dynamic list returned to the plugin only contained one server(itself). That
                              means clustering is not setup correctly for the servers. Make sure
                              multicast is working and that all the servers join the cluster.
                              
                              Regards,
                              
                              Eric
                              
                              "joe" <smartgege@yahoo.com> wrote in message
                              news:3eb0290f@newsgroups.bea.com...
                              > This problem is fixed by setting DynamicServerList to OFF.
                              >
                              > "joe" <smartgege@yahoo.com> wrote in message
                              > news:3eade3a1@newsgroups.bea.com...
                              > > I am using LoadRunner to do the stress test. In a 800 users test, I
                              > noticed
                              > > all the requests were dispatched to one server, the other 3 servers had
                              no
                              > > load at all.
                              > >
                              > > But the fail over works, which means if I stop the first server, the
                              other
                              > 3
                              > > servers can handle new requests.
                              > >
                              > > No we are not doing anything to stick to a particular server, that is
                              also
                              > > the reason why the websphere 5.0 clustering works with our application.
                              > >
                              > > Joe
                              > > "Carole Yang" <shaoxian_yang@yahoo.com> wrote in message
                              > > news:3ead92c3@newsgroups.bea.com...
                              > > >
                              > > > Hi,
                              > > >
                              > > > I am using the same setup as yours, such as WLS 7 sp2 and WebLogic
                              Proxy
                              > > Plugin.
                              > > > I am getting the opposite result to yours.
                              > > >
                              > > > For my case, the http request is not sticky to one particular server
                              > > within one
                              > > > session. That means it actually randomly goes to other server while
                              it
                              > is
                              > > in
                              > > > one session. Since my application is not implementing HTTP session
                              > > replication,
                              > > > my application won't work once it is load balanced to another server
                              at
                              > > runtime.
                              > > >
                              > > >
                              > > > Note, you have to tested for long enough. It doesn't always happen.
                              It
                              > > randomly
                              > > > goes to another server. That is not good for our application. Did
                              you
                              > do
                              > > anything
                              > > > special to keep a sticky connection to a particular server? I guess
                              > not,
                              > > right?
                              > > > Since your HTTPClusterServlet looked the same as mine.
                              > > >
                              > > >
                              > > >
                              > > > --Carole
                              > > >
                              > > > "joe" <smartgege@yahoo.com> wrote:
                              > > > >I am using WebLogic 7 sp2, with one cluster contains 4 managed
                              servers.
                              > > > >
                              > > > >Now the failover works, which means if I stop any 3 servers, the
                              proxy
                              > > > >server can dispatch the request to the last managed server.
                              > > > >
                              > > > >But, if all 4 server ups and running, the proxy server always
                              dispatch
                              > > > >all
                              > > > >requests to one server. Attached is the web.xml of the proxy app.
                              > Please
                              > > > >help. Thanks!
                              > > > >
                              > > > > <servlet>
                              > > > > <servlet-name>HttpClusterServlet</servlet-name>
                              > > > >
                              > > <servlet-class>weblogic.servlet.proxy.HttpClusterServlet</servlet-class>
                              > > > > <init-param>
                              > > > > <param-name>WebLogicCluster</param-name>
                              > > > > <param-value>ip1:8300|ip2:8300|ip3:8300|ip4:8300</param-value>
                              > > > > </init-param>
                              > > > > <init-param>
                              > > > >
                              > > > >Joe
                              > > > >
                              > > > >
                              > > >
                              > >
                              > >
                              >
                              >