HADB session failover & realm problem

I have a enterprise applicaiton server cluster configured for loadbalancing and session failover.
I installed HADB.
HADB works, I test with the webapp from the samples of the application server:
I add some attribute in session, I see which node executed the request, I stop the node.
The other requesto go to the other node and the session is reloaded as it was on the stopped node.
The problem I have is with app with realms authentication.
I can login without problem on the first node.
I stop the server handling the request and when switched to the other server I have to login again if I request a realm protected URL again.
Any suggestion?
Thanks in advance.

Solved
on Cluster configuration (in the tree of admin apps of application server):
my-clu-config -->
   Availability Service -->
        Web Container Availability -->
                  Single-Sign-On State: Enabled.

Similar Messages

Session-failover-enabled not working in iWS6 with a FileStore

I'm trying to use a FileStore to implement session persistence using IWSSessionManager. I have the following in my web-apps.xml:
<web-app uri="/Banking" dir="c:/java/online">
<session-manager class='com.iplanet.server.http.session.IWSSessionManager'>
<init-param>
<param-name>session-data-store</param-name>
<param-value>com.iplanet.server.http.session.FileStore</param-value>
</init-param>
<init-param>
<param-name>session-data-dir</param-name>
<param-value>c:/iplanet/servers/SessionData</param-value>
</init-param>
<init-param>
<param-name>session-failover-enabled</param-name>
<param-value>false</param-value>
</init-param>
</session-manager>
</web-app>
I'm seeing the following exception in my log:
[12/Jun/2002:10:10:56] info ( 320): java.io.NotSerializableException: com.iplanet.server.http.servlet.WebApplication
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.util.Hashtable.writeObject(Hashtable.java:764)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at com.iplanet.server.http.session.IWSHttpSession.writeObject(IWSHttpSession.java:764)
at java.lang.reflect.Method.invoke(Native Method)
at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at com.iplanet.server.http.session.FileStore.save(FileStore.java:167)
at com.iplanet.server.http.session.IWSSessionManager.update(IWSSessionManager.java:499)
at com.iplanet.server.http.servlet.NSHttpServletRequest.closeInputStream (NSHttpServletRequest.java:612)
at com.iplanet.server.http.servlet.NSServletRunner.servicePostProcess(NSServletRunner.java:857)
at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:942)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
at com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
Any ideas what's wrong?
I should note that I don't think it is because I am storing non-serializable things in the session attributes. I think this because originally I was getting an exception that said that a specific attribute wasn't serializable. I changed the class definition of the class I was storing in that attribute to include "implements java.io.Serializable" and that problem went away.

Hi Sija,
Can i have detailed scenario in your cluster configuration.
Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
Regards
Nick Loy

Access Manager 7.1 Session Failover

Hello,
I am trying to do a session failover with access Manager 7.1.
My Infrastructure:
OS: Solaris 10
2 Solaris Servers dedicated to 4 LDAP instances (2 each)
2 Solaris Servers dedicated to 2 LDAP Proxy servers configured to access 4 LDAP instances.
2 Solaris Servers dedicated to 2 Sun Application Server 8.2 running 2 instances of Access Manager sharing the 4 LDAP instances through Proxy.
2 Solaris Servers dedicated to 2 instances of JMS servers (1 on each) with Access Manager Session DB configured. JMS is running on cluster mode.
1 Solaris server for Webserver 7.0 configured for Load Balancing (loadbalancer.xml).
Configuration:
2 instances of Access Manager on separate solaris boxes use the same LDAP instance(s).
Access Manager is configured for session failover using amsfoconfig as documented.
The Session failover instances where started as documented
1.     Start session DB using amsfo script
2.     Start the Access Manager instances (by Starting DAS)
3.     Start Webserver
My Problem:
Session Failover does not work. The Amsession log throws
ERROR: JMQSessionRepository.save(): failed to save Session
java.lang.NullPointerException
at com.iplanet.dpro.session.jmqdb.PersistSession.setString(PersistSession.java:310)
at com.iplanet.dpro.session.jmqdb.JMQSessionRepository.save(JMQSessionRepository.java:357)
at com.iplanet.dpro.session.service.SessionService.saveForFailover(SessionService.java:2812)
AmSessionMonitor file continuously throws below error and fills up the disk (20 GB ) space quickly:
04/24/2007 04:28:13:450 PM EDT: Thread[amSessionMonitor,5,main]
WARNING: SessionMonitor runtime exception
java.lang.NullPointerException
at com.iplanet.dpro.session.service.SessionService.locateCurrentHostServer(SessionService.java:1762)
at com.iplanet.dpro.session.service.SessionService.getCurrentHostServer(SessionService.java:1731)
at com.iplanet.dpro.session.service.SessionMonitor.run(SessionMonitor.java:94)
JMS queue Log:
Sun Java(tm) System Message Queue 3.7
Sun Microsystems, Inc.
Version: 3.7 UR1 (Build 9-b)
Compile: Sun Jun 18 22:11:21 PDT 2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_09 Sun Microsystems Inc. /usr/jdk/instances/jdk1.5.0/jre
[18/Apr/2007:09:14:28 EDT] License: Sun Java(tm) System Message Queue 3.7 UR1 Enterprise Edition
[18/Apr/2007:09:14:29 EDT] IMQ_HOME=/
"log.txt" 725 lines, 61600 characters
Magic/Version: 469754818/301 Size: 116 Type: ACKNOWLEDGE(24)
Expiration: 0 Timestamp: 1177446120954
Source IP: 172.31.120.44(c0:ca:66:ec:a9:d5) Port: 60437 Sequence: 32
Property Offset: 76 Property Size: 0
Encryption: 0 Priority: 5
Flags: consumerID: 0
TransactionID: 0
MessageID: 32-172.31.120.44(c0:ca:66:ec:a9:d5)-60437-1177446120954
Properties: null
Message Body: 40 bytes [3052053123717449216:16-172.31.120.44(b1:6a:3:39:7d:6)-60434-1177446116385]
Internal Buffers (useDirect=false):
Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
com.sun.messaging.jmq.jmsserver.util.BrokerException: Internal Error: Unable to complete processing acks: Unknown consumer [consumer:30520
53123717449216, type=NONE]
at com.sun.messaging.jmq.jmsserver.data.handlers.AckHandler.handleAcks(AckHandler.java:256)
at com.sun.messaging.jmq.jmsserver.data.handlers.AckHandler.handle(AckHandler.java:166)
at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:146)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.readData(IMQConnection.java:1856)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:816)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:141)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:459)
at java.lang.Thread.run(Thread.java:595)
[24/Apr/2007:16:22:05 EDT] [B1071]: Established cluster connection : testuidp02.dol.state.nj.us/172.31.120.45:7676 (aminstance)
[24/Apr/2007:16:23:00 EDT] [B1066]: Closing: [email protected]:57590->jms:60425 because "[B0061]: Client exited without closing con
nections". Count=1
[24/Apr/2007:16:24:37 EDT] [B1065]: Accepting: [email protected]:42435->jms:60425. Count=2
[24/Apr/2007:16:26:15 EDT] [B1066]: Closing: [email protected]:42435->jms:60425 because "[B0061]: Client exited without closing con
nections". Count=1
Access Manager via load balancer web server works fine with out session failover configuration.
I noticed through forums that Accessmanager 2005Q4 had similar problem and was fixed with a patch.
Will somebody please help who has done session failover with AM7.1?
Thanks
Kris

Yep, that was me struggling with 2005Q4 before they released a patch (120954-03 if I am not mistaken).
1. Have you configured your AM installation as a site?
2. Have you added a secondary configuration in the session tab?
A restart will be required after that. Try setting log levels to debug. When AM webserver comes up and brings the application live, you'll see information regarding the secondary configuration, and whether things are actually in place or not.
Hope this helps.
Ankush
http://www.iamcg.net

Sun access Manager session failover

Hi,
I am trying to install Sun Access Manager (2005Q1) with Session failover. I have hardware load balancer under which i have configuring Access Manager on two seperate boxes.
For session failover i have configured Berkelay database on both system but am unable to start the database.
Now i got the information that Access Manager 6.1 does not support session failover.
Can anyone confirm if access manager 6.1 supports failover or we need to upgrade it?
Thx in advance.
ASN
Message was edited by:
asn123

One clarification. AM 6.1 did have session failvoer feature. But it was container dependent. It used container features to provide this. Each container had its on configuration. It was made independent of the containers in AM 6.3 release. I would stonglry recommend using AM 6.3 or above if you are using session failover.
shivaram

Sun Access Manager 2005Q1 session failover is not working

Hi All
I m using Sun access manager 2005Q1,message queue 2005Q1, Sun Directory server 5.2 ,BerkelyDb 4.2.52 and radware hardware load balancer with sticky session.
I m have configured message queue and BerkeleyDB and both are running with any error.
I m using http://docs.sun.com/source/817-7644/ch5_scenarios.html#wp41008 doc for session failover.
Simple failover is working fine but the Session failover is not working.
Any body has done session failover with Sun Access manager 2005 Q1 I m trying to resolve this issue last two month.
Please it is urgent.

It works fine in 2005Q4, after applying a patch 120954 if I am not mistaken. But 2005Q4 and 2005Q1 are probably different in terms of session failover (site configuration etc.)
1. Stop both AM servers
2. Set logging to debug mode in AMConfig.properties.
3. Delete / move everything in /var/opt/SUNWam/debug
4. tail -f /var/opt/SUNWam/debug/amSession
5. Post that file here... you should be able to see if session failover is enabled etc....
hope this helps.

Session Failover and Clustering

 Let's say that we have two WebServers (NES) with the weblogic plugin (say WS1 and WS2) and a cluster with two WebLogicCommerce AppServers (say AS1 and AS2). Let's assume that each WebServer and AppServer runs on its own machine (total: 4 machines). Now, let's assume that the WebServer "obj.conf" files (on both WS1 and WS2) are setup so that they point to the servers in the cluster (WebLogicCluster="AS1:7601,AS2:7601").
 When a new request comes in to one of the WebServers (say WS1), the plugin will route it to one of the AppServers using Round-Robin (say AS1). A session will now be initiated in AS1 and it sends a response back to the client.
 Question 1: How does the other proxy in WS2 know that all future requests for this client need to be forwarded to AS1?
 Question 2: For failover, does the cluster automatically replicate the session state existing in AS1 onto AS2 before sending the response (does AS2 automatically become the secondary)?
 Now let's assume that AS1 crashes/dies. When the next request from the client comes to WS1 or WS2, they will forward it to AS1 (assuming that WS2 knows about the client session in AS1) . Since AS1 has crashed, will the client eventually get a timeout error message?
 Question 3: To ensure that the session failover happens so that AS2 gets the request instead (becomes the primary), do we need to setup a WebLogic Proxy Server? If so, why can't the plugins for NES provide the failover themselves?
 Thank you very much for your help!
 Giri


 Thank you very much for your responses. It has been very helpful and I am clear on the session/clustering stuff. I have new questions on EJB and clustering which I will post as a separate thread.
 Giri
 "Jason Rosenberg" <[email protected]> wrote:
 >And also, if the browser has cookies disabled, it is important for
 >the app server to embed the WebLogicSession info via url rewriting,
 >otherwise the proxy or NES will not be able to route the session
 >properly.
 >
 >So, in all http responses, be sure to pass the url string through
 >response.encodeURL(). This will do the right thing depending
 >on whether cookies are enabled or not.
 >
 >I've just only recently figured this out. Haven't actually tried it
 >all out yet, so forgive me if it is not quite this simple, but this
 >seems to be the gist of it...
 >
 >Jason
 >
 >
 >"Justin James" <[email protected]> wrote in message news:[email protected]...
 >>
 >> Giri,
 >>
 >> I'm not a weblogic representative, but I tried to replicate this proxing service inside a load balancing switch(BigIP) and I
 >discovered a few things. The weblogic server sets a cookie (WebLogicSession)that the webserver plugin uses to manage the proxying.
 >The cookie (found in the HTTP header information) contains encoded information about the primary and secondary application servers
 >that the session is bound too. Any web server can read the cookie to determine how to dispatch the request to the primary server.
 >If the primary server does not respond, the request is forwarded to the secondary server by the plugin. Regardless of cluster size,
 >the session is replicated to only one other server.
 >>
 >> <[email protected]> wrote:
 >> >Giri Alwar wrote:
 >> >
 >> >> I need a couple of clarifications. First with regard to Question 1, I understand that plugins provide load balancing and
 >failover but what I really was asking is how the plugin in WS2 knows that a session for the client has been initiated in AS1 as a
 >result of WS1 sending the initial request to AS1. If WS2 gets a future request from the client, it needs to know this to send the
 >request to AS1. Does the plugin talk to the cluster to find out if there is a primary and who it is?
 >> >>
 >> >
 >> >> I should have clarified that my other questions pertain to in-memory replication. If I do not persist the session in a database
 >then does the client get an error message (timeout) when AS1 goes down (assuming we use NES with the WebLogic plugin)?
 >> >
 >> >Plugins' know how to route requests based on cookies. If it can't reach the primary server it will automatically try secondary.
 >In your case it doesn't matter if it reaches to proxy 1 or proxy 2, it is still the same.
 >> >
 >> >- Prasad
 >> >
 >> >> To prevent this error message and achieve failover, do I need to use WebLogic as the proxy server? If so, why isn't the NES
 >plugin doing this?
 >> >
 >> >> Thanks.
 >> >> Giri
 >> >>
 >> >> Prasad Peddada <[email protected]> wrote:
 >> >> >Giri Alwar wrote:
 >> >> >
 >> >> >> Let's say that we have two WebServers (NES) with the weblogic plugin (say WS1 and WS2) and a cluster with two
 >WebLogicCommerce AppServers (say AS1 and AS2). Let's assume that each WebServer and AppServer runs on its own machine (total: 4
 >machines). Now, let's assume that the WebServer "obj.conf" files (on both WS1 and WS2) are setup so that they point to the servers
 >in the cluster (WebLogicCluster="AS1:7601,AS2:7601").
 >> >> >>
 >> >> >> When a new request comes in to one of the WebServers (say WS1), the plugin will route it to one of the AppServers using
 >Round-Robin (say AS1). A session will now be initiated in AS1 and it sends a response back to the client.
 >> >> >>
 >> >> >> Question 1: How does the other proxy in WS2 know that all future requests for this client need to be forwarded to AS1?
 >> >> >
 >> >> > Plugin takes care of load balancing and failover, it is all transparent to the client.
 >> >> >
 >> >> >
 >> >> >> Question 2: For failover, does the cluster automatically replicate the session state existing in AS1 onto AS2 before sending
 >the response (does AS2 automatically become the secondary)?
 >> >> >
 >> >> > If you have only two yes it is automatically your secondary. Yes, replication is synchronous.
 >> >> >
 >> >> >>
 >> >> >> Now let's assume that AS1 crashes/dies. When the next request from the client comes to WS1 or WS2, they will forward it to
 >AS1 (assuming that WS2 knows about the client session in AS1) . Since AS1 has crashed, will the client eventually get a timeout
 >error message?
 >> >> >
 >> >> > If you are using some kind of persistence then you will be able to retrieve the session information and since the server
 >is not available the request will automatically failover.
 >> >> >
 >> >> >> Question 3: To ensure that the session failover happens so that AS2 gets the request instead (becomes the primary), do we
 >need to setup a WebLogic Proxy Server? If so, why can't the plugins for NES provide the failover themselves?
 >> >> >
 >> >> > No, you need only one. Either NES or weblogic proxy.
 >> >> >
 >> >> >
 >> >> >> Thank you very much for your help!
 >> >> >> Giri
 >> >> >
 >> >> >- Prasad
 >> >> >
 >> >
 >>
 >
 >

Does the SCAN feature in 11gR2 provide session failover?

I setup a two-node RAC environment (11.2.0.2), and I can successfully connect to it using Single Client Access Name (SCAN). My clients' tnsnames.ora is as simple as:
RAC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = cluster-scan)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = rac)
I was told by the senior DBA that SCAN provides session failover. By that I mean: suppose there are two nodes, and I have a client establish a connection through sqlplus in another machine (client version 11.2.0.2 as well), eg:
sqlplus system/password@rac
I then use something like "SELECT host_name, instance_name FROM v$instance" to figure out which instance I am connected to and I shutdown that instance by running "shutdown abort" there. The expected behavior is for that client to automatically switch to the surviving node (*in the same session*).
However, it doesn't work that way. Instead, the next SQL statement issued in that sqlplus session results in a "ORA-03113: end-of-file on communication channel." I managed to have it failover automatically, without adding anything (eg: FAILOVER_MODE) in the clients' tnsnames files by creating a service with TAF using srvctl:
srvctl add service -d rac -s ractaf -P BASIC -m BASIC -e SELECT -z 5 -w 120
But I have been told this step is not necessary with 11gR2, and session failover should occur automatically if I installed the grid infrastructure and set up SCAN correctly. But I haven't been able to find anything in the documentation indicating this is the case. So, does the SCAN feature in 11gR2 provide session failover?
Edited by: 894946 on Nov 3, 2011 10:16 AM

I think you are right because session failover is a service property linked to cluster database instances and not a scan listener feature that basically establish connection with right instance.

AM without session failover set up?

Generally I have at least 2 servers for redundancy and plan 2 servers to host AM behind a load balancer. Unfortunately I am unable to support message queue and berkeley sleepycat DB which is required for session failover. So I am curious what the session behavior is without the session failover set up. When one AM server goes down and the other is used does the user click on a link and is asked to login again? Wondering how graceful it is.

Hi.
I have been kind of struggling with session failover for sometime now (it worked perfectly with 2003Q4 though).
Once you have a session queue / DB established, this is how things proceed:
1. User hits load balancer, which directs him / her to one of the servers.
2. User logs in. Load balancer maintains a sticky session. Future requests go to the same server.
3. Say that server goes down. User clicks. Load balancer figures out that server is down, redirects user to another AM server.
4. If you have session failover in place, user can continue to work without logging in (technically!).
It was seamless with 2003Q4. We pulled the cable on one AM server (so resulting DS, DPS, AM and message broker all went offline), and still the user's session transitioned to the other server.
If you do get session failover to work with 2005Q4, would be grateful if you could post something about it.

Cluster enviornment i get session failover exception

Hi All,
In cluster enviornment i get session failover exception comes when one of my node is down .
How can i inform all manage server at the time of creation of session object in cluster enviornment.
Thanks in advance,
Sumit Bhasin

.

Why should we use session failover?

Hello everyone,
I was researching whether or not to implement session failover on ACM7. Apparently the hardware based load balancing is working as one would expect. Probably because the session information is kept on the SSOToken...
Is there a specific scenario, that without session failover be a nightmare?
Furthermore, is there such a scenario if you aren't using stickiness?
Best,
Kirpi

Session information is not kept on the SSOToken, SSOToken is just a big string that identifies a session, but session information is stored in memory in the AM instance it was created.
Session failover enables session information replication between AM instances, so that in case the AM instance that created a session crashes, any other AM instance could be able to get all session information that belongs to SSOToken ID's generated by the crashed instance.
Sticky session is highly recommended in such scenario only for performance purposes, because session replication is expensive. If you enable sticky session LB, AM will get session information from memory.
Which scenario could be a nightmare? If a server crashes all sessions generated by it will be lost. So, all users who are working in that moment will lose session and will be re-asked for credentials. It's a bad user experience, it goes against the main objective of a SSO project, and most important, users could lose some work, depending on the applications integrated to AM.
Regards

Session Failover Documentation

Is there any detailed documentation available concerning the configuration of session failover in the Java EE 5 preview?
Michael

Hello Michael,
to enable Session Failover, open the application-j2ee-engine.xml file and set:
 fail-over-enable mode="on_request" 
All the possible options are:
disable failover is not enabled.
on_request the HTTP session is serialized after completing each request.
on_attribute the HTTP session is serialized every time an attribute is added, changed, or removed from the HTTP session.
Greetings,
Bobby

SUN IDM Failover means session failover concept

Hi All
Anybody have idea how to do configure failover in SUN IDM .
Is there any session failover concept or not?
If not then how we simple failover in SUN IDM?
Thanks
SAini

Hi
Came across this issue myself (just now) and fixed it so thought I'd comment. I appreciate this post is quite old now but this might help anyone else who has this issue.
We are using IDM 8.1 and have 2 DSEE 6.3 instances - one master and one replica. In the help description for Failover Server on the LDAP resource configuration page it says:
"List all servers in the form of "ldap://ldap.example.com:389/o=LdapFailover" which follows the standard LDAP v3 URLs described in RFC 2255. Only the host, port, and dn parts of the URL are relevant in this setting."
We originally listed our second server as above and included the "/o=LdapFailover" bit on the end and we got the same error. We removed the "/o=LdapFailover" and just left "ldap://<host>:<port>" there and it all works.
Hope this helps someone.

AM Session Failover - /opt/SUNWam/bin/amsfo stop not working

Hi,
I have configured AM session failover. I have verified that server is listening on 7777. However as soon I try to stop smsfo, it is giving error.
root@fe1 # /opt/SUNWam/bin/amsfo stop
/opt/SUNWam/bin/amsfo: fe1.test.com:7777,fe2.test.com:7777: not found
root@fe1 #
Is it a configuration error?
Any inputs are really appriciated.
Thanks and Regards,
Shashank
Edited by: shashankj on Jul 7, 2008 9:03 AM

looks like the script is trying to execute your hostnames as a command. Be sure to properly enclose all the script values in quotations (""). Also add set -x to the script for further troubleshooting

Jaas authentication with cutom realm problem

I'm having this problem, I have a web application made with JSF running on Sun One Application Server 9, and I made a cutom realm with Jaas so that the server will be handeling the authentication and it is working fine. The problem is that i want to load some info into the user's session after that he have been authenticated based on the username. But I have on clue how to do it. so I'll be very thanks full it anybody helped me.

Did you resolve this problem? Please let me know. I have the same issue now and don;t know what I should be doing next

Session time out problem

Hi guys
I am using WSAD 5.0. the problem that i am having is that i have a properties file where i give the session time out value along with many other things. and when a user logs in a servlet takes those values from the properties file and sets the session time out value, using session.setMaxInactiveInterval(). but the problem is the session is still maintained even after the stipulated inactive time. Can any one tell me what could be the problem.
Note: when i say session.getMaxInactiveInterval(), i get the value that i have set in the properties file.
Thanks

You're sure you specified seconds rather than milliseconds?
- Saish

HADB session failover & realm problem

Similar Messages

Maybe you are looking for