QuestionQ103

VerifiedDeploy and Administer Applications

An administrator configured database session persistence for an application deployed to a WebSphere Application Server ND cluster. Application users have begun reporting data loss in HTTP session objects. How can the administrator resolve the issue with database session persistence?

Explanation

A single-row session schema imposes a per-session data limit. Enabling the multi-row schema stores session attributes in separate database rows, supporting larger session data. Switching schemas requires the existing session table to be dropped and recreated (or its rows cleared) so it matches the multi-row layout.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!