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 Konstantin Kolinko
2012/11/13 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 a

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've got another probl

Re: Mystery migrating from tomcat 6 to 7

2012-11-12 Thread Konstantin Kolinko
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've got another problem, but at least I know why the app fail

Re: Mystery migrating from tomcat 6 to 7

2012-11-12 Thread 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've got another problem, but at least I know why the app fails to run. Here's the problem

Re: Mystery migrating from tomcat 6 to 7

2012-11-12 Thread Fred Toth
Hi, Sorry, just getting back to this after a delay. I've added an AccessValve to my context and it, too, reports 404. So this is more confirmation that my context has actually deployed (as the logs report), and, at least at some level, the requests are being mapped by tomcat to the correct co

Re: Mystery migrating from tomcat 6 to 7

2012-11-07 Thread Pid
On 02/11/2012 19:27, Fred Toth wrote: > signature.asc Description: OpenPGP digital signature

Re: Mystery migrating from tomcat 6 to 7

2012-11-06 Thread Konstantin Kolinko
2012/11/2 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

Re: Mystery migrating from tomcat 6 to 7

2012-11-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred, On 11/2/12 4:25 PM, Fred Toth wrote: > Well, let me post at least the last bit (the whole thing is noisy > and long). See below for the indication of a normal startup. In > particular, my app finishes startup with "initialized Struts-Spring > in

Re: Mystery migrating from tomcat 6 to 7

2012-11-02 Thread Fred Toth
Hi, Well, let me post at least the last bit (the whole thing is noisy and long). See below for the indication of a normal startup. In particular, my app finishes startup with "initialized Struts-Spring integration successfully" and tomcat indicates it's done with "Server startup in 7487 ms".

Re: Mystery migrating from tomcat 6 to 7

2012-11-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred, On 11/2/12 3:27 PM, Fred Toth wrote: > 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 norm

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