Weblogic: Universal vs Source Address Persistence

With universal persistence, you can create a persistence record on anything you like, an example would be the jsessionid value in the cookie. But it could equally be anything the FT is able to read. This differs from cookie persistence as cookie persistence does not create a record in the persistence table, the information is stored in the cookie.

Comparing this to source address affinity, this also creates a persistence record like universal persistence however it is limited to just the source address. This could cause problems if the sources are all NAT'd behind a firewall, this may cause all connections to persist on the same pool member.

To answer your other question, if the pool member was down, connections would be load balanced to another server in the pool and a new persistence record is created