Re: JSP Compiler output?
One other thought: I notice that the compiler messages look like ant messages -- could the problem be that ant is not in my classpath or system path some related ant setting? Noel Noel Rappin wrote: I replicated this experiment exactly in my environment. Tomcat 4.1.24, Linux, JSDK 1.4.1_01. Is it a Linux thing? Here's my stack trace in localhost: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:500) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:150) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:195) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) By the way, I really appreciate your time in helping with this. Noel Tim Funk wrote: You should get something somewhere. For example ... With 4.1.24 (win2k, jdk1.3, but 1.4 is the same result), I have a file called foo.jsp (at /) with the contents: % more cowbell % My error screen is attached. In the logs (localhost_log.2003-06-17.txt) I get: 2003-06-17 16:34:06 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Since fork is true, ignoring compiler setting. [javac] Compiling 1 source file [javac] Since fork is true, ignoring compiler setting. [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: ';' expected [javac] more cowbell [javac] ^ [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: cannot resolve symbol [javac] symbol : class more [javac] location: class org.apache.jsp.foo_jsp [javac] more cowbell [javac] ^ [javac] 2 errors at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130) ... -Tim Noel Rappin wrote: Okay. I did a clean install of tomcat. I placed a compilation error in one of the example JSPs. I am now seeing this in the logs: * catalina.out: start/stop messages * localhost_examples: a stack trace saying that there was a JasperException: unable to compile class for JSP * localhost_log: messages about servlet loading. What I don't see is a message saying something useful about the compilation error -- like Compile failed on line 10, statement expected or some such. Are those messages just not generated? Noel - 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: JSP Compiler output?
Interesting... can you point me to more information, or has this been discussed on this list? Noel Jason Bainbridge wrote: I haven't really been following this thread but is this the problem where in some scenarios that JAVA_HOME/bin needs to be in the system PATH? Regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP Compiler output?
There is a root cause, but it doesn't have the error info... java.lang.ClassNotFoundException: org.apache.jsp.foo_jsp at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:209) at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:131) at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:497) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:150) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:195) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) I was also able to replicate Tim's stack trace on a windows machine... the relevant part is here.. at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) It looks like in Tim's case, the compilation called at JspServletWrapper:190 triggers an error, that my system is swallowing. My system apparently makes it to JspServletWrapper:195, where it then seems to be looking for the compiled jsp class file, which it's not finding -- only then does my system show the stack trace. The question, I guess, is why is my system swallowing the javac DefaultErrorHandler? I guess I'll dig into the code. Thanks, Noel Shapira, Yoav wrote: Howdy, This isn't the full stack trace: please post the full one with the Root Cause. Yoav Shapira Millennium ChemInformatics -Original Message- From: Noel Rappin [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 4:59 PM To: Tomcat Users List Subject: Re: JSP Compiler output? I replicated this experiment exactly in my environment. Tomcat 4.1.24, Linux, JSDK 1.4.1_01. Is it a Linux thing? Here's my stack trace in localhost: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java :500 ) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrappe r.ja va:150) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.j ava: 195) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295 ) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) By the way, I really appreciate your time in helping with this. Noel Tim Funk wrote: You should get something somewhere. For example ... With 4.1.24 (win2k, jdk1.3, but 1.4 is the same result), I have a file called foo.jsp (at /) with the contents: % more cowbell % My error screen is attached. In the logs (localhost_log.2003-06-17.txt) I get: 2003-06-17 16:34:06 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Since fork is true, ignoring compiler setting. [javac] Compiling 1 source file [javac] Since fork is true, ignoring compiler setting. [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: ';' expected [javac] more cowbell [javac] ^ [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: cannot resolve symbol [javac] symbol : class more [javac] location: class org.apache.jsp.foo_jsp [javac] more cowbell [javac] ^ [javac] 2 errors at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH andl er.java:130) ... -Tim Noel Rappin wrote: Okay. I did a clean install of tomcat. I placed a compilation error in one of the example JSPs. I am now seeing this in the logs: * catalina.out: start/stop messages * localhost_examples: a stack trace saying that there was a JasperException: unable to compile class for JSP * localhost_log: messages about servlet loading. What I don't see is a message saying something useful about the compilation error -- like Compile failed on line 10, statement expected or some such. Are those messages just
Re: JSP Compiler output?
We seem to have been able to get the error stack traces by adding the init-param fork to the JSP servlet, with a value of false. Any idea why this works? Noel Noel Rappin wrote: There is a root cause, but it doesn't have the error info... java.lang.ClassNotFoundException: org.apache.jsp.foo_jsp at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:209) at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:131) at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:497) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:150) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:195) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) I was also able to replicate Tim's stack trace on a windows machine... the relevant part is here.. at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) It looks like in Tim's case, the compilation called at JspServletWrapper:190 triggers an error, that my system is swallowing. My system apparently makes it to JspServletWrapper:195, where it then seems to be looking for the compiled jsp class file, which it's not finding -- only then does my system show the stack trace. The question, I guess, is why is my system swallowing the javac DefaultErrorHandler? I guess I'll dig into the code. Thanks, Noel Shapira, Yoav wrote: Howdy, This isn't the full stack trace: please post the full one with the Root Cause. Yoav Shapira Millennium ChemInformatics -Original Message- From: Noel Rappin [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 4:59 PM To: Tomcat Users List Subject: Re: JSP Compiler output? I replicated this experiment exactly in my environment. Tomcat 4.1.24, Linux, JSDK 1.4.1_01. Is it a Linux thing? Here's my stack trace in localhost: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java :500 ) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrappe r.ja va:150) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.j ava: 195) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295 ) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) By the way, I really appreciate your time in helping with this. Noel Tim Funk wrote: You should get something somewhere. For example ... With 4.1.24 (win2k, jdk1.3, but 1.4 is the same result), I have a file called foo.jsp (at /) with the contents: % more cowbell % My error screen is attached. In the logs (localhost_log.2003-06-17.txt) I get: 2003-06-17 16:34:06 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Since fork is true, ignoring compiler setting. [javac] Compiling 1 source file [javac] Since fork is true, ignoring compiler setting. [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: ';' expected [javac] more cowbell [javac] ^ [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: cannot resolve symbol [javac] symbol : class more [javac] location: class org.apache.jsp.foo_jsp [javac] more cowbell [javac] ^ [javac] 2 errors at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorH andl er.java:130) ... -Tim Noel Rappin wrote: Okay. I did a clean install of tomcat. I placed a compilation error in one of the example JSPs. I am now seeing this in the logs: * catalina.out: start/stop messages * localhost_examples: a stack trace saying that there was a JasperException: unable to compile class for JSP * localhost_log: messages about servlet loading. What I don't see is a message saying
JK Connector url rewrite question
I'm running an Apache/Tomcat combination using mod_jk. Whenever I enter a URL to hit the apache server, somewhere along the redirect to tomcat the server portion of the url gets changed. So, if I type http://localhost/myapp I actually get in the browser http://my.hostname.com/myapp This even happens if I type the IP address, rather than a hostname. I'd really like it to not do this, and just use the hostname or IP address that I type in, but I can't seem to find any hook to change this behavior. Can anybody help? Noel Rappin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jk connector and host name
I'm setting up an apache connector using jk2, and there's one weird thing. If I hit the apache site with http://localhost/myapp the request passes to tomcat, but gets rewritten to http://my.hostname.com/myapp. This is harmless on localhost, but is a problem on another test lab where http://a.teslab.hostname.com is being incorrectly rewritten to http://a.hostname.com. Is there a setting that will prevent the hostname on the request from changing? Thanks, Noel Rappin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSDK/JRE
Sorry if this is an FAQ, but I can't find the exact information anywhere. I see that Tomcat requires a JDK, not a JRE to enable compilation of JSP pages. Is there any reasonable way to run off a JRE? Are there any license issues involved in distributing the JDK as part of a web application instead of the JRE (we actually distribute the web application, so it's not a question of just having one copy on our server)? How do other people manage this in practice? Thanks, Noel Rappin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deployment question
Quick question about deployment. I'm trying to get tomcat to auto-deploy a .war file for an application whose home is outside the normal tomcat /webapps directory. It doesn't seem to be recognizing it. Where should I put the war file to get the auto-deploy behavior? Is there some setting that I need to change? Thanks, Noel Rappin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSP Compiler output?
We're porting an application from JRun to Tomcat, and we're having one large issue... When a JSP compile fails on the Tomcat Server, the log message just says that there was a failure, but doesn't say what the compiler error actually is. We can't seem to find any place where the actual compiler error is saved or logged. Is there any way to find the actual text of the compiler error so that we can track it down? Noel Rappin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSP Compiler output?
I did. Doesn't seem to be there. Is there a setting I'm missing? Noel Tim Funk wrote: Check localhost_log.xxx -Tim Noel Rappin wrote: We're porting an application from JRun to Tomcat, and we're having one large issue... When a JSP compile fails on the Tomcat Server, the log message just says that there was a failure, but doesn't say what the compiler error actually is. We can't seem to find any place where the actual compiler error is saved or logged. Is there any way to find the actual text of the compiler error so that we can track it down? Noel Rappin - 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: JSP Compiler output?
The localhost file is there, but the JSP compiler messages are not winding up there -- we're getting a message in the app file saying that there was a compilation failure, but not the compiler message saying where and what the failure is. We're running on linux, log4j is in the application classpath, server.xml is writing to a log file for our application, but the message we're looking for is not getting there. I can't imagine how our webapp is eating the exception, but I suppose it's possible that log4j is dropping it on the floor somewhere along the way, but I can't figure out where that might be either. It's quite strange. Noel Tim Funk wrote: It should be somewhere into the $TOMCAT_HOME/logs/ directory. If its not ... - If your running windows service - is it in an event log? (guessing) - Is your server.xml writing to any other logs files? - Is your JSP/servlet/webapp /... eating the exception and not logging? (Which would be odd, since I would think this would always be logged) -Tim Noel Rappin wrote: I did. Doesn't seem to be there. Is there a setting I'm missing? Noel Tim Funk wrote: Check localhost_log.xxx -Tim Noel Rappin wrote: We're porting an application from JRun to Tomcat, and we're having one large issue... When a JSP compile fails on the Tomcat Server, the log message just says that there was a failure, but doesn't say what the compiler error actually is. We can't seem to find any place where the actual compiler error is saved or logged. Is there any way to find the actual text of the compiler error so that we can track it down? Noel Rappin - 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: JSP Compiler output?
The log4j thing isn't working -- doesn't seem to have any impact. We're trying a clean tomcat build to see if we introduced a setting or a library somewhere that's causing the problem. Should we be expecting to see these messages at all? Tim Shaw wrote: When tools I use eat (or re-translate) messages I want, I tend to try getting the same behaviour without the tool ... Have you tried pre-compiling the JSP's? Tried, but are having trouble getting the ant task to recognize our tag libs. Noel G'luck tim Tim Funk wrote: In log4j - try turning up logging for jasper, (for example in log4j.properties) log4j.category.org.apache.jasper=info -Tim Noel Rappin wrote: The localhost file is there, but the JSP compiler messages are not winding up there -- we're getting a message in the app file saying that there was a compilation failure, but not the compiler message saying where and what the failure is. We're running on linux, log4j is in the application classpath, server.xml is writing to a log file for our application, but the message we're looking for is not getting there. I can't imagine how our webapp is eating the exception, but I suppose it's possible that log4j is dropping it on the floor somewhere along the way, but I can't figure out where that might be either. It's quite strange. Noel Tim Funk wrote: It should be somewhere into the $TOMCAT_HOME/logs/ directory. If its not ... - If your running windows service - is it in an event log? (guessing) - Is your server.xml writing to any other logs files? - Is your JSP/servlet/webapp /... eating the exception and not logging? (Which would be odd, since I would think this would always be logged) -Tim Noel Rappin wrote: I did. Doesn't seem to be there. Is there a setting I'm missing? Noel Tim Funk wrote: Check localhost_log.xxx -Tim Noel Rappin wrote: We're porting an application from JRun to Tomcat, and we're having one large issue... When a JSP compile fails on the Tomcat Server, the log message just says that there was a failure, but doesn't say what the compiler error actually is. We can't seem to find any place where the actual compiler error is saved or logged. Is there any way to find the actual text of the compiler error so that we can track it down? Noel Rappin - 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: JSP Compiler output?
Okay. I did a clean install of tomcat. I placed a compilation error in one of the example JSPs. I am now seeing this in the logs: * catalina.out: start/stop messages * localhost_examples: a stack trace saying that there was a JasperException: unable to compile class for JSP * localhost_log: messages about servlet loading. What I don't see is a message saying something useful about the compilation error -- like Compile failed on line 10, statement expected or some such. Are those messages just not generated? Noel Tim Funk wrote: Starting with a clean install looks like the way to go. Then add one jsp which contains a compile error and you'll see where the error messages go. From there - continue to add your components (piecewise if possible) and find the breaking point. -Tim Noel Rappin wrote: The log4j thing isn't working -- doesn't seem to have any impact. We're trying a clean tomcat build to see if we introduced a setting or a library somewhere that's causing the problem. Should we be expecting to see these messages at all? - 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: JSP Compiler output?
I replicated this experiment exactly in my environment. Tomcat 4.1.24, Linux, JSDK 1.4.1_01. Is it a Linux thing? Here's my stack trace in localhost: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:500) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:150) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:195) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) By the way, I really appreciate your time in helping with this. Noel Tim Funk wrote: You should get something somewhere. For example ... With 4.1.24 (win2k, jdk1.3, but 1.4 is the same result), I have a file called foo.jsp (at /) with the contents: % more cowbell % My error screen is attached. In the logs (localhost_log.2003-06-17.txt) I get: 2003-06-17 16:34:06 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Since fork is true, ignoring compiler setting. [javac] Compiling 1 source file [javac] Since fork is true, ignoring compiler setting. [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: ';' expected [javac] more cowbell [javac] ^ [javac] C:\opt\jakarta\tomcat4.1.24\work\Standalone\localhost\_\foo_jsp.java:41: cannot resolve symbol [javac] symbol : class more [javac] location: class org.apache.jsp.foo_jsp [javac] more cowbell [javac] ^ [javac] 2 errors at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130) ... -Tim Noel Rappin wrote: Okay. I did a clean install of tomcat. I placed a compilation error in one of the example JSPs. I am now seeing this in the logs: * catalina.out: start/stop messages * localhost_examples: a stack trace saying that there was a JasperException: unable to compile class for JSP * localhost_log: messages about servlet loading. What I don't see is a message saying something useful about the compilation error -- like Compile failed on line 10, statement expected or some such. Are those messages just not generated? Noel - 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]
Tomcat startup failure
I have a set up where tomcat is supposed to start on boot via an rc shell script on a Linux system (tomcat 4.1.18). I have this intermittent failure mode where tomcat fails to start up on reboot. I can _always_ trigger this failure by deleting all tomcat log files, and then rebooting. After the reboot, the only thing in the log directory is a zero-length catalina.out file, and the java process is not running. Invoking the tomcat startup again at this point causes it to work normally. I can find no evidence that the tomcat java process exits, and no matter how much I turn up debugging, I get no logged output. Is there any possible mechanism that could be causing this failure, or at least some place or some way I could get better debugging information? Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
