One of the following symptoms might occur.
Both the adapter and CLM use the same JSESSIONID cookie in the HTTP session management. CLM sometimes resets the cookie when you log in to CLM, which causes the adapter to lose its session in some linking scenarios.
If you are running the HP adapter and one or more CLM applications in the same WebSphere® Application Server or the adapter is behind the same reverse proxy as CLM, you must provide a unique session management cookie for the HP adapter. For information about providing a unique session management cookie, see Changing the HTTP session management cookie name. You can verify your changes by using a web development tool (such as Firebug) to ensure that the cookie in use is not JSESSIONID.