Clustering issues with 4.5.1

Question

We are using Weblogic 4.5.1 with sp7 and have heard that there are
          issues with Weblogic clustering. Specifically, the IIS plugin having
          memory leaks, and 4.5.1 with sp7 has issues when implementing clustering
          (the app servers in the cluster sometimes do not respond and sometimes
          contend for who owns the next request coming from the proxy). I've also
          seen that when a HTTP 1.1 request comes to the Web server, the proxy
          sends a HTTP 1.0 request to the App server. I've also heard that sp10,
          due out in July will fix these issues. Can anyone verify this?
          Also, I want to make sure that our proposed configuration can work in a
          clustered environment. I have two IIS Web servers, WebA and WebB, and
          also two Application servers running 4.5.1 sp7, AppA and AppB. Both Web
          servers are identical and both App servers are identical. Our Weblogic
          ListenPort is 7005
          If I set up WebA's iisproxy.ini file to contain the line
          "WebLogicCluster=AppA:7005,AppB:7005"
          I then copy WebA's iisproxy.ini file to WebB so that the two
          iisproxy.ini files are identical.
          The App servers have an identical configuration and point to 237.0.0.1
          as their multicast IP address.
          Is this configuration ok? Can two web servers point to the same two App
          servers in the cluster, or does each Web server need it's own "cluster"
          of App servers.
          Thanks in advance...
          

Answer 1

What was that issue with deadlock and where is it described?
          Prasad Peddada wrote:
          > Also there was a dead lock issue with sp7 which was fixed in the later service
          > packs.
          >
          > Vinod Mehra wrote:
          >
          > > >> Specifically, the IIS plugin having memory leaks,
          > > These have already been fixed with SP7.
          > >
          > > >>and 4.5.1 with sp7 has issues when implementing clustering
          > > >>(the app servers in the cluster sometimes do not respond and sometimes
          > > >>contend for who owns the next request coming from the proxy).
          > >
          > > WebLogic server not responding can be because of many reasons. Most of the
          > > time it is because of bad configurations and sometimes because of
          > > Application
          > > problems itself. Now about recovering from such a hung server SP8 onwards
          > > the plugin-ins have a configurable parameter "HungServerRecoverySecs",
          > > using which the plug-ins mark that server as bad (temporarily) and
          > > the requets failover to the SECONDARY.
          > >
          > > >> I've also seen that when a HTTP 1.1 request comes to the Web server, the
          > > proxy
          > > >>sends a HTTP 1.0 request to the App server.
          > >
          > > 4.5.1 does noes not support HTTP1.1 yet. So they will still be HTTP1.0.
          > >
          > > >> I've also heard that sp10, due out in July will fix these issues. Can
          > > anyone verify this?
          > > Yes. Except the last one.
          > >
          > > >> Is this configuration ok?
          > > Yes the configuration you have described is a valid one.
          > >
          > > --Vinod.
          > >
          > > lynch wrote:
          > >
          > > > We are using Weblogic 4.5.1 with sp7 and have heard that there are
          > > > issues with Weblogic clustering. Specifically, the IIS plugin having
          > > > memory leaks, and 4.5.1 with sp7 has issues when implementing clustering
          > > > (the app servers in the cluster sometimes do not respond and sometimes
          > > > contend for who owns the next request coming from the proxy). I've also
          > > > seen that when a HTTP 1.1 request comes to the Web server, the proxy
          > > > sends a HTTP 1.0 request to the App server. I've also heard that sp10,
          > > > due out in July will fix these issues. Can anyone verify this?
          > > >
          > > > Also, I want to make sure that our proposed configuration can work in a
          > > > clustered environment. I have two IIS Web servers, WebA and WebB, and
          > > > also two Application servers running 4.5.1 sp7, AppA and AppB. Both Web
          > > > servers are identical and both App servers are identical. Our Weblogic
          > > > ListenPort is 7005
          > > >
          > > > If I set up WebA's iisproxy.ini file to contain the line
          > > > "WebLogicCluster=AppA:7005,AppB:7005"
          > > >
          > > > I then copy WebA's iisproxy.ini file to WebB so that the two
          > > > iisproxy.ini files are identical.
          > > >
          > > > The App servers have an identical configuration and point to 237.0.0.1
          > > > as their multicast IP address.
          > > >
          > > > Is this configuration ok? Can two web servers point to the same two App
          > > > servers in the cluster, or does each Web server need it's own "cluster"
          > > > of App servers.
          > > >
          > > > Thanks in advance...