Yes we did. ( that was also suggested by BMC) In the Websphere Admin Console, choose WebSphere Application Servers > serverName > Session management > Enable Cookies. Make sure that the path is set to the context root of the mid tier. To ensure that users can log in successfully, create a new NoAdditionalSessionInfo property: Choose WebSphere Application Servers > serverName > Web Container > Custom Properties. Create a new NoAdditionalSessionInfo property, and set it to true. Restart the IBM WebSphere server.
That didnot help. After that change, the issue seemed to disappear; then the next day, started testing - it reoccurred. We have done fiddler trace, wireshark capture, provided web.xml files for both MT and Websphere, logs, anything BMC asked; but still pending ... so hoping someone on the list can provide another hint (something we missed).. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
