Re: Adding user session id to access log with %S doesn't work?

2014-06-09 Thread Fred Toth
I've been going down this trail. Thanks again, Fred On 6/9/2014 1:03 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Fred, On 6/9/14, 10:59 AM, Fred Toth wrote: I'm confused. I thought (apparently mistakenly) that there was always a session, but I mus

Re: Adding user session id to access log with %S doesn't work?

2014-06-09 Thread Fred Toth
On 6/9/2014 4:58 AM, Mark Thomas wrote: On 09/06/2014 01:41, Fred Toth wrote: Hi Dan, Yes, the rest of the log is correct, and yes, I am certain I have an active session (I can see the cookie in my browser). Then something is messed up in your configuration. I've just checked this works and i

Re: Adding user session id to access log with %S doesn't work?

2014-06-08 Thread Fred Toth
Hi Dan, Yes, the rest of the log is correct, and yes, I am certain I have an active session (I can see the cookie in my browser). Thanks, Fred On 6/8/2014 4:30 PM, Daniel Mikusa wrote: On Jun 8, 2014 4:01 PM, "Fred Toth" wrote: Hi, This feature is in the doc since at least tom

Adding user session id to access log with %S doesn't work?

2014-06-08 Thread Fred Toth
Hi, This feature is in the doc since at least tomcat 5. I'm using tomcat 7.0.47 and I just tried to add the user session id to the access log by adding "%S" to the pattern attribute. However, it's not working. All I'm getting is "-" in the log. Is there some trick to this? I haven't found an

Re: Mystery migrating from tomcat 6 to 7

2012-11-13 Thread Fred Toth
On 11/13/2012 2:57 AM, Konstantin Kolinko wrote: It looks like it overrides the default mapping of this servlet. If I add the above fragment to web.xml of the docs application, I get 404 in Tomcat 7, while in Tomcat 6 it works. If I replace above with the following, it works in Tomcat 7:

Re: Mystery migrating from tomcat 6 to 7

2012-11-12 Thread Fred Toth
On 11/12/2012 4:24 PM, Konstantin Kolinko wrote: 2012/11/13 Fred Toth : Hello again, I've found my problem, sort of. In this particular application, ever since tomcat 5, we've been remapping the DefaultServlet url-pattern. Works fine in 5 and 6, but not in 7. Which means I'

Re: Mystery migrating from tomcat 6 to 7

2012-11-12 Thread Fred Toth
why having this setup in tomcat 7 causes my app to fail completely, but taking this out cures the core problem. URLs start working properly, but now I have access control problems that were solved by the above. Could be the topic of another thread after I dig some more. Thanks, Fred On 11/1

Re: Mystery migrating from tomcat 6 to 7

2012-11-12 Thread Fred Toth
id wrote: On 02/11/2012 19:27, Fred Toth wrote: Is your application mounted on an NFS share? p (hint: don't do that.) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Mystery migrating from tomcat 6 to 7

2012-11-02 Thread Fred Toth
org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["ajp-bio-8009"] Nov 2, 2012 2:31:05 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 7487 ms On 11/2/2012 3:44 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

Mystery migrating from tomcat 6 to 7

2012-11-02 Thread Fred Toth
Hi, I've got a struts2/spring app that's been running under tomcat 6 with no problems. I migrated it to 7 and I've hit a strange brick wall. On startup, the logs show the app deploying, absolutely normally with no errors at all. However, when I try to hit any URL within the app's context, I

Solution to integrating error-page with struts2

2008-09-19 Thread Fred Toth
Hi all, I had problems trying to get tomcat to forward to a struts2 action from an directive in web.xml. I was all set to run to the list for help when I figured it out. I thought I'd post this anyway in case it helps someone else. I had error-page working in the simplest sense. If I pointed it

Extending DefaultServlet, broken welcome-file

2008-04-23 Thread Fred Toth
Hi all, I'm lost in the woods. Some time ago we built an application that required us to extend the TC 5.5 DefaultServlet. All we did was point it to an external path (outside the war file). It works great. However, I now realize that I've somehow broken the mechanism for our extended servlet.