.
Something like HttpSessionListener.preSessionDestroyed() is what i need..I
wonder why cant they give such control..
Christopher Schultz-2 wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farhan,
mfs wrote:
| Actually i need to provide my own session timeOut/expiry
Guys,
Guys
Actually i need to provide my own session timeOut/expiry implementation and
i was wondering what would be the easiest way to achieve this, i am using
tomcat for development but oc4j for production, and i was wondering if
somehow i can hook in my implementation into various servlet
the
session managers of each and provide my own, and i am getting a stomach ache
by just thinking about it.
Farhan.
markt-2 wrote:
mfs wrote:
Given the above context, i was wondering if there is some way i can
provide
my own unique sessionId to the servlet container whenever it creates a
unique
it help inter-op..
Thanks
Christopher Schultz-2 wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Farhan,
mfs wrote:
| Actually we have our own session tracking framework, and now
| that i am making a seperate servlet based application, i have come to
need
| to support
Guys,
I would want to know the downsides to using cookie-less sessions ? I want to
give my client the freedom to disable cookies on the browser if he chooses
to, but i would want to know the implications to that ?
Some say, exposing your sessionId in the url exposes it to hackers who can
spoof
Guys,
Might not be the question for this list, but still to thought to check.
Is there a way i can provide the unique sessionID to the servlet
api/container, instead of it generating its own (whenever a new HttpSession
is created). Actually we have our own session tracking framework, and now
Guys,
I have got my web app deployed on the tomcat 6.0.13, I wonder what
configuration do i have to do so as to make tomcat (built-in http server)
handles the scenario where a user has disabled the cookies on the browser ?
though that wouldnt be the case for most of the users but still if that
Guys,
I have setup a cluster where i have two tomcat instances (one on windows and
the other on linux), the two instances are able to detect each other and
form a cluster. On top of them i have apache/mod_jk as a load-balancer which
has sticky-sessions set to FALSE...I am trying to test this
Guys,
I have setup a cluster where i have two tomcat instances (one on windows and
the other on linux), the two instances are able to detect each other and
form a cluster. On top of them i have apache/mod_jk as a load-balancer which
has been set NOT to use sticky-sessions, since i want to test
Mistakenly put the wrong worker.properties in my last post where the
worker.lbworker.sticky_session=false was commented which is not the
case
Farhan.
mfs wrote:
Guys,
I have setup a cluster where i have two tomcat instances (one on windows
and the other on linux), the two
Guys,
Pretty basic question, given this is my time experience on clustering where
i am trying to use tomcat 6 clustering support.
So basically i wanted to know if enabling the tomcat 6 clustering would be
of any use without having a load-balancer in the front (something like
mod_jk) ? well my
to handle failover. Otherwise there is not a huge
amount
of point. Either a load balancer or mod-jk will do the job.
On Nov 27, 2007 4:13 PM, mfs [EMAIL PROTECTED] wrote:
Guys,
Pretty basic question, given this is my time experience on clustering
where
i am trying to use tomcat 6 clustering
12 matches
Mail list logo