EJB - Load Balancing in GlassFish cluster

Hi,
I have been using GlassFish v2 for a year now developing EAR applications very happily. Now, I am starting to think of clustering due to the large amount of webpages of our new website (approx 600.000).
I have been reading blogs, documents, and watching a really cool YouToube video on how to set up a glass fish cluster in less than ten minutes but Not once i have seen that EJB load does also get balanced.
My question is, once the cluster is up and running. Does the EJB load also get distributed amongst each glassfish instance?
Pablo.

Similar Messages

Load balancing for BPEL Cluster

Can anybody tell how to configure the load balancer in BPEL Cluster ..? I am not able to get the correct documents for that. I want the request from the client can be redirect to any of the cluster server that will be having the PPEL Process deployed.
Can i use third party load balancer also or can i use oracle http server as load balancer ....how to configure in both the case?

Hi Dominik.
Thanks for responding to my message.
Where could i find more info relating to the WEB dispatcher.
I also posted a message on OSS and SAP did not mention
a WEB Dispatcher. (Startup Framework and the J2ee dispatcher handing the load balancing)
Is the WEB dispatcher a must or are there alternate solutions. I am still confused on this topic ??
On the current EP5 release, the load balancing is handled
via MS Load Balancing.
Thanks and appreciate the help !!
Morgan
Message was edited by: Morgan Moodley

Load balancing without a cluster...!!!!????

Hi boys!
          I have a question for you: my NES proxy server can realize a load
          balancing between 2 weblogic 6.0 servers that are NOT IN A CLUSTER?
          I've done some tests configuring the obj.conf like the 2 weblogic
          servers were in cluster, but I dont' understand if it works correctly.
          May be I ask too much ...
          Thanks
          Patrizia


          I'm assuming your using one browser to test this.
          The first time you access a servlet or a JSP that uses session
          tracking, the WL server will store a cookie in the browser. This
          cookie identifies the IP address and port number of the WLS where
          the request was executed (the Primary), and if it is a clustered
          configuation with session replication enable, also a Secondary
          server.
          The next time you make a request to iPlanet (or Apache), wlproxy
          looks at the cookie and directs you to the same WL server - so
          you won't see any load balancing.
          If you quit out of all your browsers, then start a new browser,
          and access it again, you won't have a WL cookie, and the request
          will get load balanced to one of the WL servers.
          Mike
          Patrizia MB <[email protected]> wrote:
          >Thanks Mike,
          >but I've some problems in verifying what you've asserted.
          >In my obj.conf I've put
          >
          > <Object name="wl" ppath="*/servlet/*">
          >
          > Service fn="wl-proxy" WebLogicCluster="10.0.0.3:7060,10.0.0.8:7060"
          >DebugConfigInfo="ON" Debug="ON"
          >
          > </Object>
          >
          >Note that I have 2 NOT-Clustered WLS instances behind
          >NES: I used
          >the "WebLogicCluster" property in the obj.conf only because
          >this
          >is the only way - as far as I know ! - to specify multiple
          >nodes to the
          >proxy.
          >
          >
          >With your suggestion, accessing the URL
          >"http://<your-nes-server>/?__WebLogicBridgeConfigInfo"
          >I can see this:
          > Query String: '__WebLogicBridgeConfig'
          > This entry is cluster aware.
          > ClusterID (from obj.conf): "10.0.0.3:7060,10.0.0.8:7060"
          > WebLogic Cluster List:
          > 1.Host: '10.0.0.8' Port: 7060 Primary
          > General Server List:
          > 1.Host: '10.0.0.3' Port: 7060
          > 2.Host: '10.0.0.8' Port: 7060
          >
          >
          >
          >
          >
          >In spite of that, there's no load-balancing!
          >I checked the 2 access files on the 2 nodes, and I see
          >that all my
          >requests go to the same server 10.0.0.8.
          >Why?
          >According to which logic 10.0.0.8 has been defined the
          >Primary? (They
          >are both Administration Servers)
          >
          >I hope you'll answer to my questions!
          >
          >TIA
          >
          >Patrizia
          >
          >
          >
          >
          >
          >
          >Mike Reiche wrote:
          >
          >> The wlproxy for NES will round-robin requests to multiple
          >WL
          >> servers if they are clustered or not clustered.
          >>
          >> You can get some additional information by adding the
          >property
          >> DebugConfigInfo=ON to the WL configuration in obj.conf
          >then
          >> hitting the URL...
          >> http://<your-nes-server>/?__WebLogicBridgeConfigInfo
          >>
          >> Check the WL NSAPI doc.
          >>
          >> Mike
          >>
          >> Monteforte Patrizia <[email protected]>
          >wrote:
          >> >Hi boys!
          >> >I have a question for you: my NES proxy server can
          >realize
          >> >a load
          >> >balancing between 2 weblogic 6.0 servers that are
          >NOT
          >> >IN A CLUSTER?
          >> >I've done some tests configuring the obj.conf like
          >the
          >> >2 weblogic
          >> >servers were in cluster, but I dont' understand if
          >it
          >> >works correctly.
          >> >May be I ask too much ...
          >> >
          >> >Thanks
          >> >
          >> >Patrizia
          >> >
          >

IIS 6 fails to load balance to weblogic cluster

Hi,
We have iis 6 which proxies request to weblogic cluster running on version 9.2 MP1. Recently we noticed the connections are overloaded on a weblogic instance while the other instance had lower connections.
I suspect it to be the IIS load balancing to the single instance. Can anyone help please.
I traced the IIS logs and can see the citrix IP as destination since the user access the application thru citrix sessions.
Thanks,

Hi,
We have iis 6 which proxies request to weblogic cluster running on version 9.2 MP1. Recently we noticed the connections are overloaded on a weblogic instance while the other instance had lower connections.
I suspect it to be the IIS load balancing to the single instance. Can anyone help please.
I traced the IIS logs and can see the citrix IP as destination since the user access the application thru citrix sessions.
Thanks,

What is load balancer in fms cluster and how to configure it and testing fms clustering

Hey guys,
I am new to fms and clustering the fms server in origin-edge mode.But i am confused actually what is load balancer and how to configure it .
After configuring , how to test and confirm that fms clustering is working.Is there any one can help me, plz....................
thanks in Advance........

Flash Media Server does not come bundled with a load balancer. In theory, one deploys FMS in an edge/origin configuration like this
1 Origin ----> N Edges ------> Customer Traffic
The idea here is that N edges shoulder the load for most customers with a single origin coordinating resources like VOD content or script access. The issue that remains is "how do I spread customers over the N edges" and that's where load balancing comes in. Most customers use a prepackaged load balancing solution - as an Adobe staffer I can't recommend any of them over the other, but you should be able to get some recommendations here along with just googling for it. The short answer contained here though is, you're going to have to find one outside of FMS if that's needed for your setup.
Asa

WLS 5.1 SP8 improper load balancing of EJB

I have noticed a strange behaviour in load balancing of EJB.
          I have 3 instances of WLS 5.1 sp8 running under a cluster, lets say X, Y and
          Z. Now if I access the EJB in the cluster from with in one of the WLS
          instances(eg servlet), lets say Y, then I always get the reference from that
          same machine "Y" no matter what load balancing algorithm I set. No matter
          how many times I access this EJB from machine Y it will only give me
          reference of EJB from Y. Somehow this seems wrong, it should round-robin
          between X, then Y then Z and then X again no matter where I get a reference
          from.
          Now if I access the EJB from outside of the cluster, a fourth JVM, then each
          time I get the reference from a different machine and clustering works fine
          and load balances as expected.
          Any explanation, workaround ??? Most of the EJB referencing we are doing is
          within the cluster itself, this is causing problems because everything
          works, but on a single machine even though we have a cluster set up. We only
          reference the EJB externally once, that does get clustered, but from that
          point on, everything happens on that machine.


          What you really want to do is use CallRouter - I've used it with clustered RMI,
          I have not used it with EJB. (but EJB use RMI so you should be able to make it
          work).
          Personally, I'd be writing my number crunching bits in C about now.
          Mike
          "Haider Kazmi" <[email protected]> wrote:
          >Thanks Mike, let me give creating InitialContext with specific IP address
          >a
          >try , maybe we can put in load sharing logic in our code this way.
          >
          >As for using C, I think as with all products, our marketing team wouldn't
          >like that but thats a definate approach to improve performance.
          >
          >cheers
          >
          >"Mike Reiche" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> You're doing heavy computation in Java - it's going to be slow.
          >> Write it in C, call it using JNI and it will be about 10 times as fast.
          >>
          >> There 'executing sequentially' is not a function of the EJB
          >specification. I
          >> assume your code looks something like...
          >>
          >>
          >> result1= ejb1.calculate1 ( a, b, c );
          >> result2= ejb2.calculate2 ( e, f, result1);
          >> result3= ejb3.calcualte3 ( x, result3);
          >>
          >> caculate3 won't be called until calculate2 has finished, which won't
          >be
          >called
          >> until calculate1 has finished. Sequential.
          >>
          >> If you really want to force the EJBs on a specific WL instance, just
          >specify the
          >> IP address and port number when you create the InitialContext.
          >>
          >> Mike
          >>
          >>
          >>
          >> "Haider Kazmi" <[email protected]> wrote:
          >> >Hi Mike
          >> >
          >> >> First you gotta understand that calling an EJB on a remote JVM costs
          >> >about
          >> >10 times
          >> >> as much as calling one on a local instance. That's what I tried
          >to
          >> >say in
          >> >the
          >> >> first followup.
          >> >>
          >> >> Second, if whatever is calling the EJB (JSP, Servlet) is load balanced,
          >> >then -
          >> >> presto - all the EJB calls are load balanced as well.
          >> >
          >> >Thats definately true, I think I might have created some confusion,
          >what
          >> >I
          >> >was really trying to say is that we are doing a lot of processing
          >and
          >> >its
          >> >mathematical in nature unlike the standard credit card transaction
          >or
          >> >website transaction. We have optimized this to a large extent, the
          >real
          >> >problem we get into is when the consumers of this result try to consume
          >> >them, each of which are stateless session beans.
          >> >The result gets posted on a JMS topic, servlet was an example, what
          >we
          >> >actually have are JMS clients calling more EJBs once a result is posted
          >> >on
          >> >the JMS topic. So here is how it goes, once the processing of workflow
          >> >is
          >> >done, this published on the relevent JMS topic based on the result
          >of
          >> >the
          >> >workflow process. All the related JMS clients subscribed to this topic
          >> >pick
          >> >it up. They call relevent EJBs with this result. So we don't have
          >control
          >> >over load balancing our clients.
          >> >
          >> >> The only time that such a configuration would load only one instance
          >> >is if
          >> >you
          >> >> only had one such EJB call at a time. But this is still faster
          >than
          >> >having the
          >> >> EJBs load balanced on remote JVM. Load balanced or not, the EJB
          >calls
          >> >are
          >> >NOT
          >> >> made in parallel, thus the calling method has to wait for the first
          >> >call
          >> >to finish,
          >> >> then the second, then the third... so that if each call takes longer
          >> >on a
          >> >remote
          >> >> JVM than locally, your total wait time is longer.
          >> >thanks for this info. I think I better read the EJB specs in more
          >details.
          >> >however whats not clear to me is even if the EJBs are different (not
          >> >just
          >> >different instances of the same EJBs and what about different instances
          >> >of
          >> >the same EJB, are things still done sequentially) will only one method
          >> >be
          >> >called at a time??
          >> >
          >> >> Maybe that's not clear - distributing the calls does not make anything
          >> >happen
          >> >> any faster - it just spreads it out.
          >> >Is this also true for stateless session beans, specifically among
          >different
          >> >instances of the same bean?
          >> >
          >> >> You should be spending your time figuring out how to reduce the
          >amount
          >> >of
          >> >processing.
          >> >This is where I am stuck at now. We are at a point where a lot of
          >the
          >> >optimization is done. The problem arizes when processing is done and
          >> >the
          >> >result is posted on the JMS, a bunch of stateless session bean try
          >to
          >> >consume the result all at once.
          >> >
          >> >
          >>
          >
          >

Query - Business Objects- CMS Cluster internals for load balancing/ sharing

Hi,
We are implementing CMS Cluster solution between two BOE server on Windows 2003 OS. As per documentation, One CMS server is primary, which coordinates with secory CMS server within same cluster. Does both server share equal load without external load balancer, by BOE cluster functionality? What are the tuning parameters for Load balancing between 2 CMS servers?
Thanks for your help!!
Regards,
G

If you somehow needed to accomplish load balancing between the 2 machines which wasn't 50/50 you could possibly try dns aliasing and have more copies of one machine than the other. I'm not recommending this, just thinking out loud here.

How to configure Load Balancer in front of Web Logic Cluster

hi all,
I installed 2 weblogic servers in cluster and now i want to deploy Hardware Load balancer in front of them, i want to know do i require any configuration on servers or i just deploy hardware Load balancer in front clustered servers with round robin technique.
Regards,
imran

I think there are two important configuration when you use hardware load balancer in front of WebLogic cluster.
1) Passive Cookie Persistance
You need to configure hardware load balancer so that it can identify Weblogic session cookie for routing request primary server holding HTTP sesstion.
2) External DNS
If there is firewall between hardware load balancer and weblogic cluster and NAT (Network translation ) is used, then you need to configure "External DNS" for each weblogic server in cluster. You need to specify the hostname used by load balancer in "external DNS".
More details about this are available at.
http://edocs.bea.com/wls/docs92/cluster/load_balancing.html#wp1026940
http://e-docs.bea.com/wls/docs92/cluster/planning.html#wp1088950
Hope this will help...
Jayesh
Yagna Sys

Load Balancing of 2-Tiered vs 3-Tiered Clustering

Hi,
          I was looking at the cluster diagrams on the clustering page:
          http://www.weblogic.com/docs60/cluster/index.html
          And I can't help notice a slight descrepency between the diagram of a 2-Tier
          cluster (WL web cluster + WL app cluster) vs.a 3-Tier cluster (web
          proxy-plugin + WL web cluster + WL app cluster).
          In the 2-Tier diagram, the arrows going from the web nodes to the app nodes
          converges to a single point, indicating that there's load balancing of
          servlet calls to ejbs.
          In the 3-Tier diagram, the arrows from each web node point directly to an
          app node, which seems to indicate that there is a static one-to-one
          relationship, hence no load-balancing. Below the 3-Tier diagram, one of the
          described limitations of using standalone web server and proxy plug-ins is:
          a.. Limited Load Balancing Options: When you use proxy plug-ins or the
          HttpClusterServlet to access clustered servlets, the load balancing
          algorithm is limited to a simple round-robin strategy.
          I believe this is describe load balancing between the fire-wall and the
          proxy web servers. But what about the load balancing between the WL web
          servers and the app servers? Does it exist, or does one web server always
          assigned to one app server?
          Gene Chuang
          Join Kiko.com!


Currently, we only support clusters within the same subnet, as most routers
          can't handle multicast traffic. We are considering designs to relax this
          restriction in a future release.
          -Don
          Cameron Purdy wrote:
          > > 3) In WLAS6.0, you can specify how to pick the secondary server. Most
          > > important of all, pick a secondary server which is on the different
          > physical
          > > box than primary.
          >
          > ... and if you are using two different physical networks, make sure it is on
          > the other physical network. Any hints on how to do that?
          >
          > --
          > Cameron Purdy
          > Tangosol, Inc.
          > http://www.tangosol.com
          > +1.617.623.5782
          > WebLogic Consulting Available
          >
          > "Wei Guan" <[email protected]> wrote in message
          > news:[email protected]...
          > > Here is my understanding:
          > > 1) Proxy will route new sessions based on round-robins. Old sessions will
          > > route to the primary server.
          > > 2) Primary server will pick the secondary server.
          > > 3) In WLAS6.0, you can specify how to pick the secondary server. Most
          > > important of all, pick a secondary server which is on the different
          > physical
          > > box than primary.
          > >
          > >
          > > --
          > > Hope it helps.
          > >
          > > Cheers - Wei
          > >
          > >
          > > "Cameron Purdy" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > Is it true that the proxy can only use round-robin to load-balance the
          > WL
          > > > cluster? I understand that, once selected for a session, the proxy will
          > > > always route requests to the primary server specified in the cookie or
          > URL
          > > > (or secondary), but in the case that no primary or secondary has been
          > > > assigned, can the proxy pick a destination server (which I assume
          > becomes
          > > > the primary) using an algorithm such as "random" (which is theoretically
          > > > superior to round-robin over time)? Also, who picks the secondary
          > server?
          > > > Is it the primary or the proxy?
          > > >
          > > > --
          > > > Cameron Purdy
          > > > Tangosol, Inc.
          > > > http://www.tangosol.com
          > > > +1.617.623.5782
          > > > WebLogic Consulting Available
          > > >
          > > >
          > > > "Don Ferguson" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > Hi, comments in line.
          > > > >
          > > > > Gene Chuang wrote:
          > > > > >
          > > > > > Hi,
          > > > > >
          > > > > > I was looking at the cluster diagrams on the clustering page:
          > > > > >
          > > > > > http://www.weblogic.com/docs60/cluster/index.html
          > > > > >
          > > > > > And I can't help notice a slight descrepency between the diagram of
          > a
          > > > 2-Tier
          > > > > > cluster (WL web cluster + WL app cluster) vs.a 3-Tier cluster (web
          > > > > > proxy-plugin + WL web cluster + WL app cluster).
          > > > > >
          > > > > > In the 2-Tier diagram, the arrows going from the web nodes to the
          > app
          > > > nodes
          > > > > > converges to a single point, indicating that there's load balancing
          > of
          > > > > > servlet calls to ejbs.
          > > > > >
          > > > > > In the 3-Tier diagram, the arrows from each web node point directly
          > to
          > > > an
          > > > > > app node, which seems to indicate that there is a static one-to-one
          > > > > > relationship, hence no load-balancing.
          > > > >
          > > > > This is just an artifact of the drawing, not of the architecture. The
          > > > same
          > > > > load balancing would be performed between the web and app tiers
          > > regardless
          > > > > of whether or not there is a front end web server.
          > > > >
          > > > > > Below the 3-Tier diagram, one of the
          > > > > > described limitations of using standalone web server and proxy
          > > plug-ins
          > > > is:
          > > > > >
          > > > > > a.. Limited Load Balancing Options: When you use proxy plug-ins or
          > the
          > > > > > HttpClusterServlet to access clustered servlets, the load balancing
          > > > > > algorithm is limited to a simple round-robin strategy.
          > > > > >
          > > > > > I believe this is describe load balancing between the fire-wall and
          > > the
          > > > > > proxy web servers. But what about the load balancing between the WL
          > > web
          > > > > > servers and the app servers? Does it exist, or does one web server
          > > > always
          > > > > > assigned to one app server?
          > > > >
          > > > > This is not describing the load balancing between the firewall and the
          > > > > proxy web servers; we do not control of how that is performed. It is
          > > > > describing the load balancing between the proxy servers and the web
          > > tier.
          > > > > The diagram should really show that more clearly, as was done in the
          > > > 2-tier
          > > > > example.
          > > > >
          > > > > -Don
          > > > >
          > > > > >
          > > > > > --
          > > > > > Gene Chuang
          > > > > > Join Kiko.com!
          > > >
          > > >
          > >
          > >

Load Balancing And the Login Server

We have just added load balancing to our cluster of 30980 portal servers. The load balancing works only sporadically. We noticed a round-robin approach was taken in the configuration guides, which is not acceptable to our infrastructure team.
Questions: Is there a problem with using load balancers such as Resonate with Oracle portal? If not, should one machine in the cluster be specifically identified as the login server? Can they each act as login servers for any of the others?

I have had the same problem.
I think whoever programmed the logon routine at that point should be fired immediately and banned from programming for life! Logging on is a very basic and well-understood task, and programmed gozillions of times since 1940s. Common sense and unwritten rules of programming dictate simply if you make something case-sensitive, then you should accept an input in its original form (i.e. password in smalls, or whatever) but not change it to uppercase and then work case-sensitively. Either this, or you program everything case-insensitively.
Fire that programmer or give him to us gollumvoice

Best way for HTTP load balancing in OSB

Hi everybody,
We have setup an OSB cluster and we need to load balance HTTP requests across managed servers. Looking for info about load balancing in OSB I found that there are mainly two options: using a hardware load balancer or a software solution like Weblogic HttpClusterServlet. At the moment we have no hardware balancer available so we will have to take the software option. I found some articles about configuring HttpClusterServlet like http://redstack.wordpress.com/2010/12/20/using-weblogic-as-a-load-balancer.
But I have a question about this configuration. If we use a managed server as an HTTP proxy that balances requests between OSB managed servers, what would happen if this server goes down? I think one of the main goals of a clustered deployment is avoiding a single point of failure but with that setup all requests would depend on the availability of the proxy managed server.
Could you recommend us a setup for implementing load balancing in OSB?
Thank you in advance,
Daniel.

Load balancing in a cluster for http requests can be achieved using atleast 4 different ways:
(1)- use a hardware load balancer like F5 BigIP LTM
(2)- use a web server with weblogic plugin to frontend the cluster
(3)- use weblogic with HTTPClusterServlet
(4)- use DNS round robin - this works if you have managed servers running on 2 machines (say mach1, mach2) but on the same port. HTTP clients use hostname 'mach' to access the URL's and the dns does a round robin name resolution of mach to mach 1 and mach2 IP addresses..
All the options except (1) achieve only load balancing and not auto failover on all instances.. Hardware load balancers has the extra feature of probing [ sending periodic pings to the targets] , by which it can detect whether the target resource is alive and if not send the traffic to other nodes which are alive.. this is why hardware load balancers are worth their investment..
other options may work if client is coded to do retrying on failure.. so on 2nd or subsequent attempt, the routing is done to the machine which is alive..
For options (1),(2) and (3), you also need some redundancy of load balancing device ( web server, weblogic or hardware load balancer) to prevent single point of failure.. Hardware load balancers are usually deployed in redundant pairs to achieve this..
Edited by: atheek1 on 22/11/2011 15:31

Load-Balancing with Coherence BackingMapListener, CacheStore etc?

Hi -
I am looking for advice on load-balancing across a cluster.
Currently we insert objects into a Coherence cluster. Each storage node also runs a CEP instance. BackingMapListeners detect Coherence insert events, and inject the rows into the local CEP instance. The first channel in the CEP has a large buffer to allow the BML to return quickly without blocking.
The CEP makes decisions about the events and emits these decisions as further events, which are merged back into the original data rows in Coherence (i.e. the primary data is updated with enrichments).
This works fine until I saturate the CEP with a very high message rate, faster than the CEP and downstream components can keep up with. At this point the buffer between the BackingMapListener and the CEP starts to fill up. Once it is full, the BackingMapListener blocks, waiting for the CEP to take an event from the front of the queue before it can insert the latest event to the back of the queue.
Once the BackingMapListener blocks, other updates to the cache are blocked - which means the downstream end of the CEP is deadlocked by the upstream end, which is waiting for the downstream end... Events move through at exactly one per minute, due to a timeout in the Coherence cache update.
I recognise that I could (and probably should) copy the primary data into a separate cache as I merge the updates into it, to break this deadlock. But I wondered if anyone has used other mechanisms for load-balancing using Coherence partitioning, apart from the BackingMapListener.
I looked at CacheStore, which seems tailor-made for this as it includes queuing and doesn't block other cache actions (although if it blocks for too long the guardian will kill it). The problem I have with CacheStore is that I can't distinguish between inserts (CEP event injection required) and updates (no CEP event required).
I tried using BinaryEntryStore, where I can test BinaryEntry.getOriginalBinaryValue() for nulll to distinguish between inserts and updates, but I can't wire this into the cache using the Spring XML schema.
Are there any other established patterns for this apart from breaking up the inserts and updates into separate caches?
-thanks, Barney

The Cisco 526 Wireless Express Mobility Controller can be used with up to six access points per controller. So 5 -6 access point would be a better option . Refer URL
http://www.cisco.com/en/US/products/ps7320/products_data_sheet0900aecd8060c22b.html

Load Balancing and WLS primary server offset

I've got a load balancer in front of my WLS cluster, and I'm trying to
          set up load balancing based on WLS clustering. What I need to know to
          do this is the offset within the cookie that's responsible for
          determining which machine within the cluster to direct to.
          Any idea how I can get this information?
          thanks,
          cfraser


Chris Fraser wrote:
          > The proxy/plug-in solution sounds pretty cool, but I've got a high speed
          > Alteon Load Balancer already set up. I would prefer to use that as the load
          > balancer to the WL cluster rather than pay to bring another WLS online to do
          > pretty much what the load balancer, that I already own, can do. I know that
          > going this route means that we're probably not going to be able to do things
          > like failover to the secondary when the primary dies, but we will be able to
          > load balance and also have the ability to dynamically add/delete servers
          > from the list of available servers as they are brought up/down.
          In Memory session replication doesn't work without our plugins. I will have to
          do little bit of investigation to figure out if other persistence mechanism's
          would work without our plugins if you are interested in them. I have to remind
          you though that other types of persistence mechanism's we support are slower
          compared to in memory session replication.
          > Are there any plans to work with an Alteon or a Foundry to have their Load
          > Balancers act as the front end to a WLS cluster?
          Currently none. We are taking steps to make the plugin's and cluster more
          robust, we currently don't have any plans to work with other 3rd party vendors.
          > For us it would be ideal, because we wouldn't have to support another piece of
          > software, we would just
          > have to support the hardware based Alteon, which can handle thousands of
          > transactions per second.
          > I understand that the primary and secondary server information is available
          > in the sessionID, I'm just not quite sure how to extract it.
          This information is saved in the cookie. But I wouldn't count that, as we
          have plans to change this. I cannot give your more details.
          > Is there a particular offset within the session ID where it can always be
          > found?
          I don't quite get what you mean here.
          Hope this helps.
          - Prasad
          > thanks for the help,
          > cfraser
          > ----------
          > C h r i s t o p h e r A . F r a s e r
          > Director, Technology
          > macroplay.com, Inc.
          > [email protected]
          >
          > Viresh Garg wrote:
          >
          > > You should be using
          > > -- NES +NSAPI Plugin
          > > -- IIS + ISAPI Plugin
          > > -- WEblogic server acting as proxy
          > > -- Apache +Apache Plugin ( only in Denali)
          > >
          > > front-ending your Weblogic cluster
          > >
          > > These proxies/plug-ins are smart to do a lot of things like:
          > >
          > > -- Load balancing in weblogic cluster
          > > -- Adding/deleting servers dynamically in cluster when the servers
          > > join/leave Weblogic cluster
          > > -- failover to secondary when primary dies.
          > >
          > > As far as the information about primary and secondary is concerned it is
          > > available in session ID.
          > >
          > > --Viresh Garg
          > >
          > > Chris Fraser wrote:
          > >
          > > > I've got a load balancer in front of my WLS cluster, and I'm trying to
          > > > set up load balancing based on WLS clustering. What I need to know to
          > > > do this is the offset within the cookie that's responsible for
          > > > determining which machine within the cluster to direct to.
          > > >
          > > > Any idea how I can get this information?
          > > >
          > > > thanks,
          > > > cfraser

How to divide equal load in Oracle Weblogic Cluster Node

Hello Friends..
I install Oracle weblogic 10.3.3.0 and oracle Forms [32 Bit] Version 11.1.1.3.0 (Production) on Two PC, PC-1 and PC-2.
I Create a cluster for load balancing and shifting the load from PC-1 to PC-2. Now I want to know which algorithm is best for equal load balance means i want to transfer equal load on both machine.
If PC-1 have 10 http request then next 10 request transfer to PC-2.
Please guide me.
Thanks,
Sachin

Hi Sachin
You need to have a load balancer or web server in front of your weblogic server cluster.
This is really a tunning excersise, so you need to try several options depending on the load of the enironment, however robin robin (default) should work for you.
You can see more details here:
Load Balancing in a Cluster
Best Regards
Luz

Portal Drive not working with external load balancer

Hi,
We have a portal cluster and we are using external Load balancer from
Juniper for load balancing the portal cluster. When given the direct
portal URL (Central instance URL or Dialog instance URL), Portal Drive
is able to connect to portal and shows the KM documents properly. But
when given the Load balancer URL, it gives error saying "Can
not connect to host using WebDAV protocol". Load balancer URL works
fine from the browser without any problems. Any help is highly appreciated.
Helpful points will be rewarded.
Regards,
Chandra

Hi Steve,
For Portal Drive, Windows integrated authentication, client certificates,basic authentication and Kerberos is supported.
(in the default delivery of com.sap.km.cm.docs iview the authentication Scheme is set to basicauthentication - switching that to form based authenticationis not being supportedbywebdav clients).
ALso now Integrated Windows Authentication (NTLM) has been made available with latest patch.
Also read through SAP NOTE 1084683 for further clarifications.
Regards,
Shailesh

EJB - Load Balancing in GlassFish cluster

Similar Messages

Maybe you are looking for