RE: error pages, actions, and tiles
Hi Susan, Are you certain that no exceptions are being logged for your setup? Note, it appears to work for me other than the exceptions that are logged upon every request. A few more things: I am able to reproduce the problem with the tiles-blank-struts1-1 example app. I have reproduced the problem with both the following Tomcat distributions (from Jbuilder 9): jakarta-tomcat-4.1.24-LE-jdk14 jakarta-tomcat-4.0.6-LE-jdk14 Are other people not forwarding to error pages to actions/tiles? Thanks, Dan -Original Message- From: Susan Bradeen Sent: Friday, September 12, 2003 4:02 PM To: Struts Users Mailing List Subject: RE: error pages, actions, and tiles Hi Dan, Did you get anywhere on this? I just put in a couple of error page definitions in my web.xml to see what happens, and it works ok for me. Here's what I have, basically just what you have: web.xml: error-page error-code404/error-code location/prompterrors.do/location /error-page error-page error-code400/error-code location/prompterrors.do/location /error-page struts-config.xml: action path=/prompterrors type=org.apache.struts.actions.ForwardAction parameter=.regError / tiles-defs.xml: definition name=.regError extends=.base put name=title value=Errors/ put name=content value=/forTesting/testError.jsp/ /definition Do you get the socket errors if you specify a straight JSP file, instead of a tile/action for the error page location attribute? I wonder if all web servers interpret the location attribute the same way. Susan On 09/12/2003 12:42:35 PM Dan Snider wrote: Sorry, I'm actually using the same technique for other errors. I wanted to give a representative case but accidentally grabbed the 400 error definition from struts-config.xml. The struts-config also contains: action type=org.apache.struts.actions.ForwardAction parameter=.error.404.page path=/error/404 / Dan -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 12:25 PM To: Struts Users Mailing List Subject: Re: error pages, actions, and tiles First of all, unless they are email typos, you've got 404s and 400s in your definitions. Should the 400s be 404s? Susan Bradeen On 09/12/2003 11:41:49 AM Dan Snider wrote: Hello, I am using Struts 1.1 and Tiles and I would like to forward error-pages to a tile-composing action. web.xml: error-page error-code404/error-code location/error/404.do/location /error-page struts-config.xml: action type=org.apache.struts.actions.ForwardAction parameter=.error.400.page path=/error/400 / From a user standpoint, it appears works but I now get the following exceptions upon every request, valid or not. ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] java.net.SocketException: Software caused connection abort: socket write error ... ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ... java.net.SocketException: Software caused connection abort: socket write error ... java.net.SocketException: Software caused connection abort: socket write error ... Any ideas? Thanks, Dan - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: error pages, actions, and tiles
On 09/15/2003 10:16:50 AM Dan Snider wrote: Hi Susan, Are you certain that no exceptions are being logged for your setup? Note, it appears to work for me other than the exceptions that are logged upon every request. No, I am not getting any kind of socket errors, or any errors logged. A few more things: I am able to reproduce the problem with the tiles-blank-struts1-1 example app. Where did you get this app? I haven't got this one in my Struts 1.1 distribution. Susan I have reproduced the problem with both the following Tomcat distributions (from Jbuilder 9): jakarta-tomcat-4.1.24-LE-jdk14 jakarta-tomcat-4.0.6-LE-jdk14 Are other people not forwarding to error pages to actions/tiles? Thanks, Dan -Original Message- From: Susan Bradeen Sent: Friday, September 12, 2003 4:02 PM To: Struts Users Mailing List Subject: RE: error pages, actions, and tiles Hi Dan, Did you get anywhere on this? I just put in a couple of error page definitions in my web.xml to see what happens, and it works ok for me. Here's what I have, basically just what you have: web.xml: error-page error-code404/error-code location/prompterrors.do/location /error-page error-page error-code400/error-code location/prompterrors.do/location /error-page struts-config.xml: action path=/prompterrors type=org.apache.struts.actions.ForwardAction parameter=.regError / tiles-defs.xml: definition name=.regError extends=.base put name=title value=Errors/ put name=content value=/forTesting/testError.jsp/ /definition Do you get the socket errors if you specify a straight JSP file, instead of a tile/action for the error page location attribute? I wonder if all web servers interpret the location attribute the same way. Susan On 09/12/2003 12:42:35 PM Dan Snider wrote: Sorry, I'm actually using the same technique for other errors. I wanted to give a representative case but accidentally grabbed the 400 error definition from struts-config.xml. The struts-config also contains: action type=org.apache.struts.actions.ForwardAction parameter=.error.404.page path=/error/404 / Dan -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 12:25 PM To: Struts Users Mailing List Subject: Re: error pages, actions, and tiles First of all, unless they are email typos, you've got 404s and 400s in your definitions. Should the 400s be 404s? Susan Bradeen On 09/12/2003 11:41:49 AM Dan Snider wrote: Hello, I am using Struts 1.1 and Tiles and I would like to forward error-pages to a tile-composing action. web.xml: error-page error-code404/error-code location/error/404.do/location /error-page struts-config.xml: action type=org.apache.struts.actions.ForwardAction parameter=.error.400.page path=/error/400 / From a user standpoint, it appears works but I now get the following exceptions upon every request, valid or not. ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] java.net.SocketException: Software caused connection abort: socket write error ... ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ... java.net.SocketException: Software caused connection abort: socket write error ... java.net.SocketException: Software caused connection abort: socket write error ... Any ideas? Thanks, Dan - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
Re: error pages, actions, and tiles
First of all, unless they are email typos, you've got 404s and 400s in your definitions. Should the 400s be 404s? Susan Bradeen On 09/12/2003 11:41:49 AM Dan Snider wrote: Hello, I am using Struts 1.1 and Tiles and I would like to forward error-pages to a tile-composing action. web.xml: error-page error-code404/error-code location/error/404.do/location /error-page struts-config.xml: action type=org.apache.struts.actions.ForwardAction parameter=.error.400.page path=/error/400 / From a user standpoint, it appears works but I now get the following exceptions upon every request, valid or not. ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] java.net.SocketException: Software caused connection abort: socket write error ... ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ... java.net.SocketException: Software caused connection abort: socket write error ... java.net.SocketException: Software caused connection abort: socket write error ... Any ideas? Thanks, Dan - 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]
RE: error pages, actions, and tiles
Sorry, I'm actually using the same technique for other errors. I wanted to give a representative case but accidentally grabbed the 400 error definition from struts-config.xml. The struts-config also contains: action type=org.apache.struts.actions.ForwardAction parameter=.error.404.page path=/error/404 / Dan -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 12:25 PM To: Struts Users Mailing List Subject: Re: error pages, actions, and tiles First of all, unless they are email typos, you've got 404s and 400s in your definitions. Should the 400s be 404s? Susan Bradeen On 09/12/2003 11:41:49 AM Dan Snider wrote: Hello, I am using Struts 1.1 and Tiles and I would like to forward error-pages to a tile-composing action. web.xml: error-page error-code404/error-code location/error/404.do/location /error-page struts-config.xml: action type=org.apache.struts.actions.ForwardAction parameter=.error.400.page path=/error/400 / From a user standpoint, it appears works but I now get the following exceptions upon every request, valid or not. ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] java.net.SocketException: Software caused connection abort: socket write error ... ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ... java.net.SocketException: Software caused connection abort: socket write error ... java.net.SocketException: Software caused connection abort: socket write error ... Any ideas? Thanks, Dan - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: error pages, actions, and tiles
Hi Dan, Did you get anywhere on this? I just put in a couple of error page definitions in my web.xml to see what happens, and it works ok for me. Here's what I have, basically just what you have: web.xml: error-page error-code404/error-code location/prompterrors.do/location /error-page error-page error-code400/error-code location/prompterrors.do/location /error-page struts-config.xml: action path=/prompterrors type=org.apache.struts.actions.ForwardAction parameter=.regError / tiles-defs.xml: definition name=.regError extends=.base put name=title value=Errors/ put name=content value=/forTesting/testError.jsp/ /definition Do you get the socket errors if you specify a straight JSP file, instead of a tile/action for the error page location attribute? I wonder if all web servers interpret the location attribute the same way. Susan On 09/12/2003 12:42:35 PM Dan Snider wrote: Sorry, I'm actually using the same technique for other errors. I wanted to give a representative case but accidentally grabbed the 400 error definition from struts-config.xml. The struts-config also contains: action type=org.apache.struts.actions.ForwardAction parameter=.error.404.page path=/error/404 / Dan -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 12:25 PM To: Struts Users Mailing List Subject: Re: error pages, actions, and tiles First of all, unless they are email typos, you've got 404s and 400s in your definitions. Should the 400s be 404s? Susan Bradeen On 09/12/2003 11:41:49 AM Dan Snider wrote: Hello, I am using Struts 1.1 and Tiles and I would like to forward error-pages to a tile-composing action. web.xml: error-page error-code404/error-code location/error/404.do/location /error-page struts-config.xml: action type=org.apache.struts.actions.ForwardAction parameter=.error.400.page path=/error/400 / From a user standpoint, it appears works but I now get the following exceptions upon every request, valid or not. ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] java.net.SocketException: Software caused connection abort: socket write error ... ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ... java.net.SocketException: Software caused connection abort: socket write error ... java.net.SocketException: Software caused connection abort: socket write error ... Any ideas? Thanks, Dan - 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] - 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]
RE: error pages, actions, and tiles
Hi Susan, I get no socket errors even if I point to the very error content page I use in the tile definition. What is odd to me is that the exceptions are thrown upon every request, not just in response to an error. This would imply the error handling logic, to some degree, is evaluated upon every request. I can't readily see why that is necessary... Dan -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 4:02 PM To: Struts Users Mailing List Subject: RE: error pages, actions, and tiles Hi Dan, Did you get anywhere on this? I just put in a couple of error page definitions in my web.xml to see what happens, and it works ok for me. Here's what I have, basically just what you have: web.xml: error-page error-code404/error-code location/prompterrors.do/location /error-page error-page error-code400/error-code location/prompterrors.do/location /error-page struts-config.xml: action path=/prompterrors type=org.apache.struts.actions.ForwardAction parameter=.regError / tiles-defs.xml: definition name=.regError extends=.base put name=title value=Errors/ put name=content value=/forTesting/testError.jsp/ /definition Do you get the socket errors if you specify a straight JSP file, instead of a tile/action for the error page location attribute? I wonder if all web servers interpret the location attribute the same way. Susan On 09/12/2003 12:42:35 PM Dan Snider wrote: Sorry, I'm actually using the same technique for other errors. I wanted to give a representative case but accidentally grabbed the 400 error definition from struts-config.xml. The struts-config also contains: action type=org.apache.struts.actions.ForwardAction parameter=.error.404.page path=/error/404 / Dan -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 12:25 PM To: Struts Users Mailing List Subject: Re: error pages, actions, and tiles First of all, unless they are email typos, you've got 404s and 400s in your definitions. Should the 400s be 404s? Susan Bradeen On 09/12/2003 11:41:49 AM Dan Snider wrote: Hello, I am using Struts 1.1 and Tiles and I would like to forward error-pages to a tile-composing action. web.xml: error-page error-code404/error-code location/error/404.do/location /error-page struts-config.xml: action type=org.apache.struts.actions.ForwardAction parameter=.error.400.page path=/error/400 / From a user standpoint, it appears works but I now get the following exceptions upon every request, valid or not. ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] java.net.SocketException: Software caused connection abort: socket write error ... ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ErrorDispatcherValve[localhost]: Exception Processing ErrorPage[errorCode=404, location=/error/404.do] ... java.net.SocketException: Software caused connection abort: socket write error ... java.net.SocketException: Software caused connection abort: socket write error ... Any ideas? Thanks, Dan - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
