sly (apparently due to the
pipelining of requests, it would seem). When I tried with two wget
processes instead, it actually worked as it should.
Thanks for the lead, and sorry for the unnecessary commotion!
Fredrik Tolf
-
To
a.lang.Object.wait(Object.java:485)
at org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable.run(ThreadPool.java:656)
- locked <0x95401098> (a org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable)
at java.lang.Thread.run(Thread.java:619)
Except one, which is tryi
for tab 1 will finish at 12:00:20, and the
request for tab 2 will finish at 12:00:30.
Why is this? Is Tomcat explicitly not handling two requests for the
exact same URL in parallel? It is the only explanation I can think of,
but I cannot figure out how or why it wo
ok at webservices.
Thanks for the tip, but I think any SSO hack would be far easier to
implement and maintain than starting to use web services.
Fredrik Tolf
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe
t, so that
it exists when the client comes back.
3. Use reflection somehow to fetch the SSOID cookie from the SSO valve.
I don't think this is possible, though, thanks to Tomcat's protection
against reflection from webapps.
