Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
On Thu, 2 Sep 2004 14:32:18 +0100, Allistair Crossley [EMAIL PROTECTED] wrote: Hi Guys Decided to give TC 5.5 / JDK 5 B2 a whirl today with our web application on my local machine and am having some teething troubles; 1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. Did you look at the generated source ? 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. Does everyone really think it's a good idea to have Context elements in server.xml ? 3/ None of my JNDI resources configured in tomcat.home/conf/Catalina/localhost/mywebapp.xml are being recognised. This was copied direct from my TC 5.0.25 installation ... should this still work? Database JAR is in common/lib. Getting lots of Cannot create JDBC driver of class '' for connect URL 'null' errors and also in STDOUT I noticed the ResourceLink element didn't work at all in 5.5.0: the digester rule was simply missing. Besides that, there could be an issue with the tweaked DBCP, but that would be surprising. WARNING: Error during context /mywebapp restart java.lang.NullPointerException at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1031) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1123) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:292) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.java:729) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1511) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1520) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1500) at java.lang.Thread.run(Thread.java:595) Which happens if the host doesn't have a child with that name, which is not normal. How can you possibly get that ? 4/ The logging suggestion at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/logger.html did not work for me. I have log4j.properties in my webapp classes ... does this override any other log4j config like in this example? That doc page is gone now (it was still linked from very few places). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. Did you look at the generated source ? No, I just removed the imports from my JSP that it was complaining about and it went away. Would you like me to put them back in and then look at the generated source for you? 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. Does everyone really think it's a good idea to have Context elements in server.xml ? I don't and I have not. This error occurred with an out of the box server.xml with _no_ Context elements. All I did was have ROOT and my own webapp in the webapps folder and then add mywebapp.xml into the conf/C/l/ folder. I think the clash came because my webapp using a path of which seems to be what ROOT tries to do also. Just removing ROOT from webapps sorts this out. 3/ None of my JNDI resources configured in tomcat.home/conf/Catalina/localhost/mywebapp.xml are being recognised. This was copied direct from my TC 5.0.25 installation ... should this still work? Database JAR is in common/lib. Getting lots of Cannot create JDBC driver of class '' for connect URL 'null' errors and also in STDOUT I noticed the ResourceLink element didn't work at all in 5.5.0: the digester rule was simply missing. Besides that, there could be an issue with the tweaked DBCP, but that would be surprising. Is there anything I can do to get Resources working in the meantime again or shall I wait for the next TC 5.5 release. Which happens if the host doesn't have a child with that name, which is not normal. How can you possibly get that ? No idea :) Like I say I have not touched the server.xml _one bit_ after installation. All I did was add my webapp into webapps and put its config file which just defines jndi resources into conf/C/l. 4/ The logging suggestion at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/logger. html did not work for me. I have log4j.properties in my webapp classes ... does this override any other log4j config like in this example? I'm going to try adding log4j.logger.org.apache.catalina.=debug, STDOUT into my webapp log4j and see what that does but first I need my webapp to work :) If I can be of any help please let me know what you want me to find out.. FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
I ran into the same issue with DBCP and JNDI. Jon - Original Message - From: Allistair Crossley [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, September 02, 2004 8:32 AM Subject: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) Hi Guys Decided to give TC 5.5 / JDK 5 B2 a whirl today with our web application on my local machine and am having some teething troubles; 1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. 3/ None of my JNDI resources configured in tomcat.home/conf/Catalina/localhost/mywebapp.xml are being recognised. This was copied direct from my TC 5.0.25 installation ... should this still work? Database JAR is in common/lib. Getting lots of Cannot create JDBC driver of class '' for connect URL 'null' errors and also in STDOUT WARNING: Error during context /mywebapp restart java.lang.NullPointerException at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1031) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1123) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:292) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.java:729) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1511) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1520) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1500) at java.lang.Thread.run(Thread.java:595) 4/ The logging suggestion at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/logger.html did not work for me. I have log4j.properties in my webapp classes ... does this override any other log4j config like in this example? Cheers for any insight into the JNDI problem :) ADC. FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - 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: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Quoting Allistair Crossley [EMAIL PROTECTED]: 4/ The logging suggestion at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/logger. html did not work for me. I have log4j.properties in my webapp classes ... does this override any other log4j config like in this example? I'm going to try adding log4j.logger.org.apache.catalina.=debug, STDOUT into my webapp log4j and see what that does but first I need my webapp to work :) If I can be of any help please let me know what you want me to find out.. There are two solutions to avoid having the Log4j config in common/classes be separate from your own webapp logging: 1. Include log4j.jar in WEB-INF/lib. This works because Tomcat implements servlet-spec recommended classloading behavior where webapps look locally first to find classes to load before looking to the parent. So, your app will be using one instance of Log4j while Tomcat itself will be using another. 2. Use a repository selector. This is more involved, but greatly simplified in Log4j-1.3 (not released yet). Tomcat could set a repository selector for all applications to use making solution #1 unnecessary. To do it on your own, see (Note that all referenced code supports Log4j-1.2.x, not 1.3 where the design and useage of repository selectors has changed significantly)... http://wiki.apache.org/logging-log4j/AppContainerLogging Jake - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Hi Remy, 1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. Did you look at the generated source ? No, I just removed the imports from my JSP that it was complaining about and it went away. Would you like me to put them back in and then look at the generated source for you? Were the imports not actually used if you were able to remove them without problems ? What was the error output ? (why do I have to ask this question ?) OK. The JSP in question is my error page (e.g isErrorPage=true) which prints out the exception in a more aesthetic manner. The reason this page was being thrown at me is because of all the other issues with the JNDI connectivity. Initially when I first started 5.5 the error message was a JasperException telling me that various package imports were not being used. Now, I never thought that was a crime (just not very good programming) but 5.5 decided to blow up because of these imports. Since the imports were not actually used, I decided to remove them from the JSP and this solved the error, and now I can see my nice error page - but remember I am seeing it in the first place because all my database connectivity is broken. I am guessing that as soon as JNDI is fixed and my webapp can proceed to fully start up, quite a number of my JSPs will break due to unused package imports. I am guessing this must be a change in Jasper because 5.0 was happy to render JSPs with unused package imports (as is any Java application code). 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. Does everyone really think it's a good idea to have Context elements in server.xml ? I don't and I have not. This error occurred with an out of the box server.xml with _no_ Context elements. All I did was have ROOT and my own webapp in the webapps folder and then add mywebapp.xml into the conf/C/l/ folder. I think the clash came because my webapp using a path of which seems to be what ROOT tries to do also. Just removing ROOT from webapps sorts this out. You really need to describe issues accurately (I always find your reports extremely weird, unfortunately). I think what you did is that you copied over your existing configuration, which will cause problems. I'm sorry you find my posts weird. I've been unlucky with some of the problems I have had with TC I guess. I do try and do everything properly. Here is an exact description of what I did to cause this problem including my stdout after starting TC. 1. Downloaded 5.5 as zip, installed Java 5 SDK 2. Unzipped to c:\jakarta-tomcat 3. Copied c:\jakarta-tomcat-5.0.25\conf\Catalina\localhost\iq.xml to c:\jakarta-tomcat-5.5.0\conf\Catalina\localhost\iq.xml (this iq.xml file is my web application. It contains my Context as the following header + all my JNDI resources ...) Context path= docBase=/iq reloadable=true 4. Copied c:\jakarta-tomcat-5.0.25\webapps\iq to c:\jakarta-tomcat\webapps\iq 5. Copied my database jTDS JAR into c:\jakarta-tomcat\common\lib\jtds.jar 6. Ran c:\jakarta-tomcat\bin\service.bat ensuring use of new Java 5 SDK 7. Started TC service. 8. Opened STDOUT log ... 02-Sep-2004 16:34:55 org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 02-Sep-2004 16:34:55 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1532 ms 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.0 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardHost start INFO: XML validation disabled **Start of LogManager static initializer *** configurationOptionStr=log4j.properties log4j:INFO Using URL [file:/C:/jakarta-tomcat/webapps/iq/WEB-INF/classes/log4j.properties] for automatic log4j configuration of repository named [default]. log4j:ERROR Could not find value for key log4j.appender.CoreLogicA log4j:ERROR Could not instantiate appender named CoreLogicA. log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender. log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-sys-email.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-stats-content-access.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender. log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-app-admin.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-sys-dto.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender. log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-app-holiday-forms.log
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
As regards the JasperException, I have just placed an unused package import to org.apache.struts back into my error page so that I can post it to you; org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The import org.apache.struts is never used org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84) org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:354) org.apache.jasper.compiler.Compiler.compile(Compiler.java:280) org.apache.jasper.compiler.Compiler.compile(Compiler.java:259) org.apache.jasper.compiler.Compiler.compile(Compiler.java:247) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:538) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:302) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:246) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:670) org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:637) org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:785) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:758) org.apache.jsp.layout.application_jsp._jspService(org.apache.jsp.layout.application_jsp:314) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:302) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:246) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069) org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:274) org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcessor.java:254) org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:309) org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279) org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) com.qas.newmedia.common.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:146) -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: 02 September 2004 16:15 To: Allistair Crossley Subject: Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) On Thu, 2 Sep 2004 15:11:38 +0100, Allistair Crossley [EMAIL PROTECTED] wrote: 1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. Did you look at the generated source ? No, I just removed the imports from my JSP that it was complaining about and it went away. Would you like me to put them back in and then look at the generated source for you? Were the imports not actually used if you were able to remove them without problems ? What was the error output ? (why do I have to ask this question ?) 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. Does everyone really think it's a good idea to have Context elements in server.xml ? I don't and I have not. This error occurred with an out of the box server.xml with _no_ Context elements. All I did was have ROOT and my own webapp in the webapps folder and then add mywebapp.xml into the conf/C/l/ folder. I think the clash came because my webapp using a path of which seems to be what ROOT tries to do also. Just removing ROOT from webapps sorts this out. You really need to describe issues accurately (I always find your reports extremely weird, unfortunately). I think what you did is that you copied over your existing configuration, which will cause problems. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com
Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
On Thu, 2 Sep 2004 16:41:14 +0100, Allistair Crossley [EMAIL PROTECTED] wrote: Hi Remy, 1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. Did you look at the generated source ? No, I just removed the imports from my JSP that it was complaining about and it went away. Would you like me to put them back in and then look at the generated source for you? Were the imports not actually used if you were able to remove them without problems ? What was the error output ? (why do I have to ask this question ?) OK. The JSP in question is my error page (e.g isErrorPage=true) which prints out the exception in a more aesthetic manner. The reason this page was being thrown at me is because of all the other issues with the JNDI connectivity. Initially when I first started 5.5 the error message was a JasperException telling me that various package imports were not being used. Now, I never thought that was a crime (just not very good programming) but 5.5 decided to blow up because of these imports. Since the imports were not actually used, I decided to remove them from the JSP and this solved the error, and now I can see my nice error page - but remember I am seeing it in the first place because all my database connectivity is broken. I am guessing that as soon as JNDI is fixed and my webapp can proceed to fully start up, quite a number of my JSPs will break due to unused package imports. I am guessing this must be a change in Jasper because 5.0 was happy to render JSPs with unused package imports (as is any Java application code). I think the warnings are interpreted as errors then. 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. Does everyone really think it's a good idea to have Context elements in server.xml ? I don't and I have not. This error occurred with an out of the box server.xml with _no_ Context elements. All I did was have ROOT and my own webapp in the webapps folder and then add mywebapp.xml into the conf/C/l/ folder. I think the clash came because my webapp using a path of which seems to be what ROOT tries to do also. Just removing ROOT from webapps sorts this out. You really need to describe issues accurately (I always find your reports extremely weird, unfortunately). I think what you did is that you copied over your existing configuration, which will cause problems. I'm sorry you find my posts weird. I've been unlucky with some of the problems I have had with TC I guess. I do try and do everything properly. Here is an exact description of what I did to cause this problem including my stdout after starting TC. 1. Downloaded 5.5 as zip, installed Java 5 SDK 2. Unzipped to c:\jakarta-tomcat 3. Copied c:\jakarta-tomcat-5.0.25\conf\Catalina\localhost\iq.xml to c:\jakarta-tomcat-5.5.0\conf\Catalina\localhost\iq.xml (this iq.xml file is my web application. It contains my Context as the following header + all my JNDI resources ...) Context path= docBase=/iq reloadable=true 4. Copied c:\jakarta-tomcat-5.0.25\webapps\iq to c:\jakarta-tomcat\webapps\iq 5. Copied my database jTDS JAR into c:\jakarta-tomcat\common\lib\jtds.jar 6. Ran c:\jakarta-tomcat\bin\service.bat ensuring use of new Java 5 SDK 7. Started TC service. 8. Opened STDOUT log ... 02-Sep-2004 16:34:55 org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 02-Sep-2004 16:34:55 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1532 ms 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.0 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardHost start INFO: XML validation disabled **Start of LogManager static initializer *** configurationOptionStr=log4j.properties log4j:INFO Using URL [file:/C:/jakarta-tomcat/webapps/iq/WEB-INF/classes/log4j.properties] for automatic log4j configuration of repository named [default]. log4j:ERROR Could not find value for key log4j.appender.CoreLogicA log4j:ERROR Could not instantiate appender named CoreLogicA. log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender. log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-sys-email.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-stats-content-access.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender. log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-app-admin.log log4j:INFO sdf is [EMAIL PROTECTED] log4j:INFO fileane is
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Did you change the jdk (vendor/version) ? As this looks more like an error message that's generated by the java compiler (jvac, jikes, ...). -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:47 PM To: Remy Maucherat; [EMAIL PROTECTED] Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) As regards the JasperException, I have just placed an unused package import to org.apache.struts back into my error page so that I can post it to you; org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The import org.apache.struts is never used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
yes, TC 5.5 needs Java 5.0 SDK. Remy also suggested privately that this must be the cause, that the warnings given by the compiler are being interpreted by Jasper as exceptions... About that, I think it's that the warnings are reported as issues by the compiler, and so Jasper thinks the compilation failed (new compiler = brand new integration = a few stupid bugs). ADC -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] Sent: 02 September 2004 17:05 To: Tomcat Users List Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) Did you change the jdk (vendor/version) ? As this looks more like an error message that's generated by the java compiler (jvac, jikes, ...). -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:47 PM To: Remy Maucherat; [EMAIL PROTECTED] Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) As regards the JasperException, I have just placed an unused package import to org.apache.struts back into my error page so that I can post it to you; org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The import org.apache.struts is never used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Hi, Well, Tomcat 5.5 uses the Eclipse JDT compiler for JSPs. I think we mistakenly treat the compiler warnings as errors in 5.5.0, and Remy's fixed it for 5.5.1. Yoav Shapira Millennium Research Informatics -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 12:05 PM To: Tomcat Users List Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) Did you change the jdk (vendor/version) ? As this looks more like an error message that's generated by the java compiler (jvac, jikes, ...). -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:47 PM To: Remy Maucherat; [EMAIL PROTECTED] Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) As regards the JasperException, I have just placed an unused package import to org.apache.struts back into my error page so that I can post it to you; org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The import org.apache.struts is never used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
:p cool, thanks Remy! ADC -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: 02 September 2004 17:01 To: [EMAIL PROTECTED] Subject: Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) On Thu, 2 Sep 2004 16:41:14 +0100, Allistair Crossley [EMAIL PROTECTED] wrote: Hi Remy, 1/ Jasper has an issue with JSP page imports where the imported packages are not used. This is throwing an exception. Did you look at the generated source ? No, I just removed the imports from my JSP that it was complaining about and it went away. Would you like me to put them back in and then look at the generated source for you? Were the imports not actually used if you were able to remove them without problems ? What was the error output ? (why do I have to ask this question ?) OK. The JSP in question is my error page (e.g isErrorPage=true) which prints out the exception in a more aesthetic manner. The reason this page was being thrown at me is because of all the other issues with the JNDI connectivity. Initially when I first started 5.5 the error message was a JasperException telling me that various package imports were not being used. Now, I never thought that was a crime (just not very good programming) but 5.5 decided to blow up because of these imports. Since the imports were not actually used, I decided to remove them from the JSP and this solved the error, and now I can see my nice error page - but remember I am seeing it in the first place because all my database connectivity is broken. I am guessing that as soon as JNDI is fixed and my webapp can proceed to fully start up, quite a number of my JSPs will break due to unused package imports. I am guessing this must be a change in Jasper because 5.0 was happy to render JSPs with unused package imports (as is any Java application code). I think the warnings are interpreted as errors then. 2/ Had the error mentioned earlier about ROOT child '' cannot be deployed because it was shared by another context. I just removed the ROOT folder from webapps to get rid of that problem. Does everyone really think it's a good idea to have Context elements in server.xml ? I don't and I have not. This error occurred with an out of the box server.xml with _no_ Context elements. All I did was have ROOT and my own webapp in the webapps folder and then add mywebapp.xml into the conf/C/l/ folder. I think the clash came because my webapp using a path of which seems to be what ROOT tries to do also. Just removing ROOT from webapps sorts this out. You really need to describe issues accurately (I always find your reports extremely weird, unfortunately). I think what you did is that you copied over your existing configuration, which will cause problems. I'm sorry you find my posts weird. I've been unlucky with some of the problems I have had with TC I guess. I do try and do everything properly. Here is an exact description of what I did to cause this problem including my stdout after starting TC. 1. Downloaded 5.5 as zip, installed Java 5 SDK 2. Unzipped to c:\jakarta-tomcat 3. Copied c:\jakarta-tomcat-5.0.25\conf\Catalina\localhost\iq.xml to c:\jakarta-tomcat-5.5.0\conf\Catalina\localhost\iq.xml (this iq.xml file is my web application. It contains my Context as the following header + all my JNDI resources ...) Context path= docBase=/iq reloadable=true 4. Copied c:\jakarta-tomcat-5.0.25\webapps\iq to c:\jakarta-tomcat\webapps\iq 5. Copied my database jTDS JAR into c:\jakarta-tomcat\common\lib\jtds.jar 6. Ran c:\jakarta-tomcat\bin\service.bat ensuring use of new Java 5 SDK 7. Started TC service. 8. Opened STDOUT log ... 02-Sep-2004 16:34:55 org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 02-Sep-2004 16:34:55 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1532 ms 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.0 02-Sep-2004 16:34:56 org.apache.catalina.core.StandardHost start INFO: XML validation disabled **Start of LogManager static initializer *** configurationOptionStr=log4j.properties log4j:INFO Using URL [file:/C:/jakarta-tomcat/webapps/iq/WEB-INF/classes/log4j.prop erties] for automatic log4j configuration of repository named [default]. log4j:ERROR Could not find value for key log4j.appender.CoreLogicA log4j:ERROR Could not instantiate appender named CoreLogicA. log4j:WARN No such property [datePattern] in org.apache.log4j.RollingFileAppender. log4j:INFO fileane is c:/jakarta-tomcat/logs/iq2-sys-email.log log4j:INFO sdf is [EMAIL PROTECTED
Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
On Thu, 2 Sep 2004 12:05:13 -0400, Shapira, Yoav [EMAIL PROTECTED] wrote: Hi, Well, Tomcat 5.5 uses the Eclipse JDT compiler for JSPs. I think we mistakenly treat the compiler warnings as errors in 5.5.0, and Remy's fixed it for 5.5.1. Right, it's fixed now. Thanks for the testing. -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Where can we get 5.5.1? Or 5.5 nightlies? .V Shapira, Yoav wrote: Hi, Well, Tomcat 5.5 uses the Eclipse JDT compiler for JSPs. I think we mistakenly treat the compiler warnings as errors in 5.5.0, and Remy's fixed it for 5.5.1. Yoav Shapira Millennium Research Informatics -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 12:05 PM To: Tomcat Users List Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) Did you change the jdk (vendor/version) ? As this looks more like an error message that's generated by the java compiler (jvac, jikes, ...). -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:47 PM To: Remy Maucherat; [EMAIL PROTECTED] Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) As regards the JasperException, I have just placed an unused package import to org.apache.struts back into my error page so that I can post it to you; org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The import org.apache.struts is never used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. -- Please post on Rich Internet Applications User Interface (RiA/SoA) http://www.portalvu.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Hi, It needs JRE 5.0 (not SDK or JDK, this is a big difference), and can run on 1.4. 5.5.1 is not out yet, give it a couple of days as we fix this first round of bugs reported for 5.5.0 and add more enhancements. Changes are being committed to CVS HEAD if you want to build a release yourself of course. For people who want nightlies or Gump builds, check http://cvs.apache.org/builds/jakarta-tomcat-5/nightly/ and http://brutus.apache.org/gump/public/buildLog.html, but you're on your own with these pretty much ;) Yoav Shapira Millennium Research Informatics -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 12:07 PM To: Tomcat Users List Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) yes, TC 5.5 needs Java 5.0 SDK. Remy also suggested privately that this must be the cause, that the warnings given by the compiler are being interpreted by Jasper as exceptions... About that, I think it's that the warnings are reported as issues by the compiler, and so Jasper thinks the compilation failed (new compiler = brand new integration = a few stupid bugs). ADC -Original Message- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED] Sent: 02 September 2004 17:05 To: Tomcat Users List Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) Did you change the jdk (vendor/version) ? As this looks more like an error message that's generated by the java compiler (jvac, jikes, ...). -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 5:47 PM To: Remy Maucherat; [EMAIL PROTECTED] Subject: RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) As regards the JasperException, I have just placed an unused package import to org.apache.struts back into my error page so that I can post it to you; org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The import org.apache.struts is never used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
On Thu, 02 Sep 2004 11:52:48 -0500, Vic [EMAIL PROTECTED] wrote: Where can we get 5.5.1? Or 5.5 nightlies? Don't worry: since this is heavy development mode, new binaries are going to be released often (unless Yoav doesn't have time to do the releases). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Hi, For this, I have time -- I figure on at least one release per week ;) But it's only been one day since 5.5.0 ;) Yoav Shapira Millennium Research Informatics -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 1:31 PM To: Tomcat Users List Subject: Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging) On Thu, 02 Sep 2004 11:52:48 -0500, Vic [EMAIL PROTECTED] wrote: Where can we get 5.5.1? Or 5.5 nightlies? Don't worry: since this is heavy development mode, new binaries are going to be released often (unless Yoav doesn't have time to do the releases). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC 5.5 - 4 issues (jasper, ROOT, jndi, logging)
Yes, but where? What URL? (the commons download link I think is for the 5.0 trunk? or is that 5.5?) .V ps: Thax tomcat team on very nice product! Remy Maucherat wrote: On Thu, 02 Sep 2004 11:52:48 -0500, Vic [EMAIL PROTECTED] wrote: Where can we get 5.5.1? Or 5.5 nightlies? Don't worry: since this is heavy development mode, new binaries are going to be released often (unless Yoav doesn't have time to do the releases). -- Please post on Rich Internet Applications User Interface (RiA/SoA) http://www.portalvu.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
