Hardware Load Balancers and Cluster WebLogic Proxy Plug-in setting

Documentation states that we need to enable the Cluster WebLogic Proxy Plug-in setting when there is a proxy plugin or HttpClusterServlet configured.
We used to have Weblogic Proxy plugin and the setting is still there, also the proxy was replaced by the hardware loadbalancer. Everything works normally and no one complained, but I would assume that WebLogic Proxy Plug-in setting should not be applicable any longer.
Is it possibly harmful to have that setting there? Does it mean that the loadbalancer emulates WebLogic Proxy Plug-in and also need this set?
Thank you

The Weblogic Proxy Plug-in Enabled flag only affects the behavior of a WL proxy module (such as if you were using Apache to proxy to WL via the mod_wl.so module). The value controls what IP address is returned when you call request.getRemoteAddr() from your application. If not enabled, you will get the IP address of the web server that proxied the request. If enabled, you will get the remote client IP address (instead of the proxy IP address) facilitated by the WL-Proxy-Client-IP header. If you are no longer using a plug-in module, the setting will have no affect. Hope this helps...

Similar Messages

Load balancing and cluster

Please help on this,
Steps I have created
1. Install Portal on node A
2. Create j2ee cluster instance on node B pointing to node A
3. Software load balance both the nodes
Even after load balancing the two portal nodes,if I shutdown Portal node A dispatcher,then the portal node B dispatcher will automatically shutdown, since the portal node B is a j2ee cluster for Portal node A.In this case how the URL will work from node B ? Please explain

I did portal install on server A. I started dispatcher and I am logging with the URL http://ServerA:52100/irj on server A. And I did install of J2EE cluster on another server called ServerB. I started Server B's dispatcher. When I am starting Server B's dispatcher in Server A I am able to see another time Element joined.The URL for the serverB is http://ServerB:52100/irj. When I created users on Server A, I am able to see the users on Server B.When server B goes down or if dispatcher of B stopped even then Server A is working because it is independent install. But when the Server A goes down which is the main server then the additional J2EE cluster node that is Server B is going down automatically because it is dependent on Server A. But I want to make it as complete high availability of failover,means if Server A goes down it should fail over to Server B and if Server B goes down it should fail over to Server A. I understood we can do software load balancing from windows level or hardware load balancing to get the high availability. But now with my existing installs, I want to make failover to work, please suggest me which is the best way to do without changing any of the existing installs.
My environment is :
Operating system: Windows 2003 Enterprise Edition
Data base: SQL 2000(Already configured as cluster)
Portal: EP6.0 SP2

HT1338 Why does it say plug in out of date? I down load Adobe and it stills says plug in needed

Cant figure out how to unblock my plug ins. No videos wont play

You need Adobe Flash Player?
http://get.adobe.com/flashplayer/

Load balancer vs. proxy plug-in

 Using WebLogic 6.1 SP2, the proxy plug-in handles the logic of connecting to
 the secondary server (stored in a cookie) if the primary is down. How does
 this work if you use a hardware load balancer in place of the proxy
 plug-ins?


More info at http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902 and
 http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902.
 Kumar Allamraju wrote:
 > Hi:
 >
 > yeah this was a problem in 5.1
 > We relaxed this restriction in 6.x release. This is the main reason WLS
 > clustering will now
 > work with hardware load balancers.
 >
 > Starting from 6.x, any server can become a primary server when failover
 > happens.
 > For e.g. if S1 and S2 are primary & secondary servers for client1 and when
 > the HW LD detects
 > that the primary is down, it will route the request to any of the servers
 > (can be S3, S4, S5) in the cluster
 > and that server(e.g. S3) will become the primary server for this
 > request(i.e. client1) and get this client's session data
 > from S2. At this point S3 become primary and S3 will nominate another server
 > (e.g. S4) as a secondary server
 > (based on the replication groups, if any)
 > We will only do this for active clients. For e.g if client2 doesn't make a
 > request when S1 is down, we don't try to
 > get it's data and chose a new secondary for him. This is called lazy
 > initialization/replication.
 >
 > Hope it helps.
 >
 > --
 > Kumar
 > "Joe" <[email protected]> wrote in message news:[email protected]...
 > >
 > > Using WebLogic 6.1 SP2, the proxy plug-in handles the logic of connecting
 > to
 > > the secondary server (stored in a cookie) if the primary is down. How
 > does
 > > this work if you use a hardware load balancer in place of the proxy
 > > plug-ins?
 > >
 > >
 > >
 > >
 Rajesh Mirchandani
 Developer Relations Engineer
 BEA Support

Site Resilience and Multi Role Servers without Load Balancers

I am designing an Exchange 2013 Site Resilient Scenario with two Multi Role Exchange Servers per Site. There are Two Sites.
This is a small organization, 400 users and all must be virtualized. A single forest, Two Sites 50/50
users each Site. There is a third Site for Witness Server collocation.
Our goal is to have redundancy per individual Site and Site Resiliency. Multi Role or Dedicated CAS it's my question. I don't have load balancer, budget is a key factor. If dedicated CAS was chosen, we would have eight exchange servers total.
My dream design is precisely two multi Role Servers per Site, four total. One DAG stretched across both sites. One third site for witness folder collocation.
Zero load balancers and my understanding is that ‘Single Global Namespace Support’ , Round Robin and one stretched DAG in Exchange 2013 will do the magic and it'll keep connected users even when local datacenter is down (Further manual DNS changes would
be obviously necessary after the crash to avoid sporadic connectivity loss).
My question is:
1. Will
be all my goals accomplished deploying only four Exchange Multi Role servers (Two per Site) in these locations? Or having dedicated CAS would make a difference?
2. Even I don't want load balancer (NLB or virtual-hardware load balancer). Is this a must?
3. In this scenario I pretend to use nothing but Standard versions of Exchange 2013 and Standard versions of Windows 2012/R2. Is there any reason why having Enterprise Edition would improve or validate my design?
Thanks for your help.
This is the scenario

Ya Standard edition now does clustering. The only difference with datacenter is the number of VMs you are licensed for under Hyper-V.
As for load balancing/HA, we set up a generic cluster resource ip/dns name and use that to point exchange clients to. Technically this is not a supported scenario from Microsoft, but we have been using it since 2010 and know of a ton of other people
doing it as well. It's kind of the unofficial poor man's HA. No load balancing, but with our load (and yours) it doesn't matter that only one server at a time is handling CAS. Works great and automatically fails over if you reboot the active
node. You can of course still split the active databases out across multiple nodes.

Load balancers with web servers & policy agents

I have a pair of host machines, hostA and hostB, running multiple web server instances, portalA, portalB, contentA, contentB, serviceA, serviceB, etc.
The two hosts, hostA and hostB, are sitting behind load balancers. ServiceA and serviceB must be protected by login and I have a policy agent installed on hostA and hostB for these two instances.
The load balancers respond to https://service/* and forward requests to http://serviceA:3456/* or http://serviceB:3456/* depending on the host selected by round-robin.
I've been told that serviceA and serviceB cannot be running on the default 443 port (although we could enable SSL if we wanted) in order to work nicely with the other web server instances that are behind the load balancers.
The problem is that the policy agent knows that it is running as http://serviceA:3456/.
The user makes a request to the load balancers for:
https://service/protected.html
The load balancer passes the request to:
http://serviceA:3456/protected.html
The agent sends a redirect to login which sends the user to:
http://service:3456/protected.html
This final URL is not available through the load balancers and it's obviously not the public URL.
I have fqdnDefault set to 'service.x.x' so the URL is rewritten to that extent. Is there a way to tell the agent that the port it's running on is not the public port (ie. that it's behind a NAT device)? Is there a way to tell the agent that it's should actually redirect to https and not http?

Hi,
CQ authoring does not leverage server side sessions, therefor you'll never loose data because of this.
But: As the cluster has a small delay on synchronisation, it could be, that on a write and subsequent read you'll get the old content, if you don't have sticky sessions (because both requests are not processed by the same server). Therefor I advise you to use sticky sessions in front of a CQ authoring cluster.
Jörg

Outlook client behaviour with load balancers when moving DB

Hi there,
My setup is 3 mailbox servers in a CAS array. I use hardware load balancers pointing outlook clients at the CAS array (mail.company.com). I am doing some maintenance which is involving moving certain DBs to different drives. I dismount the DB and change
the DB path to begin the move. When I do this within minutes of starting the maintenance, our hardware load balancers get almost flooded to capacity with client connections. We need to understand exactly what is happening here. My guess is that as the
DB is offline, the clients just sit there and attempt to constantly reconnect. We have hundreds of thousands of available connections which get saturated almost instantly.
Why do the clients attempt so many connections? Can this be prevented? I also dont understand why the load balancers arent keeping the connections open for longer so each time a client reconnects it just uses the same already open connection
Does anybody have any thoughts/advice/experience with this?
Thanks, Lamby.

Hi,
Hardware load balancers continuously monitor the load on the server and try to distribute the load evenly. Load balancing ensures that the load on your Client Access server is evenly distributed, not based on the database level. If one CAS server fails,
Outlook would still access database. However, if one database is offline, Outlook client would continue to connect to the same RPC Client Access Server array to access database, even though this database is failed.
If you want to keep the high availability for database level, you can deploy a DAG.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Load balancing and Application Server

Hi guys,
IHAC who have EBS + Kofax + OUCM (Oracle UCM) and needs to purchase load balancers for the installations. He is between Cisco and Radware load balancers and he says that Radware's ones have a module for Oracle Applications.
Do yo have any idea/experience/recommendation/advice with these load balancers?
Any help will be appreciated,
Dani

I'm pretty sure F5 Networks has the most comprehensive scope to support Oracle AS environments with Oracle health monitors, Advanced LB Algorythms and methods, SSL Offload and Acceleration, Web Acceleration, Sticky Persistence, URL URI rewriting and loopbacks... Please check out the following F5 and Oracle Deployment guides for complete configuration and deployment support.
http://www.f5.com/pdf/deployment-guides/f5-oracle10g-dg.pdf
and
http://www.oracle.com/technology/products/ias/hi_av/BigIP.pdf

Apache and cluster and failover

 Hi All,
 I have a quick question. I am running 2 WLS 5.1 sp6 app servers
 in clustered mode (on solaris 7) using Apache 1.3.12 (also Solaris),
 and the weblogic proxy. Everything is working fine, and failover
 works correctly if one of the servers crashes.
 My problem is when the primary server for a session is correctly
 shut down. In my environment failover does not work in this situation.
 In the case that the server is shut down correctly, should failover
 occur? I would think that all sessions that are on the server
 being shut down would be transferred to the secondary server...
 is this a bug in weblogic? Or am I just wrong?
 Thanks again


 "Cameron Purdy" <[email protected]> wrote:
 >Some OS's combined with some WL releases will failover
 >on graceful
 >shut-down. Sometimes you just have to kill -9 or close
 >the port to get
 >failover to work.
 >
 >--That is very good information. Thank you. I do see the failover
 working correctly when I have 2 NT WLS app servers and a Solaris
 Apache web server. The problem occurs when I have 2 Solaris app
 servers and the Solaris Apache web server. does this sound familiar?
 >Cameron Purdy
 >Tangosol, Inc.
 >http://www.tangosol.com
 >+1.617.623.5782
 >WebLogic Consulting Available
 >
 >
 >"Nick Barbato" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Hi All,
 >>
 >> I have a quick question. I am running 2 WLS 5.1 sp6
 >app servers
 >> in clustered mode (on solaris 7) using Apache 1.3.12
 >(also Solaris),
 >> and the weblogic proxy. Everything is working fine,
 >and failover
 >> works correctly if one of the servers crashes.
 >>
 >> My problem is when the primary server for a session
 >is correctly
 >> shut down. In my environment failover does not work
 >in this situation.
 >> In the case that the server is shut down correctly,
 >should failover
 >> occur? I would think that all sessions that are on
 >the server
 >> being shut down would be transferred to the secondary
 >server...
 >> is this a bug in weblogic? Or am I just wrong?
 >>
 >> Thanks again
 >
 >

Reverse Proxy plug in and Load Balancer Plug in

Hi,
Can anyone please provide me with an example obj.conf file showing how to combine the reverse proxy plug-in and Load Balancer plug-in.
I would like to use the reverse proxy plug in to detect when static content is requested and provide this from the web server. Requests for dynamic content would then be forwarded to an Application server via the Load balancer plug-in. I have found plenty of documentation on how to configure these plug-in separately but nothing on how to combine the two.

smiking
reverse proxy plugin - its job is to forward the requests to another server for a specific task. you can use the webserver 7 . it does forward and limited load balancing (using round robin ) based on the number of servers you provide in the configuration. i would say this is a poor man's setup.
load balancer plugin - some app servers like sun java system app server or web logic provide this plugin so that you can effectively use the back end app server
with both these setup, you can <if> constructs to determine which requests need to be forwarded to the back end server.
I wonder, why do you need both - if both of them is designed to do the same thing.

WebLogic Server - Firewall between proxy and cluster causes errors

 Product Name and Version, including Service Pack (if any):
 =============================================
 Weblogic 5.1 , SP8
 Platform (OS Version)
 =================
 Windows 2000 server,
 JDK Version (if applicable)
 =====================
 Jdk1.2
 Detailed Problem Description
 ======================
 We have 2 weblogic servers in a cluser on two windows 2000 Servers
 , NT01 and NT02.The webservers are in a DMZ behind the firewall
 and there is a second firewall between the webserver and the weblogic
 servers.The webserver is a Linux box , running Apache 1.3.9 with
 the weblogic Plugin(LIN01).The per server weblogic.properties file
 has the weblogic.system.DNSName=LIN01.
 We still get errors on the console when we run our jsp/Servlet
 application.The errors are listed below.Could you please help us
 identify the problem
 Thanks,
 Gigen Thomas
 Error Message/Stack Trace
 =====================
 ed Mar 21 16:38:50 PST 2001: <ServletContext-General> Generated
 java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway.java
 Wed Mar 21 16:38:52 PST 2001: <ServletContext-General> Generated
 java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway_45_leftframe.java
 Wed Mar 21 16:39:41 PST 2001: <Cluster> Adding server -255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
 to cluster view
 Wed Mar 21 16:39:41 PST 2001:<E> <Kernel> ExecuteRequest failed.
 java.io.NotSerializableException: com.sun.mail.imap.IMAPStore
 at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:845)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
 at java.util.Hashtable.writeObject(Hashtable.java:738)
 at java.lang.reflect.Method.invoke(Native Method)
 at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1585)
 at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:907)
 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
 at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java:118)
 at weblogic.servlet.internal.session.ReplicatedSession.writeExternal(ReplicatedSession.java:74)
 at weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(WLObjectOutputStreamBase.java,
 Compiled Code)
 at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(WLObjectOutputStreamBase.java,
 Compiled Code)
 at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java,
 Compiled Code)
 at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(WLObjectOutputStreamBase.java,
 Compiled Code)
 at weblogic.rmi.extensions.AbstractOutputStream2.writeObject(AbstractOutputStream2.java:82)
 at weblogic.rmi.extensions.AbstractOutputStream.writeObject(AbstractOutputStream.java:83)
 at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:86)
 at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
 Compiled Code)
 at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
 Compiled Code)
 at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
 at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
 Code)
 --------------- nested within: ------------------
 weblogic.rmi.MarshalException: error marshalling arguments
 - with nested exception:
 [java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]
 at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:90)
 at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
 Compiled Code)
 at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
 Compiled Code)
 at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
 at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
 Code)
 --------------- nested within: ------------------
 weblogic.rmi.extensions.RemoteRuntimeException: Undeclared checked
 exception - with nested exception:
 [weblogic.rmi.MarshalException: error marshalling arguments
 - with nested exception:
 [java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]]
 at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:108)
 at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
 Compiled Code)
 at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
 Compiled Code)
 at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
 at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
 Code)
 Wed Mar 21 16:40:12 PST 2001: <ServletContext-General> Generated
 java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner.java
 Wed Mar 21 16:40:14 PST 2001: <ServletContext-General> Generated
 java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_mainframe.java
 Wed Mar 21 16:40:14 PST 2001: <ServletContext-General> Generated
 java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_leftframe.java
 Wed Mar 21 16:43:41 PST 2001: <RJVM> Signaling peer -255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
 gone: weblogic.rjvm.PeerGoneException:
 - with nested exception:
 [java.net.SocketException: Connection reset by peer]
 Wed Mar 21 16:44:28 PST 2001: <ServletContext-General> Generated
 java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_dtlogout.java


 Thanks Prasad.Your comments are very much appreciated !!!
 Prasad Peddada <[email protected]> wrote:
 >This has nothing to do with firewall.
 >
 >
 >You have a non serializable object com.sun.mail.imap.IMAPStore
 >in session.
 >
 >You cannot have non serializable objects in sessions when
 >you are using inmemory replication/file/jdbc persistence.
 >
 >-- Prasad
 >
 >Gigen Thomas wrote:
 >
 >> Product Name and Version, including Service Pack (if
 >any):
 >> =============================================
 >> Weblogic 5.1 , SP8
 >>
 >> Platform (OS Version)
 >> =================
 >> Windows 2000 server,
 >>
 >> JDK Version (if applicable)
 >> =====================
 >> Jdk1.2
 >>
 >> Detailed Problem Description
 >> ======================
 >> We have 2 weblogic servers in a cluser on two windows
 >2000 Servers
 >> , NT01 and NT02.The webservers are in a DMZ behind the
 >firewall
 >> and there is a second firewall between the webserver
 >and the weblogic
 >> servers.The webserver is a Linux box , running Apache
 >1.3.9 with
 >> the weblogic Plugin(LIN01).The per server weblogic.properties
 >file
 >> has the weblogic.system.DNSName=LIN01.
 >>
 >> We still get errors on the console when we run our jsp/Servlet
 >> application.The errors are listed below.Could you please
 >help us
 >> identify the problem
 >>
 >> Thanks,
 >> Gigen Thomas
 >>
 >> Error Message/Stack Trace
 >> =====================
 >> ed Mar 21 16:38:50 PST 2001: <ServletContext-General>
 >Generated
 >> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway.java
 >> Wed Mar 21 16:38:52 PST 2001: <ServletContext-General>
 >Generated
 >> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_driveway\_driveway_45_leftframe.java
 >> Wed Mar 21 16:39:41 PST 2001: <Cluster> Adding server
 >-255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
 >> to cluster view
 >> Wed Mar 21 16:39:41 PST 2001:<E> <Kernel> ExecuteRequest
 >failed.
 >> java.io.NotSerializableException: com.sun.mail.imap.IMAPStore
 >> at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:845)
 >> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
 >> at java.util.Hashtable.writeObject(Hashtable.java:738)
 >> at java.lang.reflect.Method.invoke(Native Method)
 >> at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1585)
 >> at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:907)
 >> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:342)
 >> at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java:118)
 >> at weblogic.servlet.internal.session.ReplicatedSession.writeExternal(ReplicatedSession.java:74)
 >> at weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(WLObjectOutputStreamBase.java,
 >> Compiled Code)
 >> at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(WLObjectOutputStreamBase.java,
 >> Compiled Code)
 >> at weblogic.common.internal.WLObjectOutputStreamBase.writeObject(WLObjectOutputStreamBase.java,
 >> Compiled Code)
 >> at weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(WLObjectOutputStreamBase.java,
 >> Compiled Code)
 >> at weblogic.rmi.extensions.AbstractOutputStream2.writeObject(AbstractOutputStream2.java:82)
 >> at weblogic.rmi.extensions.AbstractOutputStream.writeObject(AbstractOutputStream.java:83)
 >> at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:86)
 >> at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
 >> Compiled Code)
 >> at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
 >> Compiled Code)
 >> at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
 >> at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
 >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
 >Compiled
 >> Code)
 >>
 >> --------------- nested within: ------------------
 >> weblogic.rmi.MarshalException: error marshalling arguments
 >> - with nested exception:
 >> [java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]
 >> at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:90)
 >> at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
 >> Compiled Code)
 >> at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
 >> Compiled Code)
 >> at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
 >> at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
 >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
 >Compiled
 >> Code)
 >> --------------- nested within: ------------------
 >> weblogic.rmi.extensions.RemoteRuntimeException: Undeclared
 >checked
 >> exception - with nested exception:
 >> [weblogic.rmi.MarshalException: error marshalling arguments
 >> - with nested exception:
 >> [java.io.NotSerializableException: com.sun.mail.imap.IMAPStore]]
 >> at weblogic.cluster.replication.ReplicationManager_WLStub.create(ReplicationManager_WLStub.java:108)
 >> at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java,
 >> Compiled Code)
 >> at weblogic.cluster.replication.ReplicationManager.checkHosts(ReplicationManager.java,
 >> Compiled Code)
 >> at weblogic.cluster.replication.ReplicationManager.clusterMembersChanged(ReplicationManager.java:582)
 >> at weblogic.cluster.MemberStash$ClusterMembersChangeDeliverer.execute(MemberStash.java:207)
 >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
 >Compiled
 >> Code)
 >>
 >> Wed Mar 21 16:40:12 PST 2001: <ServletContext-General>
 >Generated
 >> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner.java
 >> Wed Mar 21 16:40:14 PST 2001: <ServletContext-General>
 >Generated
 >> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_mainframe.java
 >> Wed Mar 21 16:40:14 PST 2001: <ServletContext-General>
 >Generated
 >> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_partner\_partner_45_leftframe.java
 >> Wed Mar 21 16:43:41 PST 2001: <RJVM> Signaling peer
 >-255280969513470611S192.168.6.12:[7001,7001,7002,7002,7001,-1]
 >> gone: weblogic.rjvm.PeerGoneException:
 >> - with nested exception:
 >> [java.net.SocketException: Connection reset by peer]
 >> Wed Mar 21 16:44:28 PST 2001: <ServletContext-General>
 >Generated
 >> java file: E:\weblogic_cluster\FIPBEA01\classfiles\jsp_servlet\_dtlogout.java
 >

Proxy, Serverlet and Cluster

1. We plan to use ISS as proxy and route jsp request to a cluster of
 Serverlet/EJB. We will track session data in each server.
 Question : How do the ISS proxy know to route browser request to the server
 in cluster ?
 2. If we use Weblogic server without ISS to server static/dynamic pages. We
 have load balance router in front of Weblogic cluster.
 Question : How did load balance router know to route the request from
 browser to the server which track session data in the cluster ?
 Thanks in advance.
 Mickey Hsieh


 Comments inline.
 Jim Zhou
 "Mickey Hsieh" <[email protected]> wrote:
 >Thanks Jim
 >I had two follow up questions.
 >
 >Q: Can I put many IIS to server static page and Proxy ? then I put one
 >hardware LB in front of IIS Web farm ?
 Definitly. Ultimately you have 3 level of LB. First level is LB hardware (CISCO Load Director, for example) will route
 the traffic to a farm of IIS/Proxies, which serves only static contents (HTML, image). Second level is proxy will LB the servlet requests to WLS clustered
 servers. The third level is when servlet is calling EJB, it get load balanced if your EJBs are deployed in a
 different cluster than your presentation (servlet/JSP).
 >
 >
 >> For WLS 4.51 and 5.1, you load balance router can only be used to load
 >balanced HTTP reuqests to a
 >> farm of IIS servers. You can't have the router to load balance directly to
 >WLS cluster, because your load
 >> balance router will not read the cookie embeded in every HTTP request. But
 >that will be changed in WLS 6.0
 >Q: Is there any hardware LB can perform routing as well ?
 > If not, How WLS 6.0 take care routing without Proxy ?
 I don't think any hardware LB is designed to read BEA's propritory cookie to find out the primary server
 for it to route to. My understanding in WLS 6.0, BEA is promoting people to use WLS to serve both static
 and dynamic content. So IIS/Proxy is not needed any more. I am not an expert on LB hardware, I am also
 puzzled by how does hardware LB route all the HTTP request that belong to same session to one
 particular primary server, but I know how the failover situation get handled in WLS 6.0, LB hardware just
 choose another primary server based on its LB algorithm when the previous primary server goes down.
 The new primary server will recover the session data from secondary server ( it finds out the secondary by
 reading the cookie).
 >
 >
 >
 >
 >
 >"Jim Zhou" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Comments inline.
 >>
 >> Jim Zhou.
 >>
 >> "Mickey Hsieh" <[email protected]> wrote:
 >> >1. We plan to use ISS as proxy and route jsp request to a cluster of
 >> >Serverlet/EJB. We will track session data in each server.
 >> >Question : How do the ISS proxy know to route browser request to the
 >server
 >> >in cluster ?
 >> >
 >> When first HTTP request comes to IIS proxy, proxy will pick one server
 >in the cluster to serve the
 >> servlet reuqest. WebLogic servlet engine will put a cookie in the servlet
 >response. So next click from the
 >> browser client, proxy will examine the cookie, inside the cookie, BEA
 >embeded the primary server and
 >> secondary server that holds the HTTP session. So proxy will get the
 >primary server name from cookie,
 >> and relay the request to that WLS server in the cluster which holds the
 >session data. In case the primary
 >> server is down, proxy is smart enough to route the request to secondary
 >server, for that particular session,
 >> secondary server will change itself to primary server, and find another
 >live WLS instance in the cluster to be
 >> the secondary server for that session.
 >> Be aware that in WLS 6.0, servlet load balancing does not require
 >proxy to examine the cookie anymore.
 >> You can use hardware load balancing in front of WLS cluster. In the case
 >of failure, hardware LB will pick
 >> another primary server, the new primary server will examine the cookie,
 >find the secondary server, and
 >> replicate the session data from the secondary server. So in WLS 6.0, once
 >you are secondary server, you
 >> are always secondary server. Quite different than 4.51 and 5.1.
 >> In case browser does not support cookie, URL rewriting is used.
 >>
 >> >2. If we use Weblogic server without ISS to server static/dynamic pages.
 >We
 >> >have load balance router in front of Weblogic cluster.
 >> >Question : How did load balance router know to route the request from
 >> >browser to the server which track session data in the cluster ?
 >>
 >> For WLS 4.51 and 5.1, you load balance router can only be used to
 >load balanced HTTP reuqests to a
 >> farm of IIS servers. You can't have the router to load balance directly to
 >WLS cluster, because your load
 >> balance router will not read the cookie embeded in every HTTP request. But
 >that will be changed in WLS 6.0
 >>
 >> >
 >> >Thanks in advance.
 >> >
 >> >Mickey Hsieh
 >> >
 >> >
 >> >
 >>
 >
 >

WebLogicSession and X-WebLogic-Cluster-Hash cookies

 Hello, apologies up front if this has been posted before, I haven't
 been able to
 find any reference to it yet. First, how do I decode the
 WebLogicSession cookie
 between the HttpClusterSerlvet and the HTTP client to extract the IPs of the
 primary/backup cluster servers that have replicated my HTTP session?
 Second,
 how is the translation done between the WebLogicSession cookie
 (proxy<->client)
 and the X-WebLogic-Cluster-Hash (proxy<->cluster)?
 Thanks in advance for any responses,
 -Steven Vaughan


I'm not exactly sure what you are asking. Are you trying to configure a
 hardware load balancer or something like that in front of the proxy?
 If you take a look at the cookie information (you can do so online by using
 safe cookies at anonymizer.com for example) you will see the IP addresses
 embedded in the cookie data. Do you need to know exactly what the
 information/offsets there are in that data? Could you explain what you are
 trying to accomplish?
 Cameron Purdy
 Tangosol, Inc.
 http://www.tangosol.com
 +1.617.623.5782
 WebLogic Consulting Available
 "Steven Vaughan" <[email protected]> wrote in message
 news:[email protected]..
 >
 > Hello, apologies up front if this has been posted before, I haven't
 > been able to
 > find any reference to it yet. First, how do I decode the
 > WebLogicSession cookie
 > between the HttpClusterSerlvet and the HTTP client to extract the IPs of
 the
 > primary/backup cluster servers that have replicated my HTTP session?
 > Second,
 > how is the translation done between the WebLogicSession cookie
 > (proxy<->client)
 > and the X-WebLogic-Cluster-Hash (proxy<->cluster)?
 >
 > Thanks in advance for any responses,
 > -Steven Vaughan
 >

Error loading weblogic apache plug-in

HPUX11i
Apache 2.0.55
WebLogic 8.13
I am following the instructions on how to configure the Weblogic Apache plug-in:
http://e-docs.bea.com/wls/docs81/plugins/apache.html#119517
When I attempt to verify the syntax of the http.conf or attempt to start apache, I get the following error:
/usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage:
/usr/lib/libcl.2
/usr/lib/dld.sl: Exec format error
Syntax error on line 247 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/local/apache2/modules/mod_wl_20.so into server: Exec format error
Any ideas on how to fix this?
Thanks.

 We will be making a port of the plug-in in the future. You should contact
 your account manager who can supply the full details.
 Thanks,
 Michael Girdley
 WLS Product Manager
 Ken <kenw{noSpam]@lostwax.com> wrote in message
 news:8cej50$dsu$[email protected]..
 > I've just read about the WebLogic Apache plug-in that's new in 5.1 :-)
 >
 > Am I right to assume that this plug-in only works for Apache running on
 > Solaris? :-(
 >
 > I'm running Apache (Stronghold actually) on Linux and I need to use this
 to
 > proxy JSP request to my Weblogic Servers running on Solaris - any
 thoughts?
 >
 > Ken
 >
 >

Which cluster attribute should you modify to ensure that load balancing and

An EJB is targeted to a cluster. Remote EJB clients can therefore take advantage of WebLogic Server’s load balancing and failover capabilities.
However, a proxy server exists between the clients and cluster, which performs IP address transaction.
Which cluster attribute should you modify to ensure that load balancing and failover work correctly?
A. Multicast Address
B. Persistent Store
C. Cluster Address
D. Migration Basis
E. Replication Channel

http://docs.oracle.com/cd/E13222_01/wls/docs81/config_xml/Cluster.html
Cluster address

Hardware Load Balancers and Cluster WebLogic Proxy Plug-in setting

Similar Messages

Maybe you are looking for