WL6.1 Clustering

          We are setting up Clustering for WL6.1 with a Admin Server and a Managed Server
          on different machines. All beans are deployed on Managed Server. Everything looks
          fine and we can run applications too. But in console, we got the following Exception.
          Can anyone help?
          thanks,
          Hong
          javax.naming.NameNotFoundException: Unable to resolve comp.env Resolved: '' Unresolved:'comp'
          ; remaining name 'env'
          <>
          --------------- nested within: ------------------
          weblogic.management.console.actions.ActionException: Unable to resolve comp.env
          Resolved: '' Unresolved:'comp' - with nested exception:
          [javax.naming.NameNotFoundException: Unable to resolve comp.env Resolved:
          '' Unresolved:'comp' ; remaining name 'env']
          at weblogic.management.console.actions.ErrorAction.(ErrorAction.java:38)
          at weblogic.management.console.actions.jndi.ViewJndiContextAction.perform(ViewJndiContextAction.java:50)
          at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
          at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          

          We are setting up Clustering for WL6.1 with a Admin Server and a Managed Server
          on different machines. All beans are deployed on Managed Server. Everything looks
          fine and we can run applications too. But in console, we got the following Exception.
          Can anyone help?
          thanks,
          Hong
          javax.naming.NameNotFoundException: Unable to resolve comp.env Resolved: '' Unresolved:'comp'
          ; remaining name 'env'
          <>
          --------------- nested within: ------------------
          weblogic.management.console.actions.ActionException: Unable to resolve comp.env
          Resolved: '' Unresolved:'comp' - with nested exception:
          [javax.naming.NameNotFoundException: Unable to resolve comp.env Resolved:
          '' Unresolved:'comp' ; remaining name 'env']
          at weblogic.management.console.actions.ErrorAction.(ErrorAction.java:38)
          at weblogic.management.console.actions.jndi.ViewJndiContextAction.perform(ViewJndiContextAction.java:50)
          at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
          at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          

Similar Messages

  • Wl6.0 clustering error

              Hi,
              I have two weblogic servers on different m/cs in a cluster.When the request is going
              to one server it is showing the following error.What could be the reason?
              weblogic.cluster.replication.NotFoundException: Lost 2 updates of -525890432560839199
              at weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)
              at weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationManager_WLStub.java:316)
              at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:426)
              at weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessionData.java:398)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:147)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1526)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1310)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1622)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.NestedError: Could not find secondary on remote server - with nested
              exception:
              [weblogic.cluster.replication.NotFoundException: Lost 2 updates of -525890432560839199]
              at weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessionData.java:405)
              at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:147)
              at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1526)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1310)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1622)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              Thanks
              Venkat
              

              Hi Patrizia,
              I have been in touch with bea supoort since last two weeks. They are trying to
              find out the reason for this error.
              I have posted this question long back but nobody gave me answer.
              I think nobody has done clustering successfully on wl6.0sp1.
              If I find the reason I will let you know.
              Thanks
              Venkat
              Patrizia MB <[email protected]> wrote:
              >Hi Venkat,
              >I've just enabled In memory session replicaton and I've encountered EXACTLY
              >your problem which repeat whenever I
              >invoke my servlet. I've two WLS6SP1 instances running in cluster.
              >Have you understood why Weblogic throws those kind of exceptions?
              >I've looked up in other newsgroups (weblogic.developer.interest.clustering.in-memory-replication)
              >and the problem
              >seems very frequent... what is wrong in our cluster configuration???
              >
              >Thanks
              >
              >Patrizia
              >
              >
              >Venkat wrote:
              >
              >> Hi,
              >>
              >> I have two weblogic servers on different m/cs in a cluster.When the
              >request is going
              >> to one server it is showing the following error.What could be the reason?
              >>
              >> weblogic.cluster.replication.NotFoundException: Lost 2 updates of -525890432560839199
              >> at weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)
              >> at weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationManager_WLStub.java:316)
              >> at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:426)
              >> at weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessionData.java:398)
              >> at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:147)
              >> at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1526)
              >> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1310)
              >> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1622)
              >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >> --------------- nested within: ------------------
              >> weblogic.utils.NestedError: Could not find secondary on remote server
              >- with nested
              >> exception:
              >> [weblogic.cluster.replication.NotFoundException: Lost 2 updates of
              >-525890432560839199]
              >> at weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessionData.java:405)
              >> at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:147)
              >> at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1526)
              >> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1310)
              >> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1622)
              >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >> >
              >>
              >> Thanks
              >> Venkat
              >
              

  • Session not replicated in WL6.1

              We are having session-not-replicated problem in WL6.1 Clustering.
              We have 3 servers on different machines running WL6.1 sp1, 1 is running the admin
              server and the
              other 2 are running as managed weblogic server.
              We have a web application that has been deployed to the cluster and is set
              for PersistantStoreType equal to replicated.
              We are using a Cisco Local Redirector with "sticky load balancing" infront of
              the servers.
              In our applications, most of JSP pages can modify the session data using session.setAttribute().
              And we use session.removeAttribute() to clean a session data.
              session.setAttribute("mysession1", data1);
              ....some codes......
              if (session.getAttribute("mysession") != null)
                   session.removeAttribute("mysession");
              session.setAttribute("mysession", data2);
              With session.removeAttibute() in our codes, some session data is not replicated
              to secondary server.
              We checked all session data in secondary server after shutting down the primary
              server.
              But if we comment out all session.removeAttribute() methods, failovers tested
              successfully.
              All our session data is serializable. Some are String and Some are Objects.
              Is this a known problems in WL6.1? Anyone has any idea?
              thanks,
              Hong
              

              We are having session-not-replicated problem in WL6.1 Clustering.
              We have 3 servers on different machines running WL6.1 sp1, 1 is running the admin
              server and the
              other 2 are running as managed weblogic server.
              We have a web application that has been deployed to the cluster and is set
              for PersistantStoreType equal to replicated.
              We are using a Cisco Local Redirector with "sticky load balancing" infront of
              the servers.
              In our applications, most of JSP pages can modify the session data using session.setAttribute().
              And we use session.removeAttribute() to clean a session data.
              session.setAttribute("mysession1", data1);
              ....some codes......
              if (session.getAttribute("mysession") != null)
                   session.removeAttribute("mysession");
              session.setAttribute("mysession", data2);
              With session.removeAttibute() in our codes, some session data is not replicated
              to secondary server.
              We checked all session data in secondary server after shutting down the primary
              server.
              But if we comment out all session.removeAttribute() methods, failovers tested
              successfully.
              All our session data is serializable. Some are String and Some are Objects.
              Is this a known problems in WL6.1? Anyone has any idea?
              thanks,
              Hong
              

  • NumberFormatException on getEJBObject

              Hi,
              I got NumberFormatException when getEJBObject() is called in WL6.1 clustering.
              I suspect if the format of example for "Cluster Address list" at page 6-5 in
              "Using Weblogic Server Clusters" document is correct. According to the document,
              the field should accept the following format;
              192.168.0.50,192.168.0.51,192.168.0.52:7001
              I confirmed first operator of NumberFormatException is taken from the field by
              changing the port number.
              So, what is the correct syntax for "Cluster Address List" field?
              Here is the stacktrace;
              NumberFormatExceptionjava.lang.NumberFormatException: 7031:7031
              at java.lang.Integer.parseInt(Integer.java:423)
              at java.lang.Integer.parseInt(Integer.java:463)
              at weblogic.rjvm.ServerURL.parseURL(ServerURL.java:281)
              at weblogic.rjvm.ServerURL.<init>(ServerURL.java:69)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
              tialContextFactoryDelegate.java:261)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
              tialContextFactoryDelegate.java:203)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
              extFactory.java:124)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
              65)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
              at javax.naming.InitialContext.init(InitialContext.java:222)
              at javax.naming.InitialContext.<init>(InitialContext.java:198)
              at weblogic.ejb20.internal.HomeHandleImpl.getEJBHome(HomeHandleImpl.java
              :61)
              at weblogic.ejb20.internal.HandleImpl.getEJBObject(HandleImpl.java:134)
              at cygent.portal.frame.jsp.CygentHttpSessionState.releaseDataCursor(Cyge
              ntHttpSessionState.java:382)
              Thanks in advance,
              

              Hi,
              I got NumberFormatException when getEJBObject() is called in WL6.1 clustering.
              I suspect if the format of example for "Cluster Address list" at page 6-5 in
              "Using Weblogic Server Clusters" document is correct. According to the document,
              the field should accept the following format;
              192.168.0.50,192.168.0.51,192.168.0.52:7001
              I confirmed first operator of NumberFormatException is taken from the field by
              changing the port number.
              So, what is the correct syntax for "Cluster Address List" field?
              Here is the stacktrace;
              NumberFormatExceptionjava.lang.NumberFormatException: 7031:7031
              at java.lang.Integer.parseInt(Integer.java:423)
              at java.lang.Integer.parseInt(Integer.java:463)
              at weblogic.rjvm.ServerURL.parseURL(ServerURL.java:281)
              at weblogic.rjvm.ServerURL.<init>(ServerURL.java:69)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
              tialContextFactoryDelegate.java:261)
              at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
              tialContextFactoryDelegate.java:203)
              at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
              extFactory.java:124)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
              65)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
              at javax.naming.InitialContext.init(InitialContext.java:222)
              at javax.naming.InitialContext.<init>(InitialContext.java:198)
              at weblogic.ejb20.internal.HomeHandleImpl.getEJBHome(HomeHandleImpl.java
              :61)
              at weblogic.ejb20.internal.HandleImpl.getEJBObject(HandleImpl.java:134)
              at cygent.portal.frame.jsp.CygentHttpSessionState.releaseDataCursor(Cyge
              ntHttpSessionState.java:382)
              Thanks in advance,
              

  • Clustering with wl6.1 - Problems

    Hi,
              After reading a bit about clustering with weblogic 6.1 (and thanks to
              this list), I have done the following:
              1. Configure machines - two boxes (Solaris and Linux).
              2. Configure servers - weblogic 6.1 running on both at port 7001.
              3. Administration server is Win'XP. Here is the snippet of config.xml
              on the Administration Server:
              <Server Cluster="MyCluster" ListenAddress="192.168.1.239"
              Machine="dummy239" Name="wls239">
              <Log Name="wls239"/>
              <SSL Name="wls239"/>
              <ServerDebug Name="wls239"/>
              <KernelDebug Name="wls239"/>
              <ServerStart Name="wls239"/>
              <WebServer Name="wls239"/>
              </Server>
              <Server Cluster="MyCluster" ListenAddress="192.168.1.131"
              Machine="dummy131" Name="wls131">
              <Log Name="wls131"/>
              <SSL Name="wls131"/>
              <ServerDebug Name="wls131"/>
              <KernelDebug Name="wls131"/>
              <ServerStart Name="wls131"
              OutputFile="C:\bea\wlserver6.1\.\config\NodeManagerClientLogs\wls131\startserver_1029504698175.log"/>
              <WebServer Name="wls131"/>
              </Server>
              Problems:
              1. I can't figure out how I set the "OutputFile" parameter for the
              server "wls131".
              2. I have NodeManager started on 131 listening on port 5555. But when
              I try to start server "wls131" from the Administration Server, I get
              the following error:
              <Aug 16, 2002 6:56:58 AM PDT> <Error> <NodeManager> <Could not start
              server 'wls131' via Node Manager - reason: '[SecureCommandInvoker:
              Could not create a socket to the NodeManager running on host
              '192.168.1.131:5555' to execute command 'online null', reason:
              Connection refused: connect. Ensure that the NodeManager on host
              '192.168.1.131' is configured to listen on port '5555' and that it is
              actively listening]'
              Any help will be greatly appreciated.
              TIA,
              

    I have made some progress:
              1. The environment settings on 131 were missing. I executed setEnv.sh
              to setup the required environment variables.
              2. nodemanager.hosts (on 131) had the following entries earlier:
                   # more nodemanager.hosts
                   127.0.0.1
                   localhost
                   192.168.1.135
              I changed it to:
                   #more nodemanager.hosts
                   192.168.1.135
              3. The Administration Server (135) did not have any listen Address
              defined (since it was working without it), but since one of the errors
              thrown by NodeManager on 131 was - "could not connect to
              localhost:70001 via HTTP", I changed the listen Address to
              192.168.1.135 (instead of the null).
              4. I deleted all the logs (NodeManagerInternal logs on 131) and all
              log files on NodeManagerClientLogs on 135.
              5. Restarted Admin Server. Restarted NodeManager on 131.
              NodeManagerInternalLogs on 131 has:
                   [root@]# more NodeManagerInternal_1029567030003
                   <Aug 17, 2002 12:20:30 PM IST> <Info> <NodeManager> <Setting
              listenAddress to '1
                   92.168.1.131'>
                   <Aug 17, 2002 12:20:30 PM IST> <Info> <NodeManager> <Setting
              listenPort to '5555
                   '>
                   <Aug 17, 2002 12:20:30 PM IST> <Info> <NodeManager> <Setting WebLogic
              home to '/
                   home/weblogic/bea/wlserver6.1'>
                   <Aug 17, 2002 12:20:30 PM IST> <Info> <NodeManager> <Setting java
              home to '/home
                   /weblogic/jdk1.3.1_03'>
                   <Aug 17, 2002 12:20:33 PM IST> <Info>
              <[email protected]:5555> <SecureSo
                   cketListener: Enabled Ciphers >
                   <Aug 17, 2002 12:20:33 PM IST> <Info>
              <[email protected]:5555> <TLS_RSA_
                   EXPORT_WITH_RC4_40_MD5>
                   <Aug 17, 2002 12:20:33 PM IST> <Info>
              <[email protected]:5555> <SecureSo
                   cketListener: listening on 192.168.1.131:5555>
                   And the wls131 logs contain:
                   [root@dummy131 wls131]# more config
                   #Saved configuration for wls131
                   #Sat Aug 17 12:24:42 IST 2002
                   processId=18437
                   savedLogsDirectory=/home/weblogic/bea/wlserver6.1/NodeManagerLogs
                   classpath=NULL
                   nodemanager.debugEnabled=false
                   TimeStamp=1029567282621
                   command=online
                   java.security.policy=NULL
                   bea.home=NULL
                   weblogic.Domain=domain
                   serverStartArgs=NULL
                   weblogic.management.server=192.168.1.135\:7001
                   RootDirectory=NULL
                   nodemanager.sslEnabled=true
                   weblogic.Name=wls131
                   The error generated for the client (131) was:
                   [root@dummy131 wls131]# more wls131_error.log
                   The WebLogic Server did not start up properly.
                   Exception raised:
                   java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl
                   <<no stack trace available>>
                   --------------- nested within: ------------------
                   weblogic.management.configuration.ConfigurationException:
              weblogic.security.acl.
                   DefaultUserInfoImpl - with nested exception:
                   [java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl]
                   at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:1042)
                   at weblogic.management.Admin.start(Admin.java:381)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:373)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
                   at weblogic.Server.main(Server.java:35)
                   Reason: Fatal initialization exception
                   and the output on the admin server (135) is:
                   <Aug 17, 2002 12:24:42 PM IST> <Info>
              <[email protected]:5555> <BaseProcessControl: saving process
              id of Weblogic Managed server 'wls131', pid: 18437>
                   Starting WebLogic Server ....
                   Connecting to http://192.168.1.135:7001...
                   <Aug 17, 2002 12:24:50 PM IST> <Emergency> <Configuration Management>
              <Errors detected attempting to connect to admin server at
              192.168.1.135:7001 during initialization of managed server (
              192.168.1.131:7001 ). The reported error was: <
              weblogic.security.acl.DefaultUserInfoImpl > This condition generally
              results when the managed and admin servers are using the same listen
              address and port.>
                   <Aug 17, 2002 12:24:50 PM IST> <Emergency> <Server> <Unable to
              initialize the server: 'Fatal initialization exception
                   Throwable: weblogic.management.configuration.ConfigurationException:
              weblogic.security.acl.DefaultUserInfoImpl - with nested exception:
                   [java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl]
                   java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl
                   <<no stack trace available>>
                   --------------- nested within: ------------------
                   weblogic.management.configuration.ConfigurationException:
              weblogic.security.acl.DefaultUserInfoImpl - with nested exception:
                   [java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl]
                   at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:1042)
                   at weblogic.management.Admin.start(Admin.java:381)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:373)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
                   at weblogic.Server.main(Server.java:35)
                   '>
                   The WebLogic Server did not start up properly.
                   Exception raised:
                   java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl
                   <<no stack trace available>>
                   --------------- nested within: ------------------
                   weblogic.management.configuration.ConfigurationException:
              weblogic.security.acl.DefaultUserInfoImpl - with nested exception:
                   [java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl]
                   at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:1042)
                   at weblogic.management.Admin.start(Admin.java:381)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:373)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
                   at weblogic.Server.main(Server.java:35)
                   Reason: Fatal initialization exception
              6. Now from the client (131) error, I thought it was something to do
              with security. So I tried to start weblogic manually (connected as the
              same user). Curiosly enough, it does start (it threw some errors for
              some EJBs, but I got the final message):
                   <Aug 17, 2002 12:30:39 PM IST> <Notice> <WebLogicServer>
              <ListenThread listening on port 7001>
                   <Aug 17, 2002 12:30:39 PM IST> <Notice> <WebLogicServer>
              <SSLListenThread listening on port 7002>
                   <Aug 17, 2002 12:30:40 PM IST> <Notice> <WebLogicServer> <Started
              WebLogic Admin Server "myserver" for domain "mydomain" running in
              Production Mode>
              7. As you can see the domain on the client (131) is "mydomain". But
              shouldn't the Admin server be 192.168.1.135, since this is what I have
              configured for the NodeManager? Or is it that the error occurs because
              the Admin server Node Manager is configured to work with is 135, while
              in the default scripts the admin server is itself? I'm confused :-)
              Help, anyone?
              

  • Beginner,  want to test clustering sample on WL6.1

              Hi,
              I have just started reading on clustering. I want to test the
              clustering example given with Weblogic 6.1 on Win 2k.
              The first thing I want to know is can I test on one Machine.
              That is I want to have Adminstration server, and one managed
              server(at least, on one machine). If yes how do it do it ?
              TIA
              Ashwani
              

              Thanks Kumar, How can I configure this. Any pointer. or any weblogic document
              Ashwani
              Kumar Allamraju <[email protected]> wrote:
              >Yes , you can test clustering in a single box.
              >Make sure this machine is multihomed.
              >i.e. multiple IP's configured to this box.
              >
              >--
              >Kumar
              >
              >Ashwani Kalra wrote:
              >
              >> Hi,
              >> I have just started reading on clustering. I want to test the
              >> clustering example given with Weblogic 6.1 on Win 2k.
              >>
              >> The first thing I want to know is can I test on one Machine.
              >> That is I want to have Adminstration server, and one managed
              >> server(at least, on one machine). If yes how do it do it ?
              >>
              >> TIA
              >> Ashwani
              >
              

  • Ejb wl5.1 client talking to ejb wl6.1 server?

    I have a session ejb running in wl 5.1 that must act as a client of a wl6.1
    ejb (wl 6.1 running on another host). Since the RMI layer is incompatible
    between 5.1 and 6.1 I must jump through some hoops to get this to work. I've
    considered packaging the wl6.1 classes together with the 6.1 client classes
    in a separate jar, along with a helper class to use a separate classloader
    to load classes from that jar (in the hopes of keeping the common rmi
    classes in a separate namespace). Does this sound like the best approach?
    Has anyone else faced this problem? What other solutions are there?
    Thanks. - Miles

    You can use direct socket communication (custom impl) or URLs to do
    web-service style integration.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Miles Krivoshia" <[email protected]> wrote in message
    news:[email protected]..
    I have a session ejb running in wl 5.1 that must act as a client of awl6.1
    ejb (wl 6.1 running on another host). Since the RMI layer is incompatible
    between 5.1 and 6.1 I must jump through some hoops to get this to work.I've
    considered packaging the wl6.1 classes together with the 6.1 clientclasses
    in a separate jar, along with a helper class to use a separate classloader
    to load classes from that jar (in the hopes of keeping the common rmi
    classes in a separate namespace). Does this sound like the best approach?
    Has anyone else faced this problem? What other solutions are there?
    Thanks. - Miles

  • Setting up Load Balancing / Clustering in BIP installation

    Hi,
    We're upgrading Siebel 7.8 to 8.1.1.5. As part of this process, we'll be replacing the two clustered Actuate Servers with two BI Publisher installations.
    We need BIP to behave like for like compared to Actuate (clustered / load balanced) but I cannot any detailed instructions on implementing Load Balancing / Clustering of BIP anywhere.
    We use a Loadbalancer.org appliance to balance the Siebel URL - my plan is to use this to support load balancing of the Web Services across the two BIP instances. However, I also need the two BIP installations to share the same repository.
    I've come across an Oracle White Paper (http://www.oracle.com/technetwork/middleware/bi-publisher/bip-cluster-deployment-366859.pdf) that states:
    The repository is shared among different servers in the cluster
    However, looking at the installation guide for Oracle BIP 10.1.x.x.x, there are no details on how to achieve this.
    Anyone know where to find documentation explaining, in detail, how to load balance multiple BIP servers to achieve the same level of high availability as we had with Actuate?
    Thanks in advance!
    mroshaw

    http://e-docs.bea.com/wls/docs60/////adminguide/apache.html
              "Kit Chan" <[email protected]> wrote in message news:[email protected]..
              > After I have gone through the documentation of Administering the server and
              > Clustering, I still do not know where should I start with and what settings
              > I need to add. Is there any detailed document concerning setting up a
              > cluster with Apache plug-in and two WL6.0 servers?
              >
              > Can anyone please help?
              >
              > Thanks a lot.
              >
              > Kit Chan
              > [email protected]
              >
              >
              >
              

  • Multiple clusters definition with the same httpd.conf

    I want to define two different weblogic clusters for the same virtual host based on the URL. I've tried this
    <Location /tocluster1 >
    WebLogicCluster machine1:8090,machine2:8090
    SetHandler weblogic-handler
    </Location >
    <Location /tocluster2 >
    WebLogicCluster machine3:9090, machine4:9090
    SetHandler weblogic-handler
    </Location >
    It doesn't work : requests are mixed up between both clusters.
    Is it possible to achieve using WL6.1SP5 plugin and apache 2.0.47 ?

    I had a similar issue and got it fixed after applying the latest version of the
    proxy plugin. If you already got the latest plugin then it is fine. Otherwise
    let me know, I can send it over to you. You may also open a case with BEA and
    get it.
    Thanks,
    Jiten
    "lauren" <[email protected]> wrote:
    >
    I am having the same issue with Weblogic 8.1 plugin on Apache 2.0.46.
    So it seems
    like the issue has been fixed yet. Do I have to use only one WeblogicCluster
    for each Apache Virtual host? Does anyone have a better solution? Thanks
    Lauren
    "Bjørn Bjerkeli" <[email protected]> wrote:
    WebLogic 5.1 supports only one config per VirtualHost, as specifiedin
    docs, and
    from 6.1 and up multiple configs are supported, also specified in docs.
    I would strongly recommend to use the 6.1-approach when proxying tomultiple
    clusters,
    even if the "old" style works too. I have done some testing that yielded
    high
    error ratios, apache bridge failures and READ_TIMEOUTS when using mod_proxy
    as
    a intermediate to proxy from one VirtualHost to antother containingthe
    cluster-definition
    /Bjørn Bjerkeli, Zenior AS
    "Yakov Broido" <[email protected]> wrote:
    Hey,
    I had the same problem and it didnt work.
    eventually I had to use multiple VirtualHosts.
    It seems that its a bug and the WebLogicCluster directive(and some
    others)
    are global for each vhost.
    This bug is going to be fixed in next ServicePack of WLS 7.0 but Idonno
    what about 6.1
    "Philippe Peeters" <[email protected]> wrote in message
    news:40165b9b$[email protected]..
    I want to define two different weblogic clusters for the same virtualhost
    based on the URL. I've tried this
    <Location /tocluster1 >
    WebLogicCluster machine1:8090,machine2:8090
    SetHandler weblogic-handler
    </Location >
    <Location /tocluster2 >
    WebLogicCluster machine3:9090, machine4:9090
    SetHandler weblogic-handler
    </Location >
    It doesn't work : requests are mixed up between both clusters.
    Is it possible to achieve using WL6.1SP5 plugin and apache 2.0.47

  • Wl6 Admin - Cluster - Cluster Address - What does this tab represent?

    In the WL6.0Sp1 Admin Console, at cluster creation time, a Cluster address
              is required. What does this cluster address represent?
              Heres what WL6 documentation says
              (http://edocs.beasys.com/wls/docs60/ConsoleHelp/cluster.html#create_cluster)
              Cluster Address - This attribute returns the address to be used by clients
              to connect to this cluster. This address may be either a DNS host name that
              maps to multiple IP addresses or a comma separated list of single address
              host names or IP addresses.
              We created a cluster of 4 WL6 servers, 3 on Multi-homed Win2K with static
              ip's and one on a single-homed Win2k m/c. Our Enterprise appplication (ear)
              is targetted at the cluster only, not individual m/c's in the cluster.
              Initially, the Cluster Address was specified as all the ip addresses. Then
              we specified only one ip address in the Cluster Address tab. Yet, in both
              the above cases, we were able to access our application by hitting any of
              the 4 ip's in the cluster. The clustering algorithm was set to
              "Round-Robin".
              And in both cases (single ip address and 4 ip addresses in Cluster address
              tab), the cluster monitor on the Admin console was showing all four WL6
              server instances participating in the cluster! We also tried a DNS name that
              mapped to the Ip addresses and again all 4 instances were shown to be
              participating in the cluster.
              I have two questions
              1) What exactly is the significance of the Cluster Address tab?
              2) How do we know which WL6 server instance is being accessed at which
              client request. With round robin, will each of the 4 WL6 instances be
              accessed once every 4 requests? How do we monitor/verify this, either via
              console or via log files?
              Thanks in advance for help/clarifications.
              Regards,
              Nitin
              

    thank you thank you for taking an interest. this is so frustrating.
    i only have apple keyboard, mighty mouse, and 20 inch cinema display connected. this morning took out memory and tried to boot up with individual pairs in the first bank. first the (2)256, the (2) 1g, and then the other (2) 1g modules. everytime I get the weird fuzzy wheel under the logo after a while, black screen flashes, then grey apple logo fuzzy screen then black forever.
    I ran tiger updates this morn. still will only boot to safe mode. then tried to run leopard disk to install it
    will not boot from leopard disk.
    tried safe boot, then doulble click install leopard, restart, then the saga repeats with the pixely red square around the wheel.
    these are fresh drives with only what came on instll disk loaded.
    thanks again for taking an interest.
    i love this system(well at least i did). I want to install leopard on my powerbook too but am terrified to do so right now since it is working and I have work to do. Can't afford to have no computer to do my work on...self employment is great?!
    This is making me crazy. I anxiously await your words of wisdom.

  • Clustering License

              I have two quesions:
              1) How do I know if my WebLogic6.0 license is a
              license for custering?
              2) Assume that I have three machines running WL6.0 cluster,
              one of them is the Admin server and the other two are
              Managed servers, how many clustering licenses do I
              need? Just one on the machine which runs the Admin server?
              Thanks a lot.
              

    [att1.html]
              

  • Load Balancing / Clustering Quick Start

    After I have gone through the documentation of Administering the server and
              Clustering, I still do not know where should I start with and what settings
              I need to add. Is there any detailed document concerning setting up a
              cluster with Apache plug-in and two WL6.0 servers?
              Can anyone please help?
              Thanks a lot.
              Kit Chan
              [email protected]
              

    http://e-docs.bea.com/wls/docs60/////adminguide/apache.html
              "Kit Chan" <[email protected]> wrote in message news:[email protected]..
              > After I have gone through the documentation of Administering the server and
              > Clustering, I still do not know where should I start with and what settings
              > I need to add. Is there any detailed document concerning setting up a
              > cluster with Apache plug-in and two WL6.0 servers?
              >
              > Can anyone please help?
              >
              > Thanks a lot.
              >
              > Kit Chan
              > [email protected]
              >
              >
              >
              

  • Clustering on WL5.1

    Hi All
    I have one configuration problem on CLuster ,I just want to know where I have define IP Addresses for cluster Servers eg., serevr11, server12 and serevr13. I have doubt whether it is going to be in the cluster folder weblogic.property file or per server basis folder weblogic.property file.
    I hope this is the correct property which is going to be set...
    weblogic.cluster.multicastAddress=222.0.0.11
    weblogic.system.binAddr=22.11.15.11
    weblogic.system.binAddr=22.11.15.12
    weblogic.system.binAddr=22.11.15.13
    If I am wrong, please let me know.
    If any one did clustering on 5.1 please help.
    I did clustering on WL6, its damm easy on WL6.
    Thanks

    First look at the Weblogic documentation. You can find this on: http://www.weblogic.com/docs51/cluster/index.html
    If you don't get an answer there, you might try asking a question in BEA's newsgroups: http://newsgroups.bea.com
    regards
    Jesper

  • Weblogic6.0 clustering problem

    Hi All
              I need to test clustering features in weblogic6.0 using
              WindowsNT machine.I downloaded the wl6.0 and installed on my NT
              machine.I added one sever like MSever in the ADMIN console.I started
              StartManagedWebLogic with severname and admin host address.I am gettin
              these errors.can any body help how to solve this problem.I appreciate
              early reply.
              D:\weblogic6\wlserver6.0\config\NAMDomain>startManagedWebLogic MServer
              http://137.168.67.164:7001
              D:\weblogic6\wlserver6.0>set
              PATH=.\bin;D:\weblogic6\wlserver6.0\bin;D:\weblogic6\jdk130\bin;C:\Program
              Files\Oracle\jre\1.1.7\bin;D:\jdk1.2.2\bin;D:\j2sdkee1.2.2\bin;D:\weblogic\bin;D:\OraHome1\bin;C:\WINNT\sys
              D:\weblogic6\wlserver6.0>set
              CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              D:\weblogic6\wlserver6.0>"D:\weblogic6\jdk130\bin\java" -hotspot -ms64m
              -mx64m -classpath .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              -Dweblogic.Domain=NAMDomain -Dweblogic.Name=MServer
              "-Dbea.home=D:\weblogic6"
              Starting WebLogic Server ....
              <Feb 20, 2001 11:21:47 AM EST> <Notice> <Management> <Loading
              configuration file .\config\NAMDomain\config.xml ...>
              <Feb 20, 2001 11:21:50 AM EST> <Info> <Logging> <Only log messages of
              severity "Error" or worse will be displayed in this window. This can be
              changed at Admin Console> NAMDomain> Servers> MServer> Logging> Debug
              Starting Cluster Service ....
              <Feb 20, 2001 11:21:58 AM EST> <Notice> <WebLogicServer> <WebLogic
              Server started>
              <Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <Unable to
              create a server socket for: FA2880/137.168.67.112, port: 7001.
              java.net.BindException: Address in use: JVM_Bind Perhaps the address
              FA2880/1
              <Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <The
              WebLogic Server is no longer listening for connections. You should
              probably restart it.>
              <Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <Server shutdown
              has been requested by system>
              <Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <The shutdown
              sequence has been initiated.>
              <Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Disconnecting from
              cluster MCluster>
              <Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Multicast socket
              receive error: java.net.SocketException: socket closed
              java.net.SocketException: socket closed
              at java.net.PlainDatagramSocketImpl.receive(Native Method)
              at java.net.DatagramSocket.receive(DatagramSocket.java:392)
              at
              weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:128)
              at
              weblogic.cluster.MulticastManager.execute(MulticastManager.java:290)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Thanks in advance
              Nagesh
              

    Hi All
              I need to test clustering features in weblogic6.0 using
              WindowsNT machine.I downloaded the wl6.0 and installed on my NT
              machine.I added one sever like MSever in the ADMIN console.I started
              StartManagedWebLogic with severname and admin host address.I am gettin
              these errors.can any body help how to solve this problem.I appreciate
              early reply.
              D:\weblogic6\wlserver6.0\config\NAMDomain>startManagedWebLogic MServer
              http://137.168.67.164:7001
              D:\weblogic6\wlserver6.0>set
              PATH=.\bin;D:\weblogic6\wlserver6.0\bin;D:\weblogic6\jdk130\bin;C:\Program
              Files\Oracle\jre\1.1.7\bin;D:\jdk1.2.2\bin;D:\j2sdkee1.2.2\bin;D:\weblogic\bin;D:\OraHome1\bin;C:\WINNT\sys
              D:\weblogic6\wlserver6.0>set
              CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              D:\weblogic6\wlserver6.0>"D:\weblogic6\jdk130\bin\java" -hotspot -ms64m
              -mx64m -classpath .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              -Dweblogic.Domain=NAMDomain -Dweblogic.Name=MServer
              "-Dbea.home=D:\weblogic6"
              Starting WebLogic Server ....
              <Feb 20, 2001 11:21:47 AM EST> <Notice> <Management> <Loading
              configuration file .\config\NAMDomain\config.xml ...>
              <Feb 20, 2001 11:21:50 AM EST> <Info> <Logging> <Only log messages of
              severity "Error" or worse will be displayed in this window. This can be
              changed at Admin Console> NAMDomain> Servers> MServer> Logging> Debug
              Starting Cluster Service ....
              <Feb 20, 2001 11:21:58 AM EST> <Notice> <WebLogicServer> <WebLogic
              Server started>
              <Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <Unable to
              create a server socket for: FA2880/137.168.67.112, port: 7001.
              java.net.BindException: Address in use: JVM_Bind Perhaps the address
              FA2880/1
              <Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <The
              WebLogic Server is no longer listening for connections. You should
              probably restart it.>
              <Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <Server shutdown
              has been requested by system>
              <Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <The shutdown
              sequence has been initiated.>
              <Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Disconnecting from
              cluster MCluster>
              <Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Multicast socket
              receive error: java.net.SocketException: socket closed
              java.net.SocketException: socket closed
              at java.net.PlainDatagramSocketImpl.receive(Native Method)
              at java.net.DatagramSocket.receive(DatagramSocket.java:392)
              at
              weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:128)
              at
              weblogic.cluster.MulticastManager.execute(MulticastManager.java:290)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Thanks in advance
              Nagesh
              

  • Weblog 6 Clustering basic question

    I am trying to setup Weblogic ver 6.0 Clustering on my Windows NT machine.
              From the weblogic console i created a Cluster, which has the IP address of
              my machine, and given it some name MyCluster.
              I have not given any Multicast IP address to it.
              On the left hand pane : For my servers under Servers/exampleServer
              On the right hand pane :
              I go to Configuration/Cluster window and choose MyCluster for the cluster
              field for my Server exampleServer.
              And click Apply.
              This results in error messages in my Weblogic command line window with lots
              of NullPointerExceptions etc...
              Have i missed any step here ?
              Can any one please give me a step by step guide to creating a Cluster, and
              then adding server (instances ?) to it.
              Do i need more than one IP address (i guess...) ?
              

              A cluster needs at least TWO IPs (2 IPs in 1 PC or 2 PCs).
              Your IP for cluster should be like 1.1.1.1,1.1.1.2 or cluster.domain
              with two IPs assigned to it.
              That should be why you got NullPoint for the missing 2nd IP.
              You might follow my attached ReadMe.doc and modify my sample config.xml
              for both machines/locations (use same config.xml on the two), modify
              my startExamplesCluster.cmd (for master), startExamplesSlave.cmd
              (for slave) and setExamplesEnv.cmd (for both) to fit yours, and
              try.
              config.xml has all the result you can make in console.
              Cluster feature in WL6 is far from perfect, don't guess the ideal
              possibilities all the time.
              Good luck!
              Steven
              "JSB" <[email protected]> wrote:
              >I am trying to setup Weblogic ver 6.0 Clustering on my
              >Windows NT machine.
              >
              >From the weblogic console i created a Cluster, which has
              >the IP address of
              >my machine, and given it some name MyCluster.
              >I have not given any Multicast IP address to it.
              >
              >On the left hand pane : For my servers under Servers/exampleServer
              >On the right hand pane :
              >I go to Configuration/Cluster window and choose MyCluster
              >for the cluster
              >field for my Server exampleServer.
              >And click Apply.
              >
              >This results in error messages in my Weblogic command
              >line window with lots
              >of NullPointerExceptions etc...
              >
              >Have i missed any step here ?
              >Can any one please give me a step by step guide to creating
              >a Cluster, and
              >then adding server (instances ?) to it.
              >Do i need more than one IP address (i guess...) ?
              >
              >
              >
              [startExamplesSlave.cmd]
              

Maybe you are looking for

  • [New_Feature_Requirement] [iOS 8] Detecting permissions for camera access

    Here is the feature request: Feature#3837401 - [New_Feature_Requirement] [iOS 8] Detecting permissions for camera access Problem: The camera privacy control is now required by iOS 8 for all regions. With iOS 8 any application that use camera encounte

  • JDeveloper workshops in Australia and New Zealand 2008

    Hi gang, a little blatant self promotion for a JDeveloper workshop I'm running in conjunction with the Australian Oracle User Group and sponsored by OTN in 2008. "Scared of JDeveloper because you don't know Java, but worried you'll miss the boat in d

  • Viewing the way of a message through integration process

    Hey, I would like to check the lifecycle of a message through an integration process (IP). Therefore I took the ID of a message that triggers the IP.  Our IP have several sending steps and I would like to see the messages that will be send. In sxmb_m

  • Java.io.FileNotFoundException: URLConnection Destination

    Hi, I am using ADS for downloading Performance Management documents. So far I am successfully running interactive forms in my DEV and QUA system. However, it does not work in PROD. Here is the error I get: <b>Caused by: java.io.FileNotFoundException:

  • How much bytes are my data - TCP-String

    Hi, I have a 40960 elements long 1D array of SGL data type. I flatten it and I send it through TCP. The receiver gets it but certainly slower than it is sent. It makes me think that I read in much more bytes than needed. For the TCP read I use the CR