Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Lataxes, Karl
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

RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Caldarale, Charles R
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 context.xml and web.xml files as described are similar to what we have running under Tomcat 5.0.25. Which is likely the problem. The Context element has

Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread David Smith
As configured below, try http://d1uap:4901/UMI/UMI/servlet/HUControlServlet The servlet mapping in WEB-INF/web.xml should not include the context path of the webapp. --David 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

RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Lataxes, Karl
, but the results were the same. -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Friday, September 04, 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

RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Caldarale, Charles R
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 to UMI.xml contains only the following: Context

Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karl, On 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

RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Lataxes, Karl
-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Friday, September 04, 2009 10:42 AM To: Tomcat Users List Subject: Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karl, On 9/4

Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 9/4/2009 10:50 AM, Caldarale, Charles R wrote: From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18 what happens if you change your URI

RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Caldarale, Charles R
From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18 what happens if you change your URI mapping to: servlet-mapping servlet-nameHUControlServlet/servlet-name

Re: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Christopher Schultz
-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. I even tried commenting out servlet-mapping altogether, but still

RE: Unable to Access Servlet After Migrating From Tomcat 5.0.25 to 6.0.18

2009-09-04 Thread Lataxes, Karl
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. I even tried