Hello Victor,
looks like you are having a problem with the request failover here. Can you provide some information about the architecture of your environment? How do you access the application? As you have six JVMs I assume you are running a cluster of WebSphere Application Server servers which are accessed via a cluster of HTTP servers running the WAS Plugin. Is that correct? Did you update the plug-cfg.xml so that the plugin is aware of all cluster members? Can the plugin access all servers via the respective transport ports?
------------------------------
Hermann Huebler
#IBMChampion
------------------------------
Original Message:
Sent: Wed July 24, 2019 10:59 PM
From: Victor Amrich
Subject: WebSphere 8.0.0.13 database session persistence problem
Hi, i am new sending to the IBM community, this is my first time.
I comment the error that i have using session persistence with database. The environment that i have is a cluster with 6 jvm server, Is running one application that is for test, a simple jsp file that set and get session atributes.
The database persistence session i had configured in application configuration inside WebSphere console. The database is a Oracle instance with the schema:
CREATE TABLE SESSIONS ( ID VARCHAR(128) NOT NULL , PROPID VARCHAR(128) NOT NULL , APPNAME VARCHAR(128) NOT NULL, LISTENERCNT SMALLINT , LASTACCESS INTEGER, CREATIONTIME INTEGER, MAXINACTIVETIME INTEGER , USERNAME VARCHAR(256) , SMALL RAW(2000), MEDIUM LONG RAW , LARGE RAW(1) )
All is ok, the session is saved in databace with their atributes, but if i shutdown the jvm instance that is procesing my resquest it gives me error 500, that an internal server error was produced. If i start the instance i recover the session.
At the moment that i shutdown the instance i see that the cookie do not change the clonid. If i change manually the clonid setting for example :-1 the request goes correctly to another member of the cluster.
Does anyone know what i am missing?
Many Thanks!
Victor