Cluster IMR problem?

Question

          Hi,
          I have a configuration where a single Apache running the WLS-plugin
          fronts two WLS instances executing on the same, multihomed Solaris
          machine. The cluster specific weblogic.properties file contains the
          following:
          weblogic.httpd.clustering.enable=true
          weblogic.httpd.session.persistence=true
          weblogic.httpd.session.persistentStoreType=replicated
          Static pages and servlets not depending on HTTP session state work fine
          but when I try to run the example session servlet
          (examples.servlets.SessionServlet) the web browser never gets any
          response. I can't find anything suspicous in the log files.
          Does anybody have any idea of what could be wrong? Is there a simple way
          to verify that the clustering config, the multicast address etc is okay?
          Thank you
          Patrik
          

Answer 1

          Yep, that definately made a difference. It works now - thanks!
          Cheers
          Patrik
          Wei Guan skrev:
          > What is your SP? Could you try SP4?
          >
          > --
          > Cheers - Wei
          >
          > Patrik Gottfridsson <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > The weblogic.httpd.clustering.enable is set on the command line in the
          > startup
          > > script. Also, I ran the multicastTest utility after shutting down the
          > > application server. So neither of these should cause any problems. The
          > strange
          > > thing is that everything looks normal. I get some nice messages in the
          > > weblogic.log saying that both WLS instances join the cluster and so on.
          > >
          > > To debug I tried set this property in the cluster-wide config file:
          > >
          > > weblogic.debug.replication=2
          > >
          > > and this resulted in the following message in the weblogic.log of the
          > primary
          > > WLS:
          > >
          > > Thu Aug 17 16:36:35 GMT+02:00 2000:<I> <RepMan> Trying to create secondary
          > for
          > > 5449997915261938767 on new host
          > > 5557948761125425783S192.168.1.235:[7001,7001,7002,7002,7001,-1]
          > >
          > > and then nothing more (browser hung). Should the trace contain something
          > more,
          > > e.g. "Secondary created ok .."? I guess this would imply that the
          > replication
          > > fails in some way.
          > >
          > > Cheers
          > >
          > > Patrik
          > >
          > >
          > >
          > > Wei Guan skrev:
          > >
          > > > weblogic.httpd.clustering.enable=true must be set in startup script.
          > > >
          > > > --
          > > > Cheers - Wei
          > > >
          > > > Vincent Wong <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > >
          > > > > Hi,
          > > > >
          > > > > I have a configuration where a single Apache running the WLS-plugin
          > > > > fronts two WLS instances executing on the same, multihomed Solaris
          > > > > machine. The cluster specific weblogic.properties file contains the
          > > > > following:
          > > > >
          > > > > weblogic.httpd.clustering.enable=true
          > > > > weblogic.httpd.session.persistence=true
          > > > > weblogic.httpd.session.persistentStoreType=replicated
          > > > >
          > > > > Static pages and servlets not depending on HTTP session state work
          > fine
          > > > > but when I try to run the example session servlet
          > > > > (examples.servlets.SessionServlet) the web browser never gets any
          > > > > response. I can't find anything suspicous in the log files.
          > > > >
          > > > > Does anybody have any idea of what could be wrong? Is there a simple
          > way
          > > > > to verify that the clustering config, the multicast address etc is
          > okay?
          > > > >
          > > > > Thank you
          > > > >
          > > > > Patrik
          > > > >
          > >