WebLogic Cross-domain problem resolution under different ports in the same domain

Environment: The same server, the same WebLogic application, built two domains, two domain IPs, the port is different. A domain put Web application A, a put Web application B.

Action: When a user accesses a program, a program returns a link that allows the user to access B.

Problem: The session with a is lost when the user successfully accesses the link given by a

Workaround:

Build a weblogic.xml under the webinfo of A or B and add the following configuration:
The problem is resolved by following the settings in Weblogic.xml.

[HTML]View PlainCopy

2. <session-descriptor>
4. <session-param>
6. <param-name>cookiename</param-name>
8. <param-value>ts</param-value>
10. </session-param>
12. </session-descriptor>

"Problem Analysis"
The same server ServerName = Server01, the same weblogic, established two Domain,domain01 (port-8018) and DOMAIN02 (port-8008) respectively, Deploy the app App1 in Domain01, deploy the app App2 in Domain02, and start the two domain, and if it's completely the default configuration, it's no problem to access two apps separately. However, if the same client accesses App1 and then accesses APP2, it will find that the APP1 session is missing.
When the client accesses App1, Domain01 retains a cookie named Jsessionid on the client, records the DOMAIN01 information, jsessionid the default value of WebLogic Cookie-name, When the same client accesses APP2, the Jsessionid value in the client cookie is Domain02 refreshed, and if you continue to access App1 in the previously opened IE, the session is lost (Jsessionid has been Domain02 refreshed!). )。

WebLogic Cross-domain problem resolution under different ports in the same domain