Apache 2.0.54 and Tomcat 7.0.8
On 15.08.2011 21:20, Pid wrote:
> On 15/08/2011 19:09, Lataxes, Karl wrote:
>> I wrote the code to generate the session id and add it as an HTTP header at
>> the recommendation of someone on the users list. The problem now is
>> appending the jvmr
Working With Apache 2.0.54 and Tomcat 7.0.8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl,
On 8/15/2011 2:09 PM, Lataxes, Karl wrote:
> I wrote the code to generate the session id and add it as an HTTP
> header at the recommendation of someone on the users list.
Not to open a whole can of
@tomcat.apache.org
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
On 15.08.2011 17:09, Lataxes, Karl wrote:
> Yes, the space before "servlet" is a copy/paste error.
>
> I made the LogFormat additions to httpd.conf, set the mod_jk logging level to
>
t;." is not being appended
to the session as expected.
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Saturday, August 13, 2011 8:11 AM
To: users@tomcat.apache.org
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
On 12.08.2011 15:
spite sticky_session being set to 1.
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Friday, August 12, 2011 4:17 AM
To: users@tomcat.apache.org
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
On 11.08.2011 15:32, Lataxes, Karl wrote:
:09 PM
To: Tomcat Users List
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
Rainer Jung wrote:
> On 09.08.2011 20:45, Lataxes, Karl wrote:
>> Our clients cannot send or process JSESSIONIDs as they are not web
>> browsers, but proprietary equipment running
/2011 7:49 AM, Lataxes, Karl wrote:
> After some testing, I determined that appending the session ID to the
> URL will not work.
Why not?
> I can, however, add the session ID as a new HTTP header, but I have to
> determine which modules to use (mod_headers, mod_proxy,
Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
Lataxes, Karl wrote:
> I believe this may what you requested. The parameter information I extracted
> from the request was contained in the request body, as well as the session ID
> I mentioned previously. If we need to include addition
x-www-form-urlencoded'
HEADER: content-length '134'
PARAMETER INFORMATION
PARAM: ''
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Friday, July 15, 2011 3:22 PM
To: users@tomcat.apache.org
Subject: Re: Sticky Session Not Working With Apa
15, 2011 9:44 AM
To: users@tomcat.apache.org
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
On 15.07.2011 12:48, Lataxes, Karl wrote:
> Our servlet assigns a session id to a client when it initially contacts the
> server. The session id consists of "session
ges to the original Tomcat node it initially contacted?
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Wednesday, July 13, 2011 3:12 PM
To: Tomcat Users List
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
On 13/07/2011 19:39, Lataxes,
erver applications will have to be modified accordingly,
which may be an option.
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Wednesday, July 13, 2011 11:23 AM
To: Tomcat Users List
Subject: Re: Sticky Session Not Working With Apache 2.0.54 and Tomcat 7.0.8
On 13/07/2011 14:37, La
We are attempting to run identical servlets under several Tomcat 7.0.8 nodes
behind a load balancer (Apache 2.0.54 using mod_jk), but we have been unable to
get sticky sessions to work. Initial requests are forwarded to a node as
expected, but subsequent requests from the same client are being
Servlet After Migrating From Tomcat 5.0.25
to 6.0.18
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl,
On 9/4/2009 11:10 AM, Lataxes, Karl wrote:
> I tried your suggestion and replaced the trailing / in the url-pattern
> of the servlet-mapping tag with *, but got the same result.
n 9/4/2009 8:56 AM, Lataxes, Karl wrote:
> I am attempting to migrate a servlet from Tomcat 5.0.25 to 6.0.18, but
> my efforts to access it while running under 6.0.18 have been
> unsuccessful.
[snip]
> Here is the stack trace I received when running my server based
> application t
rom Tomcat 5.0.25
to 6.0.18
> From: Lataxes, Karl [mailto:karl.lata...@nielsen.com]
> Subject: RE: Unable to Access Servlet After Migrating From Tomcat
> 5.0.25 to 6.0.18
>
> I made the recommended changes but am still getting the exception.
> The context file that I renamed
2009 9:16 AM
To: Tomcat Users List
Subject: RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25
to 6.0.18
> From: Lataxes, Karl [mailto:karl.lata...@nielsen.com]
> Subject: Unable to Access Servlet After Migrating From Tomcat 5.0.25
> to
> 6.0.18
>
> The cont
I am attempting to migrate a servlet from Tomcat 5.0.25 to 6.0.18, but
my efforts to access it while running under 6.0.18 have been
unsuccessful. The servlet is accessed on the server via HTTP, but has
web interfaces for simple testing and to check servlet loading and
client-server message traffic
18 matches
Mail list logo
