hm, might be a bit of typo-work, but why not specify them in your
deployment-descriptor (aka web.xml)?
example (snippet):
servlet
description/description
display-nameSomeName/display-name
servlet-nameMyServlet/servlet-name
On Fri, Mar 19, 2010 at 11:05 AM, Andrey Ilyin andrey.il...@db.com wrote:
Does this mean that session/servletContext is shared between contexts? E.g.
if I have some attribute in session/application contexts in webapp1 would it
be accesible in webapp2?
when the context is dropped from a
On Fri, Mar 19, 2010 at 11:54 AM, Mark Thomas ma...@apache.org wrote:
2) There is cookie in browser - it will loadbalance to engine which
already
has session - since cookie has no context path
Correct.
Mark, I think you might be missing something here.
If I got the OP correct, it's not
here?
As an aside, have you considered using a less arrogant e-mail address?
First off, I don't see the email-adress as arrogent (since it's
rc46fi). However, I'm owning a domain 2smart4u, and since I stopped
using my real name in public emails (thanks to seach-engines and
spam), I'm using
Guys,
On Fri, Mar 19, 2010 at 5:12 PM, Mark Thomas ma...@apache.org wrote:
On 19/03/2010 12:16, 2smart4u wrote:
As per the thread title the OP wanted to:
Always load balance to same box with different tomcat contexts
I understood it that way that he always wanted to loadbalance the same
just a quick thought:
have you tried installing Tomcat into a directory where it's name is
*not* containing any spaces?
cheers
gregor
--
just because you're paranoid, don't mean they're not after you...
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available
@
On Tue, Mar 16, 2010 at 9:53 PM, Campbell, Lance la...@illinois.edu wrote:
I have a web server and an application server. I use mod_jk to
communicate between apache2.0 and tomcat 6. I don't believe the
communication between apache and tomcat is secured by default. Is there
a way to have it
From the docs:
= [cut] =
If set to true, all paths for session cookies will be set to /. This
can be useful for portlet specification implementations. If not
specified, this attribute is set to false.
= [cut] =
More or less, it drops the context from the Cookie-path, meaning the
cookie is
Resource-Ref is definately 2.3-standard.
Here's a configuration we're running in production. Adapt it to your
needs, should work with TC 5.5 and 6.x:
META-INF/context.xml:
?xml version='1.0' encoding='utf-8'?
Context
Resource
auth=Container
description=somedescr
name=jdbc/someName
Hi guys,
long time no see ;)
I hope somebody can shed some light here since meanwhile I'm running
out of ideas:
I set up a Vanilla Debian Lenny and downloaded the latest Tomcat
6.0.26 from tomcat.apache.org.
I've also installed libapr1, libapr1-dev, openssl and libssl-dev
I untared
Mabye a little piece of infor which might be helpful:
excerpt from config.log (not working):
configure:3402: i486-linux-gnu-gcc --version 5
./configure: line 3404: i486-linux-gnu-gcc: command not found
in config.log (working) the output is
configure:2737: i486-linux-gnu-gcc --version /dev/null
11 matches
Mail list logo
