Who takes care of load balancing work in weblogic cluster ?

Hi Folks,
How load balancing is handled internally by weblogic cluster ? Does Admin server takes care of cluster load balancing ? According to me Admin has nothing to do with load balancing in cluster . Manage server continue to run even when Admin server is down.
I am not looking for explanation about different load balancing algorithm. I am interested in who executes those algorithms in weblogic cluster and how .
Cheers
B.

Hi,
You need to configure loadbalancer and there are different ways to do this. Please go through the below thread to user Apache Loadbalancer.
problem with Apache Proxy plugin
Regards
Suresh.

Similar Messages

Load Balancing in Clustered Weblogic 12c

Hi,
Weblogic.........: 12.1.3
OS..................: Oracle Enterprise Linux 6.3
We have configured a Clustered Weblogic (2 virtual servers) successfully. Now we are searching for some good Load Balancing solutions. I've tested a ProxyServlet, but it didin't really solve the question, because this kind of load balancing only balances apps in the same server.
Is it mandatory to use a third-party solution, like an Apache Httpd Server, or Big IP? In fact, i would like to know initially for some viable solutions to provide a load balancing solution to a 2-server Weblogic 12c Solution.
Thanks in advance.

Hi,
It is not manadatory, and it is possible to load balance apps on different servers with the ProxyServlet. It's only that this will be running on a server from where the others need to be accesable.
Also, it depends on what you are using this environment for. The ProxyServlet is a good solution if you want to replicate an Enterprise environment and test the load balancing with a WebLogic cluster. However, if you want to run Production applications in this environment, then consider the above suggestions: either a WebServer or a dedicated external Load Balancer.
Regards

Question on how does load balancing work on Firewall Services Module (FWSM)

Hi everyone,
I have a question about the algorithm of load balancing on Firewall Services Module (FWSM).
I understand that the FWSM supports up to three equal cost routes on the same interface for load balancing.
Please see a lower simple figure.
outside inside
--- L3 SW --+
|
MHSRP +--- FWSM ----
|
--- L3 SW --+
I am going to configure the following default routes on FWSM point to each MHSRP VIP (192.168.13.29 and 192.168.13.30) for load balancing.
route outside_1 0.0.0.0 0.0.0.0 192.168.13.29 1
route outside_1 0.0.0.0 0.0.0.0 192.168.13.30 1　　　　　　
However I don't know how load balancing work on FWSM.
On FWSM, load balancing work based on
Per-Destination ?
Per-Source ?
Per-Packet ?
or
Other criteria ?
Your information would be greatly appreciated.
Best Regards,

Configuring "tunnel default gateway' on the concentrator allowed traffic to flow as desired through the FWSM.
FWSM is not capable of performing policy based routing, the additional static routes for the VPN load balancing caused half of the packets to be lost. As a result, it appears that the VPN concentrators will not be able to load balance.

How Load Balance works in RAC?

Hi All,
I have a 2-node 10gR2 RAC on RHEL4. One of our web based application is connecting to the RAC database. Today, while starting up the application, one of our node(node1) was down and all the connections from the app are connected to the DB using other node(node2). There were around 120 connection from application. Again, i brought back the node1 but still, the connections were on node2 and no connection on node1.
My doubt is, how the load balancing works in RAC? is there limit like after some number of connections, it will load balance to other node?
Thanks,
Praveen.

If all the connections go to node 2 cause node 1 is down, then, when node 1 comes back, those connections already established on node 2 will remain on node 2. There is no mechanism to migrate existing connections. However, over time, as more connections come in, they should go to node 1. Over time, the load should balance out. But, the only way to immediately rebalance would be to force existing connections to recycle their connection.
If one node is capable of handling the load, I wouldn't worry about it....over time, things will balance out.
-Mark

Load balance with JMS in cluster

          I would like to develop a MDB listening to a topic, which can be deployed in a
          weblogic cluster, so that whenever a message is published to that topic, one and
          only one of the MDB in a wls server of the cluster will process the message, what
          is the best way to do this?
          thanks
          Zhou


Do you desire a distributed topic that doesn't replicate
          between topic members, but replicates
          to all subscribers on a particular member?
          If so, then a distributed topic is NOT
          what you want to configure. Instead, you can do as you
          suggest: set JNDINameReplicated to false
          and put a same JNDI named topic on each server.
          Tom
          Tom Barnes wrote:
          >
          >
          > x zhou wrote:
          >
          >> Can I do the following to achive what I want:
          >
          >
          > I don't know what you want. But a message sent to a topic
          > member still gets replicated to the other topic members.
          >
          > I'm guessing what you are looking for is a
          > distributed queue, not a distributed topic. I suggest
          > you look at the distributed queue option. A message
          > sent to a distributed queue will only get processed
          > by one MDB.
          >
          >>
          >> 1) create a distributed topic having topic name "topic.distributed"
          >> that has "topic.1"
          >> and "topic.2" as its member on two wls instances in a cluster
          >>
          >> 2) write a MDB that will be deployed seperately to 2 wls instances in
          >> the cluster,
          >> with different weblogic-ejb-jar.xml file: the difference is at the line:
          >>
          >> <destination-jndi-name>topic.1</destination-jndi-name> for server 1;
          >> <destination-jndi-name>topic.2</destination-jndi-name> for server 2;
          >>
          >> 3) create the publisher using the distributed topic (of jndi name
          >> 'distribute.topic'),
          >> according the document, it should send the message to one and only one
          >> of its
          >> member, and therefore the corresponding MDB in the wls instance of the
          >> cluster
          >> which receives the message will be notified
          >>
          >> and this will give me multi-threading in the same wls instance
          >> (because of MDB)
          >> and load-balancing across the whole cluster, right?
          >>
          >> Incidently, it looks like I can make the topic member's jndi name the
          >> same, as
          >> long as I un-check the "Replicate JNDI Name In Cluster" checkbox. Why
          >> is there
          >> such a box in the first place? Isn't the topic not clusterable?
          >>
          >> thanks
          >>
          >>
          >> Tom Barnes <[email protected]> wrote:
          >>
          >>> (1) Currently, there is no way in WL to get multiple consumers to share
          >>> a topic subscription - which is essentially what you are asking for.
          >>> The JMS standard doesn't support this either. This is not to say
          >>> that it wouldn't be a useful feature - I personally think it would be.
          >>>
          >>> (2) Why not use a queue?
          >>>
          >>> Tom
          >>>
          >>> X Zhou wrote:
          >>>
          >>>
          >>>> I would like to develop a MDB listening to a topic, which can be
          >>>> deployed
          >>>
          >>>
          >>> in a
          >>>
          >>>> weblogic cluster, so that whenever a message is published to that
          >>>> topic,
          >>>
          >>>
          >>> one and
          >>>
          >>>> only one of the MDB in a wls server of the cluster will process the
          >>>
          >>>
          >>> message, what
          >>>
          >>>> is the best way to do this?
          >>>>
          >>>> thanks
          >>>>
          >>>> Zhou
          >>>
          >>>
          >>
          >

HOW WISM LOAD BALANCING WORKS ?

We currently have a campus with 4 WISM on 4 6509 .
After a reload of one of these WISM, all the AP ( AIR-AP1231 ) disappear from this WISM :
(WiSM-slot1-2) >show ap summary
Number of APs.................................... 1
Before the reload this WISM has 80 AP .
The other 79 AP are now registered with another WISM .
Is this normal or ( load balancing ) or what ?
Any help is apreciated

You have to check the primary/secondary/tertiary settings on the WLC, but for each access point. Go to the Wireless tab and click on an access point for this setting.
AP Fallback mode is on the WLC under the Controller tab. It forces an access point to join its primary controller if possible. If it's disabled, the access point will be happy to stay on a non-primary controller until it reboots. If it's enabled, then as soon as its primary becomes available (either because it comes up or because you specify a new primary), it will join that controller.
AP Fallback is convenient for load-balancing, but it can cause significant downtime if a controller goes down and comes back up immediately. All your APs will fail over to another controller at the initial drop, but they'll all switch back over once the original controller comes back. Each time will cause clients to drop. If a controller starts flapping for any reason, your wireless network will be seriously disrupted. Of course, if you leave it disabled and a controller goes down, all access points will hop over to their secondary controller and never go back. This isn't so bad, though, because you can just manually set it for AP fallback at a convenient time, let them all switch back, and then disable fallback again.
If you do not active AP fallback mode, be sure to reset each AP after you give it a primary/secondary/tertiary controller. Otherwise it will sit tight on the current controller.
Also, make sure that the Master Controller mode is disabled. This forces all access points to join it if you have no primary controller listed. It's under the Controller tab, under Advanced.

Apache plug-in won't load balance requests evenly on cluster

I can't seem to get the Apache plug-in to actually do round-robin load balancing
of HTTP
requests. It does random-robin, as I like to call it, since the plug-in will usually
hit all the
servers in the cluster but in a random fashion.
I've got three managed servers:
192.168.1.5:8001 (WL6 on Linux) 192.168.1.2:8001 (WL6 on Linux) 192.168.1.7:8001
(WL6 on Linux)
Admin server on 192.168.1.7:7000 (WL6 on W2k)
My Apache server is 1.3.9 (RedHat SSL) on 192.168.1.52.
The log file for each servers has something like this:
####<Apr 19, 2001 1:18:54 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
<main> <system> <> <000102> <Joined cluster cluster1 at address 225.0.0.5 on port
8001>
####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
<ExecuteThread: '9' for queue: 'default'> <> <> <000127> <Adding
3773576126129840579S:192.168.1.2:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
to the cluster> ####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster> <neptune>
<cluster1server1> <ExecuteThread: '11' for queue: 'default'> <> <> <000127> <Adding
-6393447100509727955S:192.168.1.5:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
to the cluster>
So I believe I have correctly created a cluster, although I did not bother to
assign
replication groups for HTTP session replication (yet).
The Apache debug output indicates it knows about all three servers and I can see
it
doing the "random-robin" load balancing. Here is the output:
Thu Apr 19 00:20:53 2001 Initializing lastIndex=2 for a list of length=3 Thu Apr
19
00:20:53 2001 Init Srvr# [1] = [192.168.1.2:8001] load=1077584792 isGood=1077590272
numSk ip=134940256 Thu Apr 19 00:20:53 2001 Init Srvr# [2] = [192.168.1.5:8001]
load=1077584792 isGood=1077590272 numSk ip=134940256 Thu Apr 19 00:20:53 2001
Init Srvr# [3] = [192.168.1.7:8001] load=1077584792 isGood=1077590272 numSk
ip=134940256 Thu Apr 19 00:20:53 2001 INFO: SSL is not configured Thu Apr 19
00:20:53 2001 Now trying whatever is on the list; ci->canUseSrvrList = 1 Thu Apr
19
00:20:53 2001 INFO: New NON-SSL URL Thu Apr 19 00:20:53 2001 general list: trying
connect to '192.168.1.7'/8001 Thu Apr 19 00:20:53 2001 Connected to 192.168.1.7:8001
Thu Apr 19 00:20:53 2001 INFO: sysSend 320 Thu Apr 19 00:20:53 2001 INFO:
Reader::fill(): first=0 last=0 toRead=4096 Thu Apr 19 00:21:06 2001 parsed all
headers
OK Thu Apr 19 00:21:06 2001 Initializing lastIndex=1 for a list of length=3 Thu
Apr 19
00:21:06 2001 ###Response### : Srvr# [1] = [192.168.1.5:8001] load=1077584792
isGood=1077 546628 numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response###
: Srvr# [2] = [192.168.1.2:8001] load=1077584792 isGood=1077 546628
numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response### : Srvr# [3] =
[192.168.1.7:8001] load=1077584792 isGood=1077 546628 numSkip=1077546628 Thu Apr
19 00:21:06 2001 INFO: Reader::fill(): first=0 last=0 toRead=4096
Basically, the lastIndex=XXX appears to be random. It may do round-robin for 4
or 5
connections but then always it resorts to randomly directing new connections.
This is what the configuration looks like using the plug-in's
/weblogic?__WebLogicBridgeConfig URL:
Weblogic Apache Bridge Configuration parameters:
WebLogic Cluster List:
1.Host: '192.168.1.2' Port: 8001 Primary
General Server List:
1.Host: '192.168.1.2' Port: 8001
2.Host: '192.168.1.5' Port: 8001
3.Host: '192.168.1.7' Port: 8001
DefaultFileName: ''
PathTrim: '/weblogic'
PathPrepend: '' ConnectTimeoutSecs:
'10' ConnectRetrySecs: '2'
HungServerRecoverSecs: '300'
MaxPostSize: '0'
StatPath: false
CookieName: JSESSIONID
Idempotent:
ON FileCaching:
ON ErrorPage: ''
DisableCookie2Server: OFF
Can someone please help to shed some light on this? I would be really grateful,
thanks!
Jeff

Right - it means that the only configuration which can do perfect round-robin is a
single plugin (non-Apache, or single-process Apache) - all others essentially do random
(sort of, but it can skew test results during first N requests).
Robert Patrick <[email protected]> wrote:
Dimitri,
The way Apache works is that is spawns a bunch of child processes and the parent process
that listens on the port delegates the processing of each request to one of the child
processes. This means that the load-balancing dome by the plugin before the session ID is
assigned does not do perfect round-robining because there are multiple copies of the plugin
loaded in the multiple child processes. This situation is similar to the one you would get
by running multiple proxy servers on different machines with the NES/iPlanet and IIS
plugins.
As I pointed out in my response to Jeff, attempting to address this problem with IPC
machanisms would only solve the single machine problem and most people deploy multiple
proxy servers to avoid a single point of failure...
Hope this helps,
Robert
Dimitri Rakitine wrote:
Hrm. This is strange - I thought that all the information nesessary for a
'sticky' load-balancing (primary/secondary) is contained in the cookie/session info,
so, the particular plug-in implementation should not make any difference. For
load-balancing - statistically, given large enough sampling base, Apache plug-in
should perform just a well as NS one (unless apache is somehow misconfigured and
calls fork() for each new request).
Jeff Calog <[email protected]> wrote:
Robert,
Thanks for the sanity reply, you are definitely right. I used Netscape 3.0 on
Win2k and it did perfect round-robin load balancing to my servers.
<raving>
BEA - ARE YOU LISTENING? STOP TELLING PEOPLE YOUR APACHE PLUG-IN IS A VIABLE
LOAD BALANCING SOLUTION! It's worthless for load balancing!
</raving>
In some tests, as many as 90% of my connections/requests would be sent to a single
server. There should be something in the release notes like "By the way, the
Apache plug-in is only advertised as doing round-robin load balancing, in reality
it doesn't work worth a darn".
I'm surprised they don't used shared memory or some other technique (pipes, sockets,
signals, writing to /tmp, anything) for interprocess communication to fix that.
Jeff
Robert Patrick <[email protected]> wrote:
Yes, the problem lies in the fact that Apache uses multiple processes
instead of
multiple threads to process requests. Therefore, you end up with multiple
processes all
with the WebLogic plugin loaded into them (and they cannot see one another)...
Hopefully, Apache 2.0 when it comes out will allow the plugin to do a
better job...
Jeff Calog wrote:
I can't seem to get the Apache plug-in to actually do round-robin loadbalancing
of HTTP
requests. It does random-robin, as I like to call it, since the plug-inwill usually
hit all the
servers in the cluster but in a random fashion.
I've got three managed servers:
192.168.1.5:8001 (WL6 on Linux) 192.168.1.2:8001 (WL6 on Linux) 192.168.1.7:8001
(WL6 on Linux)
Admin server on 192.168.1.7:7000 (WL6 on W2k)
My Apache server is 1.3.9 (RedHat SSL) on 192.168.1.52.
The log file for each servers has something like this:
####<Apr 19, 2001 1:18:54 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
<main> <system> <> <000102> <Joined cluster cluster1 at address 225.0.0.5on port
8001>
####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster> <neptune> <cluster1server1>
<ExecuteThread: '9' for queue: 'default'> <> <> <000127> <Adding
3773576126129840579S:192.168.1.2:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
to the cluster> ####<Apr 19, 2001 1:19:31 AM MDT> <Info> <Cluster><neptune>
<cluster1server1> <ExecuteThread: '11' for queue: 'default'> <> <><000127> <Adding
-6393447100509727955S:192.168.1.5:[8001,8001,7002,7002,8001,7002,-1]:192.168.1.52
to the cluster>
So I believe I have correctly created a cluster, although I did notbother to
assign
replication groups for HTTP session replication (yet).
The Apache debug output indicates it knows about all three serversand I can see
it
doing the "random-robin" load balancing. Here is the output:
Thu Apr 19 00:20:53 2001 Initializing lastIndex=2 for a list of length=3Thu Apr
19
00:20:53 2001 Init Srvr# [1] = [192.168.1.2:8001] load=1077584792 isGood=1077590272
numSk ip=134940256 Thu Apr 19 00:20:53 2001 Init Srvr# [2] = [192.168.1.5:8001]
load=1077584792 isGood=1077590272 numSk ip=134940256 Thu Apr 19 00:20:532001
Init Srvr# [3] = [192.168.1.7:8001] load=1077584792 isGood=1077590272numSk
ip=134940256 Thu Apr 19 00:20:53 2001 INFO: SSL is not configured ThuApr 19
00:20:53 2001 Now trying whatever is on the list; ci->canUseSrvrList= 1 Thu Apr
19
00:20:53 2001 INFO: New NON-SSL URL Thu Apr 19 00:20:53 2001 generallist: trying
connect to '192.168.1.7'/8001 Thu Apr 19 00:20:53 2001 Connected to192.168.1.7:8001
Thu Apr 19 00:20:53 2001 INFO: sysSend 320 Thu Apr 19 00:20:53 2001INFO:
Reader::fill(): first=0 last=0 toRead=4096 Thu Apr 19 00:21:06 2001parsed all
headers
OK Thu Apr 19 00:21:06 2001 Initializing lastIndex=1 for a list oflength=3 Thu
Apr 19
00:21:06 2001 ###Response### : Srvr# [1] = [192.168.1.5:8001] load=1077584792
isGood=1077 546628 numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response###
: Srvr# [2] = [192.168.1.2:8001] load=1077584792 isGood=1077 546628
numSkip=1077546628 Thu Apr 19 00:21:06 2001 ###Response### : Srvr#[3] =
[192.168.1.7:8001] load=1077584792 isGood=1077 546628 numSkip=1077546628Thu Apr
19 00:21:06 2001 INFO: Reader::fill(): first=0 last=0 toRead=4096
Basically, the lastIndex=XXX appears to be random. It may do round-robinfor 4
or 5
connections but then always it resorts to randomly directing new connections.
This is what the configuration looks like using the plug-in's
/weblogic?__WebLogicBridgeConfig URL:
Weblogic Apache Bridge Configuration parameters:
WebLogic Cluster List:
1.Host: '192.168.1.2' Port: 8001 Primary
General Server List:
1.Host: '192.168.1.2' Port: 8001
2.Host: '192.168.1.5' Port: 8001
3.Host: '192.168.1.7' Port: 8001
DefaultFileName: ''
PathTrim: '/weblogic'
PathPrepend: '' ConnectTimeoutSecs:
'10' ConnectRetrySecs: '2'
HungServerRecoverSecs: '300'
MaxPostSize: '0'
StatPath: false
CookieName: JSESSIONID
Idempotent:
ON FileCaching:
ON ErrorPage: ''
DisableCookie2Server: OFF
Can someone please help to shed some light on this? I would be reallygrateful,
thanks!
Jeff
Dimitri--
Dimitri

WLSIFCONFIG in Windows doesnt works. Weblogic Cluster

I am trying to configure a cluster with 2 nodes in Windows WLS10.3.5.
I have configured nodemanager.properties
Interface=eth0
NetMask=255.255.255.0
and i have activated the option "Automatic Migration" of each server.
When i try to init the servers i have problems with the command "wlsifconfig.cmd". it looks that have unix commands like grep, rm, etc...
¿Anyone have the correct command for windows?
thanks a lot

I changed the name of the Interface to eth0.
The problems is unix commands in windows commands. This is my wlsifconfig.cmd
@ECHO OFF
if defined DEBUG @echo on
@REM
@REM Additional commands to support node manager ip migration.
@REM
@REM Parse command and options
if [%1]==[] CALL :usage_error
set COMMAND=
set INTERFACE=
set ADDRESS=
set NETMASK=
set ERRORLEVEL=
if [%1] == [-addif] (
set COMMAND=addif
set INTERFACE=%2%
set ADDRESS=%3%
set NETMASK=%4%
if not defined INTERFACE call :usage_error
if not defined ADDRESS call :usage_error
if not defined NETMASK call :usage_error
if [%1] == [-removeif] (
set COMMAND=removeif
set INTERFACE=%2%
set ADDRESS=%3%
if not defined INTERFACE call :usage_error
if not defined ADDRESS call :usage_error
if [%1] == [-listif] (
set COMMAND=listif
set INTERFACE=%2%
if not defined INTERFACE call :usage_error
@REM Must have specified at least one command
if not defined COMMAND CALL :usage_error
set NullDevice=nul
@REM *********************************************************************
@REM Set this to true if IP address should not be online before starting
@REM a server. Otherwise, presence of an IP address in an interface will
@REM cause the script to report success on IP addif
set ENABLESTRICTIPCHECK=N
if not defined ServerName set ServerName=myserver
if not defined ServerDir set ServerDir=%CD%
if not exist "%ServerDir%\data\nodemanager" mkdir "%ServerDir%\data\nodemanager"
set addrFile=
set addrFile=%ServerDir%\data\nodemanager\%ServerName%.addr
call :%COMMAND%
GOTO :EOF
@REM --- Start Functions ---
@REM *********************************************************************
@REM Show an error if the address does not show up in the address file
:address_error
SETLOCAL
ECHO Cannot remove %ADDRESS% - not brought online >&2
exit 1
@REM *********************************************************************
@REM Remove the given address from the interface specified
:removeif
SETLOCAL
@REM Store the contents of the address file as the %addr% var
if exist "%AddrFile%" (
grep %ADDRESS% %AddrFile% > null || call :address_error
netsh interface ip delete address %INTERFACE% addr=%ADDRESS%
set remExitVal=%ERRORLEVEL%
if not %remExitVal% == 0 (
echo Unable to remove %ADDRESS% - Check command output for more details >&2
call :cleanupAddressFile
exit %remExitVal%
echo Successfully removed %ADDRESS% from %INTERFACE%.
call :cleanupAddressFile
GOTO :EOF
@REM *********************************************************************
@REM Show the correct message (info or error) if the given address is already
@REM on the specified interface. This is normally an informative message
@REM unless ENABLESTRICTIPCHECK is set to something other then the default 'N'.
:already_online
if [%ENABLESTRICTIPCHECK%] == [N] (
echo %ADDRESS% already online on %INTERFACE%. Please make sure that the IP address specified is not used by other servers/applications. Continuing...
) ELSE (
echo %ADDRESS% already online on %INTERFACE%. Please make sure that the IP address specified is not used by other servers/applications >&2
call :cleanupAddressFile
exit 1
GOTO :EOF
@REM *********************************************************************
@REM Show that an error occured calling the netsh utility
:add_error
SETLOCAL
echo Failed to bring %ADDRESS% with %NETMASK% online on %INTERFACE% >&2
echo Check command output for more details >&2
exit 1
ENDLOCAL
@REM *********************************************************************
@REM Add the given address to the specified interface
:addif
SETLOCAL
set newif=
netsh interface ip show address %INTERFACE% | grep -e '[^      ]*IP' > tmp_ip_file
for /F "usebackq tokens=3" %%G in ( tmp_ip_file ) do (
if %%G == %ADDRESS% set newif=already-online
if not defined newif set newif=unmatched
del tmp_ip_file
if [%newif%] == [unmatched] (
call :addnew
) ELSE call :already_online
if exist "%AddrFile%" call :cleanupAddressFile
echo %ADDRESS%>> "%AddrFile%"
ENDLOCAL
GOTO :EOF
@REM *********************************************************************
@REM For some reason catching the error value has problems when it is not in
@REM its own subroutine. Setting addExitVal in the :addif routine leaves the
@REM variable as undefined causing extra error messages in the script output
@REM
:addnew
SETLOCAL
netsh interface ip add address %INTERFACE% %ADDRESS% %NETMASK%
set addExitVal=%ERRORLEVEL%
if not %addExitVal% == 0 call :add_error %addExitVal%
echo Successfully brought %ADDRESS% with %NETMASK% online on %INTERFACE%
ENDLOCAL
GOTO :EOF
@REM *********************************************************************
@REM Check the %AddrFile% for %ADDRESS% and if it is there, then call the
@REM subroutine to delete it
@REM
:cleanupAddressFile
SETLOCAL
if exist "%AddrFile%" (
grep -x %ADDRESS% %AddrFile% > nul & CALL :removeAddressFromFile
ENDLOCAL
GOTO :EOF
@REM *********************************************************************
@REM Delete %ADDRESS% from the %AddrFile%
@REM
:removeAddressFromFile
SETLOCAL
set tmpAddr=addresses.tmp
for /F "delims=" %%a in (%AddrFile%) DO (
if not %%a == %ADDRESS% (
     echo %%a>> %tmpAddr%
del -f %AddrFile%
if exist %tmpAddr% (
move %tmpAddr% %AddrFile%
del -f %tmpAddr%
ENDLOCAL
GOTO :EOF
@REM *********************************************************************
@REM List the IP addresses that are currently on the interface
:listif
netsh interface ip show address %INTERFACE% | grep -e '[^      ]*IP'
GOTO :EOF
@REM *********************************************************************
@REM Show the correct usage of this script in the instance that someone
@REM called the script incorrectly
:usage_error
ECHO Usage: wlsifconfig.cmd >&2
ECHO -addif {interface-name} {ip-address} {netmask} >&2
ECHO -removeif {interface-name} {ip-address} >&2
ECHO -listif {interface-name} >&2
ECHO 'addif' adds {ip-address} to next available sub-interface of {interface-name}. >&2
ECHO 'removeif' removes {ip-address} from sub-interface of {interface-name}. >&2
ECHO 'listif' lists last used sub-interface of {interface-name} and its corresponding {ip-address} >&2
ECHO To grep the list of interfaces, use your following command to list the interface names- >&2
ECHO netsh interface show interface. >&2
exit -101
GOTO :EOF
:ENDFUNCTIONS
@REM --- End Functions ---

Using StoneBeat WebCluster load balancing with WebLogic

          Hi,
          I have done some testing of WebLogic Server with my company's StoneBeat WebCluster
          distributed load balancing software. This might be one more option to consider
          as a load balancing solution for WLS. It is advanced in the sense that load balancing
          is really dynamic, there are no single-points of failure (distributed architecture)
          and there is a very good, configurable test subsystem that runs on each cluster
          node to check for overload situations, HW/OS failures, ...
          In the initial testing, the WebCluster load balancing works with WebLogic replication,
          although there are some cases that need mroe consideration (please see below).
          I had to get a patch to WLS6SP1 on NT to make WLS' multicast work when there are
          several NICs on the cluster nodes.
          However, there is one case which causes problems:
          - I have 3 cluster nodes
          - P: 2, S: 3 (SessionServlet = 1)
          - 2: offline - P: 3, S: 1 (SessionServlet = 2; WebCluster randomly selected a
          new node to handle the connection)
          - 2: online - P: 2, S: ? (SessionServlet = 3, WebCluster redistributes the load
          when a node goes online)
          - 2: offline
          - P: 3, S: 1 (__SessionServlet = 1__) NB!
          The log messages show that when node 2 comes back online it retrieves the replica
          from the secondary (node 1) and not from the primary (node 3). After a while (5-6
          minutes), node 3 tries to update the replica on node 1. Node 1 considers this
          a stale update request and removes the Primary 16... (node name) and then the
          secondary for 16... (the replicated object). Then there's a message (still on
          node 1) that it is unable to find object 16... Back on node 3 the primary for
          16... is removed.
          From the WLS6 documentation (under the discussion of using replication with external
          HW load balancing solutions) I thought that this case would have been handled:
          - it is stated that after the failure of a node, if the HWLB box sends the next
          request to a node where there is no replica, WLS is able to retrieve the replica
          - to be fair, this is what happens: when node 2 came back online, it retrieved
          the replica from node 1 (the secondary) - I suppose that there is an assumption
          that if a request arrives to a node without a replica, the primary __must have
          failed__
          Is there any way to get around this problem?
          Admittedly, WebCluster has a problem in that the stickyness of connections is
          not perfect: - when a node goes online, a connection that was correctly persisted
          (based on either source-ip or source-network address) may be moved to a new node
          since the load is redistributed. Our load balancing is very dynamic, but doesn't
          maintain a list of who is connected to which node when resistribution takes place
          Regards,
          Frank Olsen
          Stonesoft


Rick,
You may want to look at the Alteon and F5 configuration we have on edocs.
Take a look at the following URLs for a possible solution
http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902
http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902
Chuck Nelson
DRE
BEA Technical Support

Time service load-balancing

Hi,
I have a question about load-balancing facilities for Time service. If I
schedule a TimeScheduleDef object to run at certain intervals, does the
run-time environment take care of load balancing it across multiple machines
on a cluster?
Thanks,
Deepak

WebLogic Time is not a clustered service -- it is configured per server and
load balancing is performed.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Deepak Goel <[email protected]> wrote in message
news:8gvrdb$n18$[email protected]..
Hi,
I have a question about load-balancing facilities for Time service. If I
schedule a TimeScheduleDef object to run at certain intervals, does the
run-time environment take care of load balancing it across multiplemachines
on a cluster?
Thanks,
Deepak

Load Balancing in RAC

If you have 2 node cluster , you have configured Node 1 as Preferred instance and Node 2 as available.
According to Oracle , the service will always run on a preferred instance and will relocate to available instance in case of preferred node failure.
Also you have server side load balancing, as per documentation the service will relocate on available instance if the preferred node crashes.
Question: How will Oracle take care of Load Balancing , since the service on available node will only run if the preferred node crashes. Since the service is not running on Node 2 (available instance) ? How will oracle distribute the connections among the nodes?

The answer to your question depends one the configuration of your Oracle Net Services, Whether you have configured connection load balancing or server side load balancing. Oracle will only balance the workload among the database instance running the service. By default Oracle starts the service on prefered node and in your case you have configured only one preferred database instance for your service and at a time service will run on one node only so Oracle does not have any options to distribute the workload even if you have configured the server side load balancing for the services using the service level goals.
To explain it further, consider you have 3 node cluster. The database instance on first and second node are preferred instances for the net service and service-level goals are defined for server side load balancing.
Now suppose second node fails and Oracle relocates the service to third node. Because Oracle is aware about the services running in the cluster even the relocated services (You should read about LOCAL_LISTENER and REMOTE_LISTENER to understand how Oracle register services with listeners on other cluster nodes) thats why using the load balancing advisory Oracle decides, which node the new database connection should be connected.

Oracle Applications 11i Load Balancing does not work with RAC one Node

Hi all,
Could you help me to resolve this issue.
Architecture environment is :
- One APPS tier node
- Two nodes Oracle Database Appliance (Primary node 1 holds INSTANCE_1 et Secondary node is configurured to holds INSTANCE_2), i.e RAC one Node.
- The primary node have instance_name SIGM_1 and the secondary node have instance_name SIGM_2, but in RAC one node, the secondary instance is not alive.
We convert our EBS 11i environment to RAC following note ID Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 11i [ID 823586.1].
When testing Database failover, Oracle Applications 11i load balancing does not work anymore.
The root cause is that, when the primary node of the Rac one node is down, the INSTANCE_NAME_1 is automaically relocating to the surviving node,.
During test failover, we imagine that when the primary node goes down, the secondary node start or relocate database with instance_name SIGM_2, and in that case the Oracle Applications load balancing works.
Currently, when the primary node goes down, the instance_name SIGM_1 is relocated on the secondary node, which cause failure of Oracle Applications Load Balancing.
Thank you for your advice.
Moussa

This is something I observed a long time ago for Safari (ie: around version 1). I'm not sure this is Safari, per se, but OpenSSL that is responsible for the behavior. I'm pretty sure Chrome does this and I've seen some Linux browsers do it.
What I have done at the last two companies I've worked for is recommend that our clients do not use SSL SessionID as the way of tracking sticky sessions on web servers, but instead using IP address. This works in nearly all cases and has few downsides. The other solution is to use some sort of session sharing on your web servers to mitigate the issue (which also means that your web servers aren't a point of failure for your users' sessions). (One of the products I supported had no session information stored on the web servers, so we could safely round-robin requests, the other product could be implemented with a Session State Server... but in most cases we just used IP address to load balance with). The other solution is to configure your load balancer to terminate the SSL tunnel. You get some other benefits from this, such as allowing your load balancer to reduce the number of actual connections to the web servers. I've seen many devices setup this way.
One thing to consider through this is that - due to the way internet standards work - this really can't be termed a bug on anyone's part. There is no guarantee in the SSL/TLS standards that a client will return the same SSL Session ID for each request and there is not requirement that subsequent requests will even use the same tunnel. Remember, HTTP is a stateless protocol. Each request is considered a new request by the web server and everything else is just trickery to try and get it to work the way you want. You can be annoyed at Safari's behavior, but it's been this way for over 5 years by my count, so I don't expect it to change.

Multicast not working with Window2K Network Load Balancing.

I'm using W2K Network Load Balancing (WBLB) for our cluster machines (2
          boxes) to load balance between IIS (one IIS instance on each box). Each IIS
          instance is a proxy to the weblogic cluster (one app server instance on each
          box). Currently I only have a single network card configured for each box,
          so I have had to enable multicast support for the WNLB. But if I do this
          I'm unable to get multicasting working correctly for the weblogic cluster.
          When I run the multicast tester (utils.MulticastTest) one box is able to
          receive multicast messages from both boxes, but the other box is only
          receiving multicast messages from itself (but not the other box). Does
          anyone have any experience with configuring weblogic clustering on machines
          with WNLB also configured?
          Thank you.
          Marko.


Hi
NLB return traffic for UDP would come from the node IPs.
You could use NAT on your firewalls so they come from the same public IP.
Otherwise you'd be looking at something other than MS NLB.
Cheers
GF

Cluster/load balance weblogic using L4 switch like Alteon

Can I install weblogic as a standalone server on 2 or more server and
          cluster/load balance weblogic using a hardware balancer like Alteon Layer4
          switch (of course I will use a centralised storage to maintain a single copy
          of data which will eliminate syncronizing problem among servers)?
          BTW, Alteon can support persistent binding. The reason to use a Layer 4
          switch is that it is very fast, and this will make the application server
          layer transparent to client, the client can think this is a single server
          (it don't need to know whether there are 5 weblogic servers or 20 weblogic
          servers behind switch), and hardware are more reliable, sacalable and fast.
          I am not sure whether the normal weblogic clustered servers need to
          share/exchange info on the running memory, if it does, this approach will
          fail.


So My understanding is:
          Alteon with WL 6.0 can do load balancing for:
          entity bean
          stateless session bean
          but can't do load balancing for:
          stateful session bean (will persistent/sticky binding solve part of the
          problem except fail-over)
          in-memory replication
          am I right?
          Pao Wan
          "Don Ferguson" <[email protected]> wrote in message
          news:[email protected]...
          > It is possible to configure Alteon to understand the WebLogic 6.0 cookie
          format
          > and have a proxy-less cluster configuration that performs load balancing
          and
          > fail over of session state.
          >
          > It is also possible to configure Alteon's hardware-based SSL decryption
          for really
          > fast HTTPS processing.
          >
          > We are working on a white paper that describes how to configure Alteon for
          use
          > with WebLogic Server 6.0.
          >
          > -Don
          >
          >
          > Robert Patrick wrote:
          >
          > > Cameron,
          > >
          > > I believe that BEA tested their new proxy-less web clustering solution
          with
          > > load-balancing products from Alteon and several other vendors
          (Arrowpoint ?--
          > > which is now Cisco). However, it was my understanding that these
          products do
          > > not understand how to decrypt our cookies and extract IP addresses but
          rather
          > > these products are capable of doing sticky load balancing based on the
          Session
          > > ID contained in our cookie.
          > >
          > > If this is correct, then what this means is that when the primary server
          fails,
          > > the request will be routed to "some other server" in the cluster but not
          > > necessarily the one that holds the secondary copy of the user's session.
          The
          > > change in WLS 6.0 is that WLS will accept these misdirected requests and
          it will
          > > go out to the correct server and "migrate" the session to the server
          that
          > > received the request making that server the new primary (and
          regenerating the
          > > Session ID).
          > >
          > > I am sure if this is wrong that our product manager or one of our
          engineers will
          > > correct me (please?)...
          > >
          > > Hope this helps,
          > > Robert
          > >
          > > Cameron Purdy wrote:
          > >
          > > > Hi Robert,
          > > >
          > > > FWIW - There are several vendors (Primeon? Arrowpoint?) who claim to
          > > > understand WL cookies and parse the IPs out. (I haven't verified it
          myself
          > > > though.)
          > > >
          > > > --
          > > > Cameron Purdy
          > > > Tangosol, Inc.
          > > > http://www.tangosol.com
          > > > +1.617.623.5782
          > > > WebLogic Consulting Available
          > > >
          > > > "Robert Patrick" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > There are not any hardware vendors (yet) that can understand
          WebLogic's
          > > > session
          > > > > ID. While you might be able to use the load balancer without the
          proxy on
          > > > 5.1,
          > > > > you would not be able to take advantage of in-memory replication
          failover
          > > > unless
          > > > > you only had two machines in the cluster. Like you said, everything
          will
          > > > work
          > > > > with 6.0 regardless of how the load balancer works (though you
          really,
          > > > really
          > > > > want to minimize the number of times the requests come into the
          wrong
          > > > server by
          > > > > utilizing sticky load balancing).
          > > > >
          > > > > Hope this helps,
          > > > > Robert
          > > > >
          > > > > Cameron Purdy wrote:
          > > > >
          > > > > > Rajesh,
          > > > > >
          > > > > > I meant that it would work in lieu of a proxy (such as Apache or
          NES)
          > > > with
          > > > > > 5.1, but only if both the hw load balancer and WL were set up to
          use
          > > > > > cookies. Some hw load balancers rely on IP and that doesn't
          work -- AOL
          > > > > > connections for example can change the source IP on the fly.
          Others
          > > > produce
          > > > > > their own cookies, that will work. Some even can use WL cookies
          and
          > > > parse
          > > > > > them to determine where to go. According to what I've read, with
          6.0 if
          > > > the
          > > > > > WL primary dies or for some other reason the request shows up at
          the
          > > > "wrong"
          > > > > > server, it will be handled correctly. That means you are pretty
          safe
          > > > with
          > > > > > hw load balancers and 6.0, almost regardless of the sticky
          > > > implementation
          > > > > > that they use.
          > > > > >
          > > > > > --
          > > > > > Cameron Purdy
          > > > > > Tangosol, Inc.
          > > > > > http://www.tangosol.com
          > > > > > +1.617.623.5782
          > > > > > WebLogic Consulting Available
          > > > > >
          > > > > > "Rajesh" <[email protected]> wrote in message
          > > > > > news:[email protected]...
          > > > > > >
          > > > > > > Hi Cameron,
          > > > > > > Can you elaborate on how it would work with WL5.1 since no in
          memory
          > > > > > replication
          > > > > > > would happen if the servers are standalone.
          > > > > > >
          > > > > > > "Cameron Purdy" <[email protected]> wrote:
          > > > > > > >Yes, this will work fine with WL6. (WL5.1 will work fine as
          long as
          > > > > > cookies
          > > > > > > >are used by the load balancer.)
          > > > > > > >
          > > > > > > >--
          > > > > > > >Cameron Purdy
          > > > > > > >Tangosol, Inc.
          > > > > > > >http://www.tangosol.com
          > > > > > > >+1.617.623.5782
          > > > > > > >WebLogic Consulting Available
          > > > > > > >
          > > > > > > >
          > > > > > > >"paowan" <[email protected]> wrote in message
          > > > > > > >news:[email protected]...
          > > > > > > >> Can I install weblogic as a standalone server on 2 or more
          server
          > > > and
          > > > > > > >> cluster/load balance weblogic using a hardware balancer like
          Alteon
          > > > > > Layer4
          > > > > > > >> switch (of course I will use a centralised storage to
          maintain a
          > > > single
          > > > > > > >copy
          > > > > > > >> of data which will eliminate syncronizing problem among
          servers)?
          > > > > > > >>
          > > > > > > >> BTW, Alteon can support persistent binding. The reason to use
          a
          > > > Layer
          > > > > > > >4
          > > > > > > >> switch is that it is very fast, and this will make the
          application
          > > > > > server
          > > > > > > >> layer transparent to client, the client can think this is a
          single
          > > > > > server
          > > > > > > >> (it don't need to know whether there are 5 weblogic servers
          or 20
          > > > > > weblogic
          > > > > > > >> servers behind switch), and hardware are more reliable,
          sacalable
          > > > and
          > > > > > > >fast.
          > > > > > > >>
          > > > > > > >> I am not sure whether the normal weblogic clustered servers
          need to
          > > > > > > >> share/exchange info on the running memory, if it does, this
          > > > approach
          > > > > > will
          > > > > > > >> fail.
          > > > > > > >>
          > > > > > > >>
          > > > > > > >
          > > > > > > >
          > > > > > >
          > > > >
          >

H-REAP and Client Load-Balancing

I'm told by Cisco that H-REAP does not support client load-balancing.
We have a situation where we want to deploy LWAPPs using H-REAP into a conference room where training would take place.
Any suggestions on how to overcome the inevitable slowness these people are going to experience from being unevenly associated with the APs?
We can't re-write the application so we are looking for a wireless solution.
Anyone hear about how other organizations have dealt with this type of situation?
I'll be glad to supply more details if I am not being clear in my description of the problem.
Thanks in advance. All responses will be rated.
Paul

This is the functionality which is missing in H-REAP: Client and Network Load Balancing
"Radio Resource Management (RRM) load-balances new clients across grouped lightweight access points reporting to each controller. This function is particularly important when many clients converge in one spot (such as a conference room or auditorium) because RRM can automatically force some subscribers to associate with nearby access points, allowing higher throughput for all clients. The controller provides a centralized view of client loads on all access points. This information can be used to influence where new clients attach to the network or to direct existing clients to new access points to improve wireless LAN performance. The result is an even distribution of capacity across an entire wireless network.
Note: Client load balancing works only for a single controller. It is not operate in a multi-controller environment."
I suppose if we limit the number of users that can associate with a particular AP then we will achieve some client load-balancing. Though a hard limit on the number of end-users will also lead to situations where some end users will not be allowed any access.

Who takes care of load balancing work in weblogic cluster ?

Similar Messages

Maybe you are looking for