• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

How do stubs work in a WebLogic Server cluster?

by admin

When you create a domain with multiple Managed Servers, all those servers function independently of each other. A cluster, on the other hand, is a group of WebLogic Server instances that work as a single instance from the point of view of a client. The reason you use a cluster is to increase scalability and reliability by taking advantage of a cluster’s workload balancing and failover capabilities that you can’t have with a single server instance. You manage clustered server instances the same as any nonclustered instance. Of course, to avail yourself of the load-balancing and failover capabilities of a cluster, you must configure a few other things as well.

You use clusters to achieve two important goals: high availability and scalability. High availability includes support for both the failover of applications as well as the failure of a server or an essential service such as a JMS service. A cluster maintains copies of application components (objects), so if a component becomes unavailable, the cluster uses the failed object’s copy to complete the processing of the task. WebLogic Server uses session replication to fail over servlets and JSP. Similarly, it uses replica-aware stubs to maintain information about the state of application components such as EJBs and RMIs. Replication allows the copies of the failed objects to finish the job when an application component fails. WebLogic Server also provides for both automatic and manual migration of an entire clustered server instance to a different machine following a server failure. You can use this capability manually for administrative purposes as well.

Clients that connect to a WebLogic Server cluster and look up a clustered object obtain a replica-aware stub for the object. This stub contains the list of available server instances that host implementations of the object. The stub also contains the load-balancing logic for distributing the load among its host servers.

Filed Under: oracle, WebLogic

Some more articles you might also be interested in …

  1. Step By Step Guide To Create Physical Standby On Normal File System For ASM Primary using RMAN
  2. ORA-30012 Database Does Not Start With UNDO_MANAGEMENT=AUTO – Oracle Database 11gr2
  3. How to Recover From Lost or Missing Database Parameter Files (PFILE or SPFILE)
  4. How to Rename the Default JSESSIONID in WebLogic
  5. How To Find When The Spfile Was Created On Linux Server
  6. ORA-00214: control file inconsistent with file
  7. oracleasm Command Examples (Cheat Sheet)
  8. ORA-354 ORA-353 and ORA-312: Possible corruption in Online Redo Log File Members in a Redo Log Group
  9. Roles and Privileges Administration and Restrictions in Oracle Database
  10. Oracle SQL script to Show current Users and SQL being Executed

You May Also Like

Primary Sidebar

Recent Posts

  • grpck command – Remove corrupt or duplicate entries in the /etc/group and /etc/gshadow files.
  • xxd command – Expressed in hexadecimal form
  • sesearch: command not found
  • macof: command not found

© 2022 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright