Through trial and error, I found that the
CoyoteConnector seems to be the root of the problem.
My pages are served up find with the HttpConnector.
I originally switched to the CoyoteConnector when
I saw that the HttpConnector was deprecated. Does
anyone know if this is a bug and if it has been
reported?
Thanks,
David Morris
[EMAIL PROTECTED] 03/30/03 10:00 AM
I recently moved a site from Tomcat 4.1.12 to 4.1.24.
That site runs a Struts 1.1-RC1 application. After
the update, the main menu worked OK, but my
application failed with a Page cannot be displayed
error. I tried various URLs and could get Tomcat
errors for any page that did not actually exist but
pages that actually did exist (xxx.do) failed. I am
using the Coyote connector and have a single context
defined in the webapps directory.
I ended up bringing the site into Eclipse and started
Debug on the Struts ActionServlet. I hit my break
pointes and lo and behold, the pages work. After some
trial and error, I can see that pages seem to fail
most of the time, but sometimes they work. In debug
with breakpoints they always seem to work.
Does anyone have any ideas how I can narrow this
down. I suppose I could go back to 4.1.12, but after
spending a couple of hours I would like to see it
work.
Thanks,
David Morris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
