Helge,
On 7/25/23 05:24, Wiemann, Helge (ESI) wrote:
we have a problem that we have set the tomcat timeout to 10 minutes. But
after a successful login with a realm, the user is automatically logged
out, sometimes after one minute, sometimes other times.
I have downloaded the source code,
Find all implementations of Session, then set breakpoiunt on
session.invalidate() would be a good place to start. Another good place
would be your SessionManager as it has several interesting methods.
The JVM's JDI does not allow you to set breakpoint on an interface, but
some IDE's have a magic
Hi all,
we have a problem that we have set the tomcat timeout to 10 minutes. But after
a successful login with a realm, the user is automatically logged out,
sometimes after one minute, sometimes other times.
I have downloaded the source code, want to set a breakpoint. Does anybody know
a
Really any idea?
Il giorno 04/ott/2011 19:13, Gabriele Faelli gabriele.fae...@gmail.com
ha scritto:
Hi all,
I'm running tomcat 5.5.23 on two RHEL 5.6.
I'm having big trouble making the session replication working across these
two nodes.
I configured a cluster and it looks like working: each
- Original Message -
From: Gabriele Faelli gabriele.fae...@gmail.com
To: users@tomcat.apache.org
Cc:
Sent: Wednesday, October 5, 2011 1:17 AM
Subject: Re: problem with session replication in tomcat 5.5.23
Really any idea?
Il giorno 04/ott/2011 19:13, Gabriele Faelli
Hi all,
I'm running tomcat 5.5.23 on two RHEL 5.6.
I'm having big trouble making the session replication working across these
two nodes.
I configured a cluster and it looks like working: each node discovers the
other one, I can see in the logs every received and transmitted ping.
Well, when I
Hi Chris,
First of all thanks for reply.
On Nov 15, 2007 8:09 PM, Christopher Schultz
[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacek,
Jacek Olszak wrote:
The problem is that the method
HttpSessionActivationListener.sessionDidActivate() is called before
Hi again, I found that I've sent wrong log when stopping the server
(second log in my earlier post). The correct is:
INFO: Pausing Coyote HTTP/1.1 on http-8080
2007-11-16 10:50:35 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
DEBUG 2007-11-16 10:50:35,625
Hi,
I try to describe my situation. I have a couple of session beans which
have transient properties. Those properties are in fact references to
Spring application beans. When the session is activated after restart
I want to inject spring beans again into restored session beans.
Unfortunately
I think your problem may be rooted in a misunderstanding* of this
listeners purpose. Perhaps you can elaborate on what you're trying to
achieve?
HttpSessionActivationListener.sessionDidActivate() is called when a
session is retrieved from a persisted state or moved to another JVM.
It's
Jacek Olszak wrote:
Hi,
I try to describe my situation. I have a couple of session beans which
have transient properties. Those properties are in fact references to
Spring application beans. When the session is activated after restart
I want to inject spring beans again into restored
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacek,
Jacek Olszak wrote:
I try to describe my situation. I have a couple of session beans which
have transient properties. Those properties are in fact references to
Spring application beans. When the session is activated after restart
I want
Hi everyone!
I have a problem with session activation after Tomcat 6 restart.The
problem is that the method
Thainks in advance,
Jacek
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL
Hi everyone!
I've a problem with session activation after Tomcat 6 restart. The
problem is that
the method HttpSessionActivationListener.sessionDidActivate() is called before
any context listeners. I have a ContextLoaderListener configured in my
web.xml which
create the Spring context. I want my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacek,
Jacek Olszak wrote:
The problem is that the method
HttpSessionActivationListener.sessionDidActivate() is called before
any context listeners. I have a ContextLoaderListener configured in
my web.xml which creates the Spring context.
Do
wrote:
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: RE: Problem with session
You mentionned a session listener, can you point me out to a
tutorial on how to do it?
See section 10 of the Servlet spec.
Are there any generic session listener that I could use out
of the box?
There's
said in my first post that I did not exagerate, the server does receive a
LOT of requests per second.
Than you again.
Caldarale, Charles R wrote:
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: RE: Problem with session
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
That's
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: RE: Problem with session
You mentionned a session listener, can you point me out to a
tutorial on how to do it?
See section 10 of the Servlet spec.
Are there any generic session listener that I could use out
of the box?
There's one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex,
Alex79 wrote:
You mentionned a session listener, can you point me out to a tutorial on how
to do it?
Easy: write a class that implements
javax.servlet.http.HttpSesionListener and then enable it in your web.xml
file like this:
listener
at the keepalive and let you know if it has an
impact.
Thank you very much for this info.
Caldarale, Charles R wrote:
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: Problem with session
I am running a web service on tomcat, which I am not very
familiar with (tomcat).
At least tell us
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: RE: Problem with session
I checked the log in the logs directory, there's nothing that
says tomcat has been restarted.
What about the webapp being restarted? (Not likely either.)
I run tomcat 5.0.
Tomcat 5.0.what?
It's an internal
that wrong and that it does come from tomcat.
Where can I find the exact tomcat version?
Thank you,
Caldarale, Charles R wrote:
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: RE: Problem with session
I checked the log in the logs directory, there's nothing that
says tomcat has been
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: RE: Problem with session
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
That's a couple of updates old, but very unlikely to be an issue.
When the problem occurs, I see a WARN level message that
says that there is no header (custom
: RE: Problem with session
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
That's a couple of updates old, but very unlikely to be an issue.
When the problem occurs, I see a WARN level message that
says that there is no header (custom info stored by the
webapp) in session (managed
idea if
tomcat is somehow auto-refreshing my web application (or itself) causing my
session to be cleared?
Thank you for pointing me out to any useful info.
Alex
--
View this message in context:
http://www.nabble.com/Problem-with-session-tf4585082.html#a13088302
Sent from the Tomcat - User
From: Alex79 [mailto:[EMAIL PROTECTED]
Subject: Problem with session
I am running a web service on tomcat, which I am not very
familiar with (tomcat).
At least tell us the version of Tomcat you're using; also, although
probably not relevant for this problem, include the JRE/JDK level
Hi,
I have installed two tomcat 5.5.16 instances on different linux machines. I
have clusttered the both machines using session replication. After configuring
the instances and i have restarted the machines but i got the warning.as below.
IOException in replication worker, unable to drain
Hmm, context.xml? I know only of server.xml. At least on Windows. Here is a
context snippet for server.xml which disables session persistence.
Michael
Context docBase=/your-doc-base path=/your-context
Manager className=org.apache.catalina.session.PersistentManager
or shorter with
Context docBase=/your-doc-base path=/your-context
Manager pathname= /
/Context
at tomcat 5.5 add the description at your META-INF/context.xml
Context
Manager pathname= /
/Context
or at the conf/context.xml
:-)
Greetings everyone,
I am using Tomcat 5.0.19 on Fedora Linux, Core 2. My catalina.out shows the
ugly exceptions during shutdown.
Some Googling revealed that session serialization can be disabled by added
the following XML snipett in the context.xml:
Manager pathname=/
I was
30 matches
Mail list logo
