RE: canno startup Tomcat 4.0.1 - how to nobble JSP?
Hi, -Original Message- From: David Hewlett [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 26, 2002 11:33 PM To: Micael Padraig Og mac Grene Cc: Tomcat Users List Subject: Re: canno startup Tomcat 4.0.1 - how to nobble JSP? Micael, Since i do not intend to use jsp at all(there is much better technology e.g. webmacro) ...Q How to disable the initilisation of JSP? You can comment out jsp related sections in CATALINA_HOME/conf/web.xml (definition and mapping for jsp servlet) Thanks. for your support... Regards, David. Anton. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: canno startup Tomcat 4.0.1 - how to nobble JSP?
j2sdk1.4.0 was all that I needed to get Tomcat 4.0.1 or 4.0.2-b2 to work. Tomcat 4.0.2-b2 didn't work on the old JVM either, BTW. I'm going to stick wtih Tomcat 4.0.1. (BTW: Not sure what you mean by Tomcat 1.4, I'm assuming that it was a typo.) Thanks. -John Kalucki At 09:33 PM 1/26/2002 +, you wrote: Micael, After dowloading j2sdk1.4 and Tomcat 1.4 it worked straightaway! I can only conclude that a particular version pair was the cause and like i always join the slowest supermarket queue Admittedly these versions are all beta however this does not hurt me right now and i will proceed from here. Ah, there is one question you might no the answer to. Apparentely the only reason the jdk rather than the jre is used by Tomcat is in the support of jsp. Since i do not intend to use jsp at all(there is much better technology e.g. webmacro) ...Q How to disable the initilisation of JSP? Thanks. for your support... Regards, David. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: canno startup Tomcat 4.0.1 - how to nobble JSP?
Yes, of course a serious typo! it was of course 4.0.2-b2! I could have used 4.0.1 but decided it made sense to look ahead while i could. We may conclude then that something, unknown, didnt gel between jdk 1.3.1 and Tomcat and we will never know. I However i remain very curious as i know of happily working configuration with just 1.3.1 that worked and continue to work just fine!! And judging by the reports this failure has been see on more than one version of unix too. Ah, i see that nobody has risen to my comment on JSP. Seriously i would like to avoid initiating JSP not because i would prefer to work under the runtime (but of course i would) but because GENUINELY i won't use it. If anybody, with an open mind that is, would like to look at the competing templating technology (see for example: webmacro.org. ) It makes a true separation of the art of web design and the server side java developer: who no longer need to be one subserviated to the other, nor a need to use up valuable development time by needing to sit down together anything like as much! Regards, Dave. On Sunday 27 January 2002 5:17 pm, you wrote: j2sdk1.4.0 was all that I needed to get Tomcat 4.0.1 or 4.0.2-b2 to work. Tomcat 4.0.2-b2 didn't work on the old JVM either, BTW. I'm going to stick wtih Tomcat 4.0.1. (BTW: Not sure what you mean by Tomcat 1.4, I'm assuming that it was a typo.) Thanks. -John Kalucki At 09:33 PM 1/26/2002 +, you wrote: Micael, After dowloading j2sdk1.4 and Tomcat 1.4 it worked straightaway! I can only conclude that a particular version pair was the cause and like i always join the slowest supermarket queue Admittedly these versions are all beta however this does not hurt me right now and i will proceed from here. Ah, there is one question you might no the answer to. Apparentely the only reason the jdk rather than the jre is used by Tomcat is in the support of jsp. Since i do not intend to use jsp at all(there is much better technology e.g. webmacro) ...Q How to disable the initilisation of JSP? Thanks. for your support... Regards, David. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: canno startup Tomcat 4.0.1 - how to nobble JSP?
Hi, David, I don't know why you hate jsp, and respect your decision. But, I find jsp is the cat's meow for me. I employ the taglibs extensively and love the results. Prior to developing my taglibs, I used a home made post controller filter interface Page which was just String [] processRequest(Request req, Response res) which made life with jsp really easy. There are many ways to skin a Tomcat. Micael -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: canno startup Tomcat 4.0.1 - how to nobble JSP?
Micael, After dowloading j2sdk1.4 and Tomcat 1.4 it worked straightaway! I can only conclude that a particular version pair was the cause and like i always join the slowest supermarket queue Admittedly these versions are all beta however this does not hurt me right now and i will proceed from here. Ah, there is one question you might no the answer to. Apparentely the only reason the jdk rather than the jre is used by Tomcat is in the support of jsp. Since i do not intend to use jsp at all(there is much better technology e.g. webmacro) ...Q How to disable the initilisation of JSP? Thanks. for your support... Regards, David. On Friday 25 January 2002 7:57 am, you wrote: I downloaded a new copy of Tomcat and the problems disappeared. At 11:40 AM 1/22/02 +, you wrote: Despite the good advice to carefully go through the documentation again the 'problem' still persists : It appears neither to start nor to fail? glibc version is 2.2.4-21 jdk is 1.3.1 i have set: ulimit -s 2048 and: export LD_ASSUME_KERNEL=2.2.5 I see i am not alone as two others report similar problem. Yet a colleague of mine on, i am quite sure, the same level of suse 7.3 jdk etc has succeeded immediately. The only known difference is that my colleague has made a clean install while mine was an upgrade from 7.2 Q. Can there be a remnant from an older installation of tomcat that could be the cause? The log for the startup gives just a one line comment as follows: 2002-01-22 09:55:43 HttpConnector Opening server socket on all host IP addresses but their is no reported failure! Indeed an active process is created. but despite the implication tht it is listening on the specified port an http request cannot connect to the port. (Other ports are working fine. e.g apache/jserv) I have also tried setting another unused port other than 8080 to no avail... The problem appears to be something more basic? Regards, David. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: canno startup Tomcat 4.0.1
On Friday 25 January 2002 7:57 am, you wrote: I downloaded a new copy of Tomcat and the problems disappeared. Thanks, I will try the same. At 11:40 AM 1/22/02 +, you wrote: Despite the good advice to carefully go through the documentation again the 'problem' still persists : It appears neither to start nor to fail? glibc version is 2.2.4-21 jdk is 1.3.1 i have set: ulimit -s 2048 and: export LD_ASSUME_KERNEL=2.2.5 I see i am not alone as two others report similar problem. Yet a colleague of mine on, i am quite sure, the same level of suse 7.3 jdk etc has succeeded immediately. The only known difference is that my colleague has made a clean install while mine was an upgrade from 7.2 Q. Can there be a remnant from an older installation of tomcat that could be the cause? The log for the startup gives just a one line comment as follows: 2002-01-22 09:55:43 HttpConnector Opening server socket on all host IP addresses but their is no reported failure! Indeed an active process is created. but despite the implication tht it is listening on the specified port an http request cannot connect to the port. (Other ports are working fine. e.g apache/jserv) I have also tried setting another unused port other than 8080 to no avail... The problem appears to be something more basic? Regards, David. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
re: canno startup Tomcat 4.0.1
I downloaded a new copy of Tomcat and the problems disappeared. At 11:40 AM 1/22/02 +, you wrote: Despite the good advice to carefully go through the documentation again the 'problem' still persists : It appears neither to start nor to fail? glibc version is 2.2.4-21 jdk is 1.3.1 i have set: ulimit -s 2048 and: export LD_ASSUME_KERNEL=2.2.5 I see i am not alone as two others report similar problem. Yet a colleague of mine on, i am quite sure, the same level of suse 7.3 jdk etc has succeeded immediately. The only known difference is that my colleague has made a clean install while mine was an upgrade from 7.2 Q. Can there be a remnant from an older installation of tomcat that could be the cause? The log for the startup gives just a one line comment as follows: 2002-01-22 09:55:43 HttpConnector Opening server socket on all host IP addresses but their is no reported failure! Indeed an active process is created. but despite the implication tht it is listening on the specified port an http request cannot connect to the port. (Other ports are working fine. e.g apache/jserv) I have also tried setting another unused port other than 8080 to no avail... The problem appears to be something more basic? Regards, David. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
re: canno startup Tomcat 4.0.1
Despite the good advice to carefully go through the documentation again the 'problem' still persists : It appears neither to start nor to fail? glibc version is 2.2.4-21 jdk is 1.3.1 i have set: ulimit -s 2048 and: export LD_ASSUME_KERNEL=2.2.5 I see i am not alone as two others report similar problem. Yet a colleague of mine on, i am quite sure, the same level of suse 7.3 jdk etc has succeeded immediately. The only known difference is that my colleague has made a clean install while mine was an upgrade from 7.2 Q. Can there be a remnant from an older installation of tomcat that could be the cause? The log for the startup gives just a one line comment as follows: 2002-01-22 09:55:43 HttpConnector Opening server socket on all host IP addresses but their is no reported failure! Indeed an active process is created. but despite the implication tht it is listening on the specified port an http request cannot connect to the port. (Other ports are working fine. e.g apache/jserv) I have also tried setting another unused port other than 8080 to no avail... The problem appears to be something more basic? Regards, David. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
