1) Not Able To Connect Database? (Ping Is Working Fine and Database Is Up and Running) What Would Be Reasons?
1) Not Able To Connect Database? (Ping Is Working Fine and Database Is Up and Running) What Would Be Reasons?
Unicast:
Say you have three servers (MS-1,MS-2,MS-3) in a cluster now if they have
to communicate with each other they have to ping (i.e. heartbeats ) the
cluster master for informing him that he is alive.
If MS-1 is the master then MS-2 and MS-3 would send the ping to MS-1
Multicast:
Here there is no cluster master each server has to ping each other to
inform everyone that I am alive.
So MS-1 would send the ping to MS-2 & MS-3 same way MS-2 would send
the ping to MS-1 & MS-3 and MS-3 would ping MS-1 & MS-3.
Reaches the BIG-IP - Looks for the pool/rule - Forwards request to one of
the node in the pool
In latest WLS 12C version you can use the upgrade installer.
Shutdown the WLS process and backup the domain & product directory
whenever the request gets routed from any Load balancer or Web-server
to any application server, the routed request contains a header part which
includes information of the
server like Port, Listen address etc based on which it routes to its
appropriate server hosting application.
Debug ON
WLLogFile /tmp/weblogic.log
8) Two managed MS1, MS2 servers is there in a cluster. how can you
say that load is there on only one server?
go to deployment->your web application->Monitoring->workload- check the
session on each node