Setting up a cluster for the first time: newbie questions

Question

Any help appreciated with this situation:
          I'm trying to set up a cluster for the first time and running into
          issues (no big surprise). I'll outline my situation and pose questions
          as they arise. If/when I get things to work I'll post a step-by-step
          summary of what it took to get a simple cluster going.
          Here's what I have:
          machines:
          1 Windows 2000 machines with WL 6.1
          2 RedHat Linux machines with WL 6.1
          All machines are on the same Home LAN, can see each other, etc.
          IP addresses are:
          Windows box: 192.168.1.100
          Linux box 1: 192.168.1.102
          Linux box 2: 192.168.1.103
          servers:
          I've set up the Windows machine as my admin server, and set up
          a managed server on each Linux machine. I created a cluster that consists
          of the 2 Linux machines and deployed the web app and EJB to the cluster.
          The Windows machine is acting as a Proxy using ClusterServlet.
          The web application has been set as the Default Web Application on the
          two Linux machines. All 3 machines are listening on ports 80/443. I also
          set up session memory replication through the console.
          Application:
          I have an application that I package as an EAR file. I'm using it as a
          "reference" application designed to mimic a real world app as much as possible.
          The EAR file contains a web application that uses Struts. It also consists
          of a single Stateless Session Bean. The WAR file and EJB Jar are all
          packaged up into the EAR file. I've been able to run this application just
          fine on a single managed server on all 3 machines.
          The web application works fine, and it can invoke the EJB. I can also
          invoke the EJB from Java stand-alone clients. Struts works great. All is
          well with the world. Now I'm trying to "cluster-ize" this app using
          the environment described above and encountering issues.
          I've read the docs and followed the instructions according to the
          "Weblogic Bible" book. I can bring up all 3 servers and the Linux
          managed servers connect to the cluster just fine. I can also
          see the Struts messages in their logs which normally happens and tells me
          the webapp is initialized properly. The console tells me that the managed
          servers are running. I get no error messages starting up any of the serves.
          Here are the problems I am encountering.
          When I try to access the Web Application (through a browser on the
          Windows machine using http://localhost) I get the following error message:
          <Nov 19, 2002 6:44:33 AM EST> <Error> <HTTP> <HttpServer(1754841,null default ct
          x,admin) found no context for "/". This request does not match the context path
          for any installed web applications and there is no default web application confi
          gured.>
          Also, when I try to invoke the EJB through a stand-alone Java client,
          I get a JNDI lookup error on the EJB's home interface.
          Questions:
          Question1: I noticed when setting up the machines that console lets you
          define a "Machine" or a "Unix Machine". What's the difference? Should I
          define the Linux machines as Unix machines or machines, and what are the
          consequences of either choice?
          Question2:
          I'm not totally clear on how my web.xml should look to set up Struts,
          the ClusterServlet, and a servlet filter I'm using to test Servlet filters.
          Here is what I had before I tried to cluster and which works fine:
          <filter>
          <filter-name>MainFilter</filter-name>
          <filter-class>com.refapp.servlets.MainFilter</filter-class>
          <init-param>
          <param-name>myAttribute</param-name>
          <param-value>Foo</param-value>
          </init-param>
          </filter>
          <filter-mapping>
          <filter-name>MainFilter</filter-name>
          <url-pattern>/*</url-pattern>
          </filter-mapping
          <!-- Struts ActionServlet Configuration -->
          <servlet>
          <servlet-name>action</servlet-name>
          <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
          <init-param>
          <param-name>application</param-name>
          <param-value>refappstruts</param-value>
          </init-param>
          <init-param>
          <param-name>config</param-name>
          <param-value>/WEB-INF/struts-config.xml</param-value>
          </init-param>
          <init-param>
          <param-name>debug</param-name>
          <param-value>2</param-value>
          </init-param>
          <init-param>
          <param-name>mapping</param-name>
          <param-value>org.apache.struts.action.RequestActionMapping</param-value>
          </init-param>
          <load-on-startup>2</load-on-startup>
          </servlet>
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          <welcome-file-list>
          <welcome-file>index.do</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>index.html</welcome-file>
          </welcome-file-list>
          (I have set up a "dummy" 0-length file called index.do that triggers
          Struts to go into its ActionServlet when first accessing the web site).
          Here is how I added ClusterServlet to web.xml:
          servlet>
          <servlet-name>ClusterServlet</servlet-name>
          <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
          <load-on-startup>0</load-on-startup>
          <init-param>
          <param-name>defaultServers</param-name>
          <param-value>192.168.1.102:80:443|192.168.1.103:80:443</param-value>
          </init-param>
          <init-param>
          <param-name>DebugConfigInfo</param-name>
          <param-value>ON</param-value>
          </init-param>
          </servlet>
          <servlet-mapping>
          <servlet-name>InitServlet</servlet-name>
          <url-pattern>/servlet/InitServlet</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>/</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>*.html</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>*.jsp</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>ClusterServlet</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          Clearly there is a problem with the Default Web application not being
          seen/mapped properly. Any chances my URL mappings for the filter servlet,
          Struts, and ClusterServlet are stepping on each other?
          With respect to the EJB, here is what my weblogic-ejb-jar looks like:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>Hello</ejb-name>
          <stateless-session-descriptor>
          <pool>
               <max-beans-in-free-pool>100</max-beans-in-free-pool>
          </pool>
          <stateless-clustering>
          <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          <stateless-bean-load-algorithm>
          round-robin
          </stateless-bean-load-algorithm>
          <stateless-bean-methods-are-idempotent>
          true
          </stateless-bean-methods-are-idempotent>
          </stateless-clustering>
          </stateless-session-descriptor>
          <jndi-name>Hello.Home</jndi-name>
          </weblogic-enterprise-bean>
          I run this through ejbc and package everything up into the EAR file.
          However, I get a JNDI lookup failure when I try to access the Bean from
          a standalone Java client running on the Windows machine.
          Here is the jndi.properties file that I am using:
          java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
          java.naming.provider.url=t3://localhost:80
          Any ideas what I'm doing wrong here? I can post config.xml also if needed.
          Thanks in advance!
          

Answer 1

Let me try to answer :)....
          A1> No need to name diff machines by default weblogic
          considers the servers are physically located in diff boxes.
          The names are used to differtiate the mang servers which are in
          multihomed
          Some things to chk
          1> Did u targeted the ear file Target as cluster.
          2> Can u see on the Admin console that both the man servers
          are participated in the cluster( u can see by clicking the monitoring
          tab on the Cluster node).
          3>Is the URL:PORT for the default web app correct?
          the reason: is I dont see the port# on the link u mentioned
          4> probably ur ejb might not been deployed on the target thats the
          reason u cant access thru java client. If u correct the targets that
          will probably fix it.
          Hope this helps
          Please post the result
          Thanks
          Sudhir
          [email protected] (Chris) wrote in message news:<[email protected]>...
          > Any help appreciated with this situation:
          > I'm trying to set up a cluster for the first time and running into
          > issues (no big surprise). I'll outline my situation and pose questions
          > as they arise. If/when I get things to work I'll post a step-by-step
          > summary of what it took to get a simple cluster going.
          > Here's what I have:
          >
          > machines:
          > 1 Windows 2000 machines with WL 6.1
          > 2 RedHat Linux machines with WL 6.1
          > All machines are on the same Home LAN, can see each other, etc.
          > IP addresses are:
          > Windows box: 192.168.1.100
          > Linux box 1: 192.168.1.102
          > Linux box 2: 192.168.1.103
          >
          > servers:
          > I've set up the Windows machine as my admin server, and set up
          > a managed server on each Linux machine. I created a cluster that consists
          > of the 2 Linux machines and deployed the web app and EJB to the cluster.
          > The Windows machine is acting as a Proxy using ClusterServlet.
          > The web application has been set as the Default Web Application on the
          > two Linux machines. All 3 machines are listening on ports 80/443. I also
          > set up session memory replication through the console.
          >
          > Application:
          > I have an application that I package as an EAR file. I'm using it as a
          > "reference" application designed to mimic a real world app as much as possible.
          > The EAR file contains a web application that uses Struts. It also consists
          > of a single Stateless Session Bean. The WAR file and EJB Jar are all
          > packaged up into the EAR file. I've been able to run this application just
          > fine on a single managed server on all 3 machines.
          > The web application works fine, and it can invoke the EJB. I can also
          > invoke the EJB from Java stand-alone clients. Struts works great. All is
          > well with the world. Now I'm trying to "cluster-ize" this app using
          > the environment described above and encountering issues.
          >
          > I've read the docs and followed the instructions according to the
          > "Weblogic Bible" book. I can bring up all 3 servers and the Linux
          > managed servers connect to the cluster just fine. I can also
          > see the Struts messages in their logs which normally happens and tells me
          > the webapp is initialized properly. The console tells me that the managed
          > servers are running. I get no error messages starting up any of the serves.
          >
          > Here are the problems I am encountering.
          >
          > When I try to access the Web Application (through a browser on the
          > Windows machine using http://localhost) I get the following error message:
          >
          > <Nov 19, 2002 6:44:33 AM EST> <Error> <HTTP> <HttpServer(1754841,null default ct
          > x,admin) found no context for "/". This request does not match the context path
          > for any installed web applications and there is no default web application confi
          > gured.>
          >
          > Also, when I try to invoke the EJB through a stand-alone Java client,
          > I get a JNDI lookup error on the EJB's home interface.
          >
          > Questions:
          > Question1: I noticed when setting up the machines that console lets you
          > define a "Machine" or a "Unix Machine". What's the difference? Should I
          > define the Linux machines as Unix machines or machines, and what are the
          > consequences of either choice?
          >
          > Question2:
          > I'm not totally clear on how my web.xml should look to set up Struts,
          > the ClusterServlet, and a servlet filter I'm using to test Servlet filters.
          > Here is what I had before I tried to cluster and which works fine:
          >
          > <filter>
          > <filter-name>MainFilter</filter-name>
          > <filter-class>com.refapp.servlets.MainFilter</filter-class>
          > <init-param>
          > <param-name>myAttribute</param-name>
          > <param-value>Foo</param-value>
          > </init-param>
          > </filter>
          >
          > <filter-mapping>
          > <filter-name>MainFilter</filter-name>
          > <url-pattern>/*</url-pattern>
          > </filter-mapping
          >
          >
          > <!-- Struts ActionServlet Configuration -->
          > <servlet>
          > <servlet-name>action</servlet-name>
          > <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
          >
          > <init-param>
          > <param-name>application</param-name>
          > <param-value>refappstruts</param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>config</param-name>
          > <param-value>/WEB-INF/struts-config.xml</param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>debug</param-name>
          > <param-value>2</param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>mapping</param-name>
          > <param-value>org.apache.struts.action.RequestActionMapping</param-value>
          > </init-param>
          > <load-on-startup>2</load-on-startup>
          > </servlet>
          >
          > <servlet-mapping>
          > <servlet-name>action</servlet-name>
          > <url-pattern>*.do</url-pattern>
          > </servlet-mapping>
          >
          > <welcome-file-list>
          > <welcome-file>index.do</welcome-file>
          > <welcome-file>index.jsp</welcome-file>
          > <welcome-file>index.html</welcome-file>
          > </welcome-file-list>
          >
          > (I have set up a "dummy" 0-length file called index.do that triggers
          > Struts to go into its ActionServlet when first accessing the web site).
          >
          > Here is how I added ClusterServlet to web.xml:
          >
          > servlet>
          > <servlet-name>ClusterServlet</servlet-name>
          > <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
          > <load-on-startup>0</load-on-startup>
          > <init-param>
          > <param-name>defaultServers</param-name>
          > <param-value>192.168.1.102:80:443|192.168.1.103:80:443</param-value>
          > </init-param>
          > <init-param>
          > <param-name>DebugConfigInfo</param-name>
          > <param-value>ON</param-value>
          > </init-param>
          > </servlet>
          >
          > <servlet-mapping>
          > <servlet-name>InitServlet</servlet-name>
          > <url-pattern>/servlet/InitServlet</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>action</servlet-name>
          > <url-pattern>*.do</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>/</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>*.html</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>*.jsp</url-pattern>
          > </servlet-mapping>
          >
          > <servlet-mapping>
          > <servlet-name>ClusterServlet</servlet-name>
          > <url-pattern>*.do</url-pattern>
          > </servlet-mapping>
          >
          >
          > Clearly there is a problem with the Default Web application not being
          > seen/mapped properly. Any chances my URL mappings for the filter servlet,
          > Struts, and ClusterServlet are stepping on each other?
          >
          > With respect to the EJB, here is what my weblogic-ejb-jar looks like:
          >
          > <weblogic-ejb-jar>
          > <weblogic-enterprise-bean>
          > <ejb-name>Hello</ejb-name>
          > <stateless-session-descriptor>
          > <pool>
          >      <max-beans-in-free-pool>100</max-beans-in-free-pool>
          > </pool>
          > <stateless-clustering>
          > <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          > <stateless-bean-load-algorithm>
          > round-robin
          > </stateless-bean-load-algorithm>
          > <stateless-bean-methods-are-idempotent>
          > true
          > </stateless-bean-methods-are-idempotent>
          > </stateless-clustering>
          > </stateless-session-descriptor>
          > <jndi-name>Hello.Home</jndi-name>
          > </weblogic-enterprise-bean>
          >
          > I run this through ejbc and package everything up into the EAR file.
          > However, I get a JNDI lookup failure when I try to access the Bean from
          > a standalone Java client running on the Windows machine.
          > Here is the jndi.properties file that I am using:
          >
          > java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
          > java.naming.provider.url=t3://localhost:80
          >
          > Any ideas what I'm doing wrong here? I can post config.xml also if needed.
          >
          > Thanks in advance!