Session Persistence Problems

The following problems are addressed in this section:

• The create-session-store Command Failed

• Configuring Instance-Level Session Persistence Did Not Work

• Session Data Seems To Be Corrupted

The create-session-store Command Failed

Description

The asadmin create-session-store command cannot run across firewalls. Therefore, for the create-session-store command to work, the application server instance and the HADB must be on the same side of a firewall.

The create-session-store command communicates with the HADB and not with the application server instance.

Solution

Locate the HADB and the application server instance on the same side of a firewall.

Configuring Instance-Level Session Persistence Did Not Work

The application-level session persistence configuration always takes precedence over instance-level session persistence configuration. Even if you change the instance-level session persistence configuration after an application has been deployed, the settings for the application still override the settings for the application server instance.

Session Data Seems To Be Corrupted

Description

Session data may be corrupted if the system log reports errors under the following circumstances:

• During session persistence

• When the session state is read during session activation

• When the session state is read after session failover

  If the data has been corrupted, there are three possible solutions for bringing the session store back to a consistent state, as described below.

Solution 1

Use the asadmin clear-session-store command to clear the session store.

Solution 2

If clearing the session store does not work, reinitialize the data space on all the nodes and clear the data in the HADB using the hadbm clear command.

Solution 3

If clearing the HADB does not work, delete and then recreate the database.

For solutions 2 and 3, above, after clearing the HADB, recreate the session store to restablish the database schema.