Cluster Address

Hi,
          I have set up my cluster just on single machine with one admin server listening on 127.0.0.1:7001 and two managed servers listening on 8001 and 8011 (on same local host).
          Also I have configured a JMS queue on one of the managed server. I am trying to browse this queue (one of the sample program I copied from weblogic example directory) to the JMS server using a COMMAND LINE client. When I run my program like
          java examples.jms.queue.QueueBrowse t3://127.0.0.1:8001
          it works fine and it also works for port 8011.
          But I am not sure how can I give a cluster address rather than individual managed server address. I tried 127.0.0.1:7001 but if fails to do jndi look up of queue. (I guess it is because Queues are registered to the managed server not admin server).
          Any help would be appreciated
          Sushil
          BTW I have posted this on clustering newsgroup but may be this newsgroup is more appropriate for this question.

Typically you will need to map a DNS name to the IP addresses of the servers in your cluster. This DNS name should match the ClusterAddress that you set in your cluster configuration.
For development purposes, you can also use the following URL: t3://127.0.0.1:8001,127.0.0.1:8011

Similar Messages

Getting initial context using a cluster address

I am having trouble getting initial context using a cluster address. My cluster
has two WL 8.1 servers at localhost:8001 and localhost:9001. I set the hashtable
to get the initial context as follows:
env.put(InitialContext.PROVIDER_URL, "t3://localhost:8001,t3://localhost:9001");
This gives me the following exception:
Could not create JNDI InitialContext: javax.naming.ConfigurationException
[Root exception is java.net.MalformedURLException: port expected: t3://cammnbhati:8001,t3://cammnbhati:9001]
Any idea whey this is not working? If I set only one of the addresses then there
is no error. For example, the following works just fine:
env.put(InitialContext.PROVIDER_URL, "t3://localhost:8001");
Thanks.

try t3://localhost:8001,localhost:9001 as url
hth
sree
"Naresh Bhatia" <[email protected]> wrote in message
news:4009cfdf$[email protected]..
>
I am having trouble getting initial context using a cluster address. Mycluster
has two WL 8.1 servers at localhost:8001 and localhost:9001. I set thehashtable
to get the initial context as follows:
env.put(InitialContext.PROVIDER_URL,"t3://localhost:8001,t3://localhost:9001");
>
This gives me the following exception:
Could not create JNDI InitialContext:javax.naming.ConfigurationException
[Root exception is java.net.MalformedURLException: port expected:
t3://cammnbhati:8001,t3://cammnbhati:9001
Any idea whey this is not working? If I set only one of the addresses thenthere
is no error. For example, the following works just fine:
env.put(InitialContext.PROVIDER_URL, "t3://localhost:8001");
Thanks.

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.

Exception: Cluster address must be set when clustering is enabled

Hi,
I've created a simple web service and deployed to a cluster. When i invoke the WSDL url (http://localhost/webservice/MyService?WSDL) through the browser i get the enclosed exception (listed at the bottom)
I can easily solve this issue by explicitly stating a cluster address witihin the admin console ( Environment->Clusters->Cluster Address:), however the documentation states that i do not need to do this. ( http://edocs.bea.com/wls/docs100/webserv/setenv.html#wp220521 )
Can someone clarify that indeed I need to explicitly declare a Cluster Address when deploying and invoking web services within a clustered environment.
Thanks
#-Exception as displayed within the browser--
Error 500--Internal Server Error
java.lang.IllegalArgumentException: Cluster address must be set when clustering is enabled.
     at weblogic.wsee.server.ServerUtil.getClusterAddress(ServerUtil.java:439)
     at weblogic.wsee.server.ServerUtil.getHTTPServerURL(ServerUtil.java:130)
     at weblogic.wsee.server.servlet.WsdlRequestProcessor.getAddressInfo(WsdlRequestProcessor.java:161)
     at weblogic.wsee.server.servlet.WsdlRequestProcessor.process(WsdlRequestProcessor.java:76)
     at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:257)
     at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

Hi,
You will have to specify the address for the cluster to get this work. This was done because if cluster address is not specified, there were other issues that popped up.
Its works as designed.
Regards.

How to define cluster address

          My network administrator doesn't undestand how to configure dns cluster address
          that map two addresses (the ones of servers in the cluster).
          Can anyone help?
          Thank you


Lucia Giraldo wrote:
          > My network administrator doesn't undestand how to configure dns cluster address
          > that map two addresses (the ones of servers in the cluster).
          > Can anyone help?
          > Thank you
          http://www.weblogic.com/docs50/cluster/setup.html
          http://www.oreilly.com/catalog/dns3/

How to use a Cluster ADdress?

          Hi!
          I created a cluster with two servers. The cluster service starts up successful.
          Everything is working. The only problem that i have is to configure a working
          cluster address. I want only one address to be visible for the clients. Not the
          all addresses of each clustermember. How can i do that. I added a address into
          the Cluster Address field but i didn´t work. Can anyone help me? Thanks
          Chris


Per the following link:
          http://e-docs.bea.com/wls/docs61/cluster/setup.html
          BEA recommends that your cluster address be a DNS entry with multiple
          IPs. Your network administrator should be able to provide one for you.
          Sincerely,
          Charlie Therit
          Developer Relations Engineer
          BEA Support
          Christian Graf wrote:
          >Hi!
          >I created a cluster with two servers. The cluster service starts up successful.
          >Everything is working. The only problem that i have is to configure a working
          >cluster address. I want only one address to be visible for the clients. Not the
          >all addresses of each clustermember. How can i do that. I added a address into
          >the Cluster Address field but i didn´t work. Can anyone help me? Thanks
          >Chris
          >
          >

WebLogic Horizontal Cluster - cluster address question

Hi,
I have a question regarding horizontal clusters.
I setup a cluster following the instructions here: http://weblogicserveradministration.blogspot.com/2010/10/horizontal-clustering.html
It appears to be successful - I can see that everything is in a running state, etc.
Then I deployed an application to the cluster. The application is in an Active state.
I'm confused as to what the cluster address should be and also how to access my application.
Right now, I have this setting for the cluster address
wls1:7020,wls2:7020
Is this correct? If so, how would I access my application?
For example, would I use http://wls1:7020/app or would I use http://wls2:7020/app, or does it matter?
I'm not sure if I'm maybe missing some other important step..
Thanks much,
Nora

Hi Nora
Actually what you need to do is, to create a new server (stand alone) which would act as a proxy srver, and keep this in front of your cluster.. then you would use the port for this proxy server to use your application. and also there would just a proxy application which would be deployed on this proxy server for load balancing. then your request can be directed to either first or the other managed server.
Keep posting :)

Failed to join cluster - Address already in use

Hi there,
          I'm trying to set up a cluster with WLS 7.0 on Linux (kernel 2.4.20). Apparently, the OS is configured correctly: the kernel is compiled with multicast support and multicast routes have been appropriately defined.
          The admin server starts correctly, and managed servers running on other OSs successfully join the cluster. However, when a I try to run a managed server on this linux, I get the following error:
          <Apr 29, 2003 12:27:52 AM CEST> <Error> <Cluster> <000116> <Failed to join cluster testcluster at address 237.0.0.1 due to : java.net.BindException: Address already in use
          java.net.BindException: Address already in use
          at java.net.PlainDatagramSocketImpl.bind(Native Method)
          at java.net.MulticastSocket.create(MulticastSocket.java:123)
          at java.net.DatagramSocket.<init>(DatagramSocket.java:135)
          at java.net.DatagramSocket.<init>(DatagramSocket.java:107)
          at java.net.MulticastSocket.<init>(MulticastSocket.java:99)
          at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:87)
          at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:110)
          at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:140)
          at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:51)
          at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:773)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
          at weblogic.Server.main(Server.java:32)
          >
          I have tried to change the multicast address but the error persists.
          Am I missing something? Any help would be muchly appreciated.


have you checked to see what is running before you start your oracle app server on your ports? you can use netstat for one

DNS cluster address additions for internal communication

Hi Guys,
          My understanding is that WL cache's DNS address of the cluster, and removes
          'dead' cluster members.
          I imagine that this means that if I use:
          ic = new InitialContext("t3://myclusteraddress:7003");
          and I have myclusteraddress mapped to 10.0.0.1 and 10.0.0.2 that all will be
          well with the world?
          And if 10.0.0.1 goes down, all will still be well?
          What happens when I dynamically add a server to such a cluster? As the
          DNS doesn't get read again, cos
          it's cached, what happens? Is there some magic that goes on behind my back
          perhaps involving multicast of
          new servers that updates the "DNS cache" so that the new server is included?
          For external clients, I understand the problem, and the need for a hardware
          load balancer or the like that
          can detect failure and not return dead DNS servers. Qustion: Can I emulate
          this using a piece of software?
          Regards,
          Q


As requested:
// Include keys file
include "/etc/rndc.key";
// Declares control channels to be used by the rndc utility.
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.
// Default controls
controls {
inet 127.0.0.1 port 54 allow {any;} keys {
"rndc-key";
options {
directory "/var/named";
recursion false;
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
// query-source address * port 53;
// # Adding this...
forwarders {
151.164.8.201;
151.164.1.8;
forward first;
// # to here..
// a caching only nameserver config
zone "." IN {
type hint;
file "named.ca";
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
zone "" IN {
file ".bak";
masters {
type slave;
zone "kccompany.org" in {
file "kccompany.org.zone";
type master;
zone "200.168.192.in-addr.arpa" IN {
file "db.192.168.200";
type master;
zone "xxx.207.64.in-addr.arpa" IN {
file "db.64.207.xxx";
type master;
logging {
category default {
defaultlog;
channel defaultlog {
file "/Library/Logs/named.log";
severity info;
print-time yes;
};

Sql developer won't connect with SQL server database on cluster

Hello,
I have a microsoft SQL server database on a windows cluster. Name for this cluster is like XXX/YYY
When I try to connect to this database with SQL developer, I get a failure, mentioning:
"Status : Failure -Cannot connect to Miscrosoft SQL Server on XXX/YYY"
As far as I know, I have installed the correct jtds driver (version 1.2.5), since I can connect to sql server databases on single server hosts.
Does anyone know how to connect to databases on windows clusters?
Edited by: Ingmar on Jan 16, 2012 4:08 PM
Edited by: Ingmar on Jan 16, 2012 4:22 PM

Hi Ingmar,
Try this is in the port box
1433/dbname;instance=YYY
dbname can be omitted
-Turloch
SQL Developer team
1/Giving an instance name in SQLDeveloper connection to SQL Server (from August 2011)
MS SQL Server Connection
The correct syntax to deal with this is in the port box
1433/dbname;instance=instance
dbname can be omitted
2/cluster configuration (uses instance name)
http://stackoverflow.com/questions/1160024/jdbc-connect-string-for-sql-server-cluster
where vvv\iii is the cluster address: jdbc address is:
"jdbc:sqlserver://vvv;instanceName=iii"
3/jtds url details available in
http://jtds.sourceforge.net/faq.html

In-memory replication of http session is not working in BEA7 cluster

          Hi everyone,
          I have 3 managed servers in Bea7.0 SP4 in a cluster. The client requests are sent
          through apache web server. I have given cluster address as URL in httpd.conf of
          apache server which sends the client requests for dynamic pages such as JSPs and
          servlets to the weblogic cluster.
          Load balancing is working fine. I ensured this from the log files of all the 3
          servers. All the 3 servers are getting different client requests and thus load
          balancing is working.
          Now, I wanted to achieve Fail-over. I do not think that i should use proxy plug-in
          for this. I feel the cluster itself will handle fail-over provided i make the
          http session as memory replicated.
          I updated the weblogic.xml with the following entry :
          <session-descriptor>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          I guess this is sufficient to make the http session as cluster aware.
          But when I shutdown server1, the user connected to server1 will be kicked out
          of the session and come to login page through server2 or server3 which are running
          fine.
          Could anyone help me to achieve http session as cluster aware. Does it indicate
          that I have to go for WLS proxy – HttpClusterServlet to achieve fail over for
          http session ?
          BTW, for your info, i am using setAttribute() and getAttribute() while manipulating
          the session.
          thanks in advance.


          Hi Ryan,
          Thanks for ur valuable input.
          I can see failover working.
          But, I can not continue with the same session in my application.
          I printed session Ids before and after failover, I found both are different.
          I guess session replication is a responsibility of weblogic/apache plugin.
          If not please let me know which all settings I should do to make failover working?
          Thanks again.
          Plad
          "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >Plad,
          >
          >Are you trying to gracefully shut down the server? If you are then the
          >problem that you say you can't identify is simply the server's default
          >behavior which is to wait for all non-replicated sessions to be dropped
          >or
          >timed out before killing the process. Try forcing the shutdown: kill
          >-9 the
          >PID or CTRL-C if you started the server from the command line. You can
          >also
          >check the ``Ignore Sessions During Shutdown" checkbox under the server's
          >control tab in the admin console, this should allow you to shut down
          >gracefully without waiting for session timeout. BTW your sequence is
          >off
          >in #5 below, the replication doesn't occur upon failure, the replication
          >has
          >already happened once you created the session object on the first server,
          >I
          >think maybe you're confusing replication with failover.
          >
          >~RU
          >
          >"Plad" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >> I have 2 managed servers in a cluster.
          >>
          >> 1. I have got a DNS name configured which maps to these 2 managed server's
          >IP
          >> addresses.
          >> 2. I can browse my site using this DNS name.
          >> In HTTPD.conf I have :
          >>
          >> ServerName dev.a.b.net
          >>
          >> <IfModule mod_weblogic.c>
          >> WebLogicCluster 10.1.38.232:7023,10.1.34.51:7023
          >> MatchExpression *.*
          >> </IfModule>
          >>
          >> LoadModule weblogic_module modules/mod_wl_20.so
          >>
          >> 3. I have adeded session descriptor in weblogic.xml , also enabled
          >proxy
          >plugin
          >> in weblogic console.
          >>
          >> 4. I tested accessing my application using DNS url after shutting down
          >alternatively
          >> each manaed server. I can access application.
          >>
          >> 5. Now, problem comes when I access a managed server1 , keeping server2
          >down.
          >> I am able to access my application.
          >> Now, I start the server2.
          >> (Here I am supposing that replication should occur)
          >> Then I am shutting down server1.
          >> But, this time the server log shows me following:
          >>
          >>
          >> 9:58:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 2 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >> 10:00:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 4 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >>
          >> I am unable to make out where the problem is?
          >> Can it be a problem of Liecense? Is there any specialcluster liecense
          >for
          >weblogic8?
          >>
          >> Hoping to get replies.
          >> Thanx.
          >> Plad
          >>
          >> "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >> >See my reply to your first post, but I've also added a few comments
          >here.
          >> >
          >> >"jyothi" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> I guess someone from bea support team only can answer both your
          >question
          >> >and mine.
          >> >> As per my knowledge, we do not need to do any setup at Apache
          >side
          >> >regarding
          >> >> cluster other than mentioning cluster address as URL while
          >contacting
          >> >WLS
          >> >> from apache.
          >> >>
          >> >> I hope someone from Bea, will help us. I do not think that we
          >> >go for
          >> >WLS
          >> >> proxy plug-in using HttpClusterServlet for making session replication.
          >> > I
          >> >strongly
          >> >> feel that the cluster itself be able to manage the fail-over of
          >> >http
          >> >sessions
          >> >> provided we put the entry "PersistentStoreType" in weblogic.xml
          >> >regarding
          >> >> the session replication.
          >> >>
          >> >
          >> >The cluster does handle the management of Sessions. The clustered
          >> >applications still create the Session objects and the cluster manages
          >> >them
          >> >as per your deployment descriptor settings (replicated, JDBC, File)
          >however
          >> >the proxy has to be aware of which server the client has an affinity
          >> >for
          >> >(only with replicated sessions) and it does that by reading a cookie
          >> >passed
          >> >back from the server that handled the initial request and created
          >the
          >> >primary session object. The proxy has a list of both the primary
          >and
          >> >secondary server locations from this cookie that it can use to failover
          >> >the
          >> >request if the primary server fails. Clusters _DO NOT_ failover nor
          >> >do they
          >> >load balance, that's the job of your proxy, whether you're using the
          >> >HTTPClusterServlet, WLS Plug-in or a more sophisticated hardware load
          >> >balancer like Big IPs F5
          >> >
          >> >> jyothi
          >> >>
          >> >
          >> >~RU
          >> >
          >> >
          >>
          >
          >

How to configure multiple cluster on multiple jvm

Hello all,
I have 15 caches and 6 servers with 8 processors each.
I wish to split the 7 Caches on 3 servers as first cluster and remainig 8 caches on 3 servers as second clsuter.
Can somebosy please provide the sample configuration.
Thanks
Vinay

Hi Gary,
clusters are separated from each other by their multicast cluster address and cluster port.
Just choose two clusteraddress-port pairs in which both the ports and the cluster addresses are different (different ports are necessary, I believe, because you want to have multiple clusters on the same machine).
You can specify the cluster address to the JVM with the Java property -Dtangosol.coherence.clusteraddress=... and you can specify the port with -Dtangosol.coherence.clusterport=....
Specify the appropriate address and port to all the JVMs according to which cluster you want the JVM to be a member of.
Alternatively you can specify an override file containing this information (you can read more about this on the wiki or in the users guide in the zip file (which is an export of the wiki).
Best regards,
Robert

Multiple Database behind the Weblogic cluster

          Hi,
          We are working on an enterprise-level EJB based application. Because the scalability and fail-over requirement of the application, we have to at least have 2 database in the backend. Ideally, the 2 database should like one for the Weblogic servers in the app server cluster that are accessing them. There are severl possible solutions:
          1. Have one database as the master data source and another database as stand-by. When the master dabase fails, we could use the Oracle hot-failover to failover to the standby database (am I right? ). The bad thing about this solution is that we are wasting a big box doing nothing, just as standby.
          2. Use a database cluster. I saw some of the discussion in the newsgroup. Basically, the database(s) in the cluster will look like one logical database for the app server cluster. Does anyone have any comments on this solution? Please provide details.
          3. We come up a solution which requires partition of the application into several logical funtion groups and partition the data as well. Even though the solution works technically, it will create a management nightmare for the server cluster.
          Anyone has experience with this? Please comment. Thanks a lot!
          Adam


          Weblogic 7 has a new concept called network channel, where there is a section talking
          about clustering over multiple NIC cards. I was confused by the cluster address in
          customized network channel (no example there). I tried to use multiple NIC cards
          for the purpose of network failover, but failed in clustering environment, although
          I succeed in single server environment.
          Kumar Allamraju <[email protected]> wrote:
          >You can set Interface address via admin console's
          >Cluster >> {Cluster Name }
          >
          >on the right hand side you will find InterfaceAddress box.
          >
          >--
          >Kumar
          >
          >zevit wrote:
          >
          >>>It's the JVM & OS who will take adv. of multiple NIC's. We don't have
          >>>anything in WLS that does this thing.
          >>>
          >>>Alternatively you can bind each WLS instance to a specific NIC card
          >>>to effeciently utilize each NIC card.
          >>>
          >>
          >> thank u kumar.. Could u please tell me how do i bind each WSL instance
          >> to a specific NIC ?
          >>
          >

Making requests to a cluster

          Hi,
          I'm a bit confused by the General tab in cluster configuration.
          It contains the following fields:-
          - Name
          - Cluster Address
          - Default Load Algorithm
          - Service Age Threshold
          I understand that hostname/IP(s) that map to one or more servers
          in the cluster goes in Cluster Address. But, if that's the case,
          what party is responsible for scheduling requests to servers
          in th cluster, using the algorithm in Default Load Algorithm? And, how does one
          connect to that party and on what port?
          If the answer is that you have to use your own policy (software
          or hardware load balancing) then what is the purpose of
          the Default Load Algorithm field in WLS 6.1?
          You already configure what servers are on the cluster, so WLS
          knows this already. So why does one have to specify the
          IPs again in Cluster Address? Seems to me, and from other
          messages in this forum, that filling out this tab doesn't have
          much benefit at all.
          Thanks in advance,
          Gary
          FT.com


The cluster address is the DNS round-robin address that clients use in their URL to
          establish
          their initial connection. The cluster address is currently only used by WL in two
          limited cases:
          EJB home handles -- These contain info that can be serialized and passed to a
          client
          which currently may not have a connection to the cluster. The client can use
          the handle to find its associated EJB.
          Entity Bean fail-over -- Allows client to automagically get back to the cluster
          if a connection to the cluster fails.
          Tom
          Gary Watson wrote:
          > Hi,
          >
          > I'm a bit confused by the General tab in cluster configuration.
          > It contains the following fields:-
          > - Name
          > - Cluster Address
          > - Default Load Algorithm
          > - Service Age Threshold
          >
          > I understand that hostname/IP(s) that map to one or more servers
          > in the cluster goes in Cluster Address. But, if that's the case,
          > what party is responsible for scheduling requests to servers
          > in th cluster, using the algorithm in Default Load Algorithm? And, how does one
          > connect to that party and on what port?
          >
          > If the answer is that you have to use your own policy (software
          > or hardware load balancing) then what is the purpose of
          > the Default Load Algorithm field in WLS 6.1?
          >
          > You already configure what servers are on the cluster, so WLS
          > knows this already. So why does one have to specify the
          > IPs again in Cluster Address? Seems to me, and from other
          > messages in this forum, that filling out this tab doesn't have
          > much benefit at all.
          >
          > Thanks in advance,
          > Gary
          > FT.com
          > ______________________________________________________________

Add IPv6 to a running failover cluster

Hi
I have a sql failover cluster running win2k8 R2 and SQL 2008 it was built around IPv4 the instance listens on IPv4 cluster IP address ( virtual IP)
I rescently got a request that there will be servers running in pure IPv6 networks and the need to be able to talk directly to the database using IPv6 that where I need to add a cluster IPv6.
The database is the backend for our backup server and it cannot be taken offline or allow a downtime of more than 30 minutes so rebuilding the cluster is out of questions
So my question how do I go by and add the IPv6 cluster address alongside the IPv4, I am not reffering to an IPv6 Resource.
Any suggestions will be very appreciated
Regards

Hello,
Please try to configure the NIC on the nodes for IPv6 and make sure the Host Record (A) has been created for IPv6 on the DNS server. I think that’s all you need.
I am sorry for the late response, I did not notice the thread on the forum.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Cluster Address

Similar Messages

Maybe you are looking for