nesday, 21 October, 2009, 5:52 PM
sudip pattanayak wrote:
> Hi Mark,
>
> I am not sure about the code, but we are confirming on whether we can share
> the code.
> As of now I have some logs. Can you derive something based on the same.
Not really. As a wil
WARN
CORE:WebconsoleSecurityProvider.login():
Returning Exception: javax.security.auth.login.LoginException: Failed to force
log off due to an internal error. One or more
of your sessions are in an invalid state and cannot be terminated.
If you see the last message it is the
Hi,
In our web application we have a design of allowing one user to login from one
instance at any point of time.
In case his earlier session is active while he tries to login from another
instance the earlier instance gets forcefully logged off.
But it so happens that if due to some problem o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sudip,
On 2/10/2009 2:36 AM, sudip pattanayak wrote:
> We have an implementation where by we call the value unbound to
> release sessions for any users.
Could you explain this in more detail?
> For any user which does not logoff from the previous sess
Hi,
We have an implementation where by we call the value unbound to release
sessions for any users.
For any user which does not logoff from the previous session we logoff the user
forcefully for the next session he tries to login.
But there are couple of instances not consistent though that th
Dear Sudip,
> But recently there are couple of occasions where one or
> more users are failing to forcefully logoff the session.(thelogs shows
> clearly the pending sessions keeps on increasing and the value unbound
> is never called for the particular user failing to forcefully logoff.
Well, we
Hi,
We are using apache-tomcat for our Web Application.
We do not allow to same users to log on from two instances of the application.
So
if the user is active from one session and then if he tries to log on
from another session, we forcefully logoff the user from the previous
session.
But recent
