-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
George,
On 2/22/2010 2:37 PM, George Baxter wrote:
> Thanks for everyone's help... it was indeed app code.. some old ugly
> legacy code was putting a reference to a request in a thread local
> variable and then not cleaning up the thread local referen
George Baxter wrote:
...
We're still a bit confused as to why this code works fine in Tomcat 5.5 and
fails so gloriously in 6, but I suppose the recycling model and maybe the
thread handling model is different.
Yeah, that's always the problem when correcting bugs in released
software. A lo
Thanks for everyone's help... it was indeed app code.. some old ugly legacy
code was putting a reference to a request in a thread local variable and then
not cleaning up the thread local reference when the request ended. When the
thread was reused, it was referencing a request that was no longe
Hmm, well it's possible. However, I'm not entirely confident that each request
has its own Cookies object. There is a 'setHeaders()' method on Cookies.
What's it for? Checking myself. Will add more logging as you suggested.
We are using Spring MVC which uses ThreadLocal to store requests..
On 18/02/2010 20:23, George Baxter wrote:
> So we think we've found a threading problem in the cookie handling.
Hmm. Each request has its own Cookies object. The only way these would
be shared between threads is if two threads were using the same request
object. That usually happens when custom fi
So we think we've found a threading problem in the cookie handling.
Running on Solaris 10, jdk 1.5, tomcat 6.0.24.
We built our 'own' version of 6.0.24, adding logging in some places, and
ultimately, this is what we discovered:
A bit of information: in these log entries, we're looking at 2 thr
Downloaded src code of tomcat for debugging purposes and sure enough, our
cookies are of type byte, so the fact that the code can parse the cookie
'string' just fine means diddly-squat.
Next plan, build my own tomcat 6.0.24 version with lots of logging and checks
for debugging purposes...
-g
Well.. we parsed the header that failed, and it parsed just fine.
Note that we're parsing via the 'old deprecated' parse by string entity. I
guess I'll try parsing by bytes next.
-g.
On Feb 16, 2010, at 2:47 PM, Konstantin Kolinko wrote:
> 2010/2/17 George Baxter :
>> Hi Konstantin,
>>
>> Th
We took a quick look at the cookie parsing code and unfortunately, logging is
dependent not on log4j configuration, but instead on a static final int 'dbg'
variable defined in the Cookies.java.
I'll try copy/paste code into my own class to see how it fairs on the header
value.
-g.
On Feb 16,
Hi Konstantin,
1. We're still an Latin-1 shop, primarily...
.. skip to
3. We've tried 6.0.24 as well, same result.
We were using 6.0.18 because I've been using in (on my Mac in development,
other users using Linux in development) for the past 8 months with no real
issues.
I'll get to work o
2010/2/17 George Baxter :
> Hi Konstantin,
>
> Thanks for your reply.
>
> Yes, the getHeaders("cookie") returns what seems to be a valid set of
> cookies, thus we're not losing them in any of the proxies we might have set
> up. (Currently, we're only in development mode for tomcat 6 and we're no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
George,
On 2/16/2010 5:14 PM, George Baxter wrote:
> Yes, the getHeaders("cookie") returns what seems to be a valid set of
> cookies, thus we're not losing them in any of the proxies we might
> have set up.
Good to know. But this means that Tomcat is
Hi Konstantin,
Thanks for your reply.
Yes, the getHeaders("cookie") returns what seems to be a valid set of cookies,
thus we're not losing them in any of the proxies we might have set up.
(Currently, we're only in development mode for tomcat 6 and we're not going
through any proxies, just dir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 2/12/2010 5:32 PM, Konstantin Kolinko wrote:
> What connectors are you using? HTTP/AJP? Nio/Bio/Apr? (usually some
> org.apache.coyote.* class is mentioned in the startup log in a
> "Starting Coyote .." message) Do you have Apache HTT
2010/2/13 George Baxter :
>
> Hello,
>
> We're running into an issue with tomcat 6.0.18 running on solaris.
> Occasionally a request will come through that has cookies in the header, but
> the request.getCookies() returns no cookies.
How do you observe that? You mean that it is present in
HttpServ
s what might be happening?
Thanks.
--
View this message in context:
http://old.nabble.com/tomcat-6-on-solaris-losing-cookies-tp27569008p27569854.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To u
On Fri, Feb 12, 2010 at 12:55 PM, George Baxter wrote:
>
> Yes, yes, I accidentally hit return instead of tab when jumping from subject
> line to message.. mea culpa! I filled in the text with an edit later!
I, for one, welcome our vistor from the future, where emails can be
retroactively edited
mputers.
>
>> -Original Message-
>> From: George Baxter [mailto:gbax...@shutterfly.com]
>> Sent: 2010 February 12, Friday 14:39
>> To: users@tomcat.apache.org
>> Subject: tomcat 6 on solaris losing cookies
>>
>>
>>
>> --
>> View this m
the sender and delete the e-mail and its
attachments from all computers.
> -Original Message-
> From: George Baxter [mailto:gbax...@shutterfly.com]
> Sent: 2010 February 12, Friday 14:39
> To: users@tomcat.apache.org
> Subject: tomcat 6 on solaris losing cookies
>
>
--
View this message in context:
http://old.nabble.com/tomcat-6-on-solaris-losing-cookies-tp27569008p27569008.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
20 matches
Mail list logo
