Logging.properties not found
We use Tomcat 5.5.23 on all platforms (Solaris, Linux and Win XP). On Solaris, I see the following message when Tomcat is shutdown. ./shutdown.sh: -Djava.util.logging.config.file=/export/home/lakshmi/Tomcat/conf/logging .properties: not found Here is an excerpt from the shutdown script: -- BEGIN EXCERPT - MAINCLASS=org.apache.catalina.startup.Bootstrap export MAINCLASS ACTION=stop export ACTION JAVA_OPTS=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogMana ger -Djava.util.logging.config.file="$CATALINA_BASE/conf/logging.properties" export JAVA_OPTS LD_LIBRARY_PATH=$CATALINA_HOME/bin:$CATALINA_HOME/libexec:$CATALINA_HOME /conf:$LD_LIBRARY_PATH export $LD_LIBRARY_PATH PATH=$CATALINA_HOME/bin:$INM_HOME/bin:$CATALINA_HOME/conf:$PATH export $PATH CLASSPATH includes $CATALINA_HOME/conf/logging.properties $JAVA_HOME/bin/java $JAVA_OPTS -Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" -classpath "$CLASSPATH" -Dcatalina.base="$CATALINA_BASE" -Dcatalina.home="$CATALINA_HOME" -Djava.io.tmpdir="$CATALINA_TMPDIR" $MAINCLASS $ACTION - END EXCERPT As you can see, $PATH, $LD_LIBRARY_PATH, $CLASSPATH all point to $CATALINA_HOME/conf location. Any clue why the message about logging.properties not being found is printed? Thanks Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Installing APR on Fedora
/usr/local/apr/lib should be in your LD_LIBRARY_PATH. --Lakshmi -Original Message- From: Ole Ersoy [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 2:47 PM To: Tomcat Users List Subject: Re: Installing APR on Fedora Hi Rainer and Filip, Could tcnative.so be called something else? I ran this: find / -name tcnative*.so and it came up blank. I tried find / -name *tc*.so And it finds: /home/ole/Desktop/tomcat-6.0.14/bin/tomcat-native-1.1.10-src/jni/native/ .libs/libtcnative-1.so /usr/local/apr/lib/libtcnative-1.so I ran: ldd /usr/local/apr/lib/libtcnative-1.so all the dependencies returned are in /lib or /usr/lib and there were no missing dependencies. I figured I'd give it a try with the libtcnative-1.so, so I updated the catalina classpath like this: CLASSPATH="/usr/local/apr/lib":"$CLASSPATH":"$CATALINA_HOME"/bin/bootstr ap.jar:"$CATALINA_HOME"/bin/commons-logging-api.jar However it seems like catalina is not using the CLASSPATH when looking for the library because I still get this: Aug 16, 2007 4:37:21 PM org.apache.catalina.core.AprLifecycleListener init INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-sun-1.6.0.1/jre/lib/i386/client:/usr/lib/jvm/jav a-1.6.0-sun-1.6.0.1/jre/lib/i386:/usr/lib/jvm/java-1.6.0-sun-1.6.0.1/jre /../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib Thoughts? Thanks again for all the super help! - Ole Rainer Jung wrote: > Where do you put tcnative.so? > > And: if you do ldd PATH_TO_TCNATIVE/tcnative.so: are there any > dependencies shown, which do not lie in /lib or /usr/lib, or which ldd > can not resolve? If yes: which libraries, and which path resp. which > libraries without path? Maybe just post the result of the ldd command. > > Ole Ersoy wrote: >> Hi Rainer, >> >> Thanks again for that great fix. When I fired up Tomcat, I still get >> this message: >> Aug 16, 2007 9:53:05 AM org.apache.catalina.core.AprLifecycleListener >> init >> INFO: The Apache Tomcat Native library which allows optimal >> performance in production environments was not found on the >> java.library.path: >> /usr/lib/jvm/java-1.6.0-sun-1.6.0.1/jre/lib/i386/client:/usr/lib/jvm/ >> java-1.6.0-sun-1.6.0.1/jre/lib/i386:/usr/lib/jvm/java-1.6.0-sun-1.6.0 >> .1/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib >> >> >> I read in a post that adding /lib and /usr/lib/ to the classpath >> would take care of it, but I must be missing something else as well. >> Any ideas? >> >> Thanks again, >> - Ole > > - > To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, > e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [SOLVED]Tomcat native library Not found in Solaris 9
Hi Rainer, Thanks for your suggestion! Using the specs file as suggested below did not work. Also, gcc -dumpspecs > /path/myspecs and then changing the *libgcc rule did not work either. What finally worked was export CC="gcc -static-libgcc" But then I had to recompile OpenSSL, APR and then Tomcat native in that order with the above value for CC to completely remove the dependency on libgcc_s.so. So now I have libssl.so, libcrypto.so, libapr-1.so and libtcnative-1.so without the dependency on libgcc_s.so. Thanks Lakshmi -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 2:20 AM To: Tomcat Users List Subject: Re: [NOT SOLVED]Tomcat native library Not found in Solaris 9 Hi, first of all: this is a gcc question. If you search for a high quality answer, you should contact the gcc commmunity. My personal way to do this (and there is definitely more than one wait to do it): export CC="gcc -specs=/path/to/my/specs" Contents of file /path/to/my/specs: *libgcc: -lgcc -lgcc_eh Now whenever you use a build system, that respects the CC env variable (e.g. most configure based systems), libgcc should get compiled in statically. Regards, Rainer Lakshmi Venkataraman wrote: > Please give me some tips for compiling libtcnative on Solaris 9 > without the dynamic dependence on libgcc_s.1.so. We ship tomcat with > our product. On customer installations, we cannot assume that > libgcc_s will be found in some standard location. > > I have searched a lot on the web. I am also trying to compile gcc with > --disable-shared option. > I am running into some issues while trying to compile gcc. > 1) How to modify Tomcat native's configure script to link libgcc > statically? > 2) What are the prerequisites before doing step 1)? > > We are using Tomcat 5.5.23. I am using tcnative-1.1.8-src with > OpenSSL-0.9.8b. > > --Thanks > Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [NOT SOLVED]Tomcat native library Not found in Solaris 9
Thanks for your reply! I will try the steps suggested below. Lakshmi -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 2:20 AM To: Tomcat Users List Subject: Re: [NOT SOLVED]Tomcat native library Not found in Solaris 9 Hi, first of all: this is a gcc question. If you search for a high quality answer, you should contact the gcc commmunity. My personal way to do this (and there is definitely more than one wait to do it): export CC="gcc -specs=/path/to/my/specs" Contents of file /path/to/my/specs: *libgcc: -lgcc -lgcc_eh Now whenever you use a build system, that respects the CC env variable (e.g. most configure based systems), libgcc should get compiled in statically. Regards, Rainer Lakshmi Venkataraman wrote: > Please give me some tips for compiling libtcnative on Solaris 9 > without the dynamic dependence on libgcc_s.1.so. We ship tomcat with > our product. On customer installations, we cannot assume that > libgcc_s will be found in some standard location. > > I have searched a lot on the web. I am also trying to compile gcc with > --disable-shared option. > I am running into some issues while trying to compile gcc. > 1) How to modify Tomcat native's configure script to link libgcc > statically? > 2) What are the prerequisites before doing step 1)? > > We are using Tomcat 5.5.23. I am using tcnative-1.1.8-src with > OpenSSL-0.9.8b. > > --Thanks > Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [NOT SOLVED]Tomcat native library Not found in Solaris 9
Please give me some tips for compiling libtcnative on Solaris 9 without the dynamic dependence on libgcc_s.1.so. We ship tomcat with our product. On customer installations, we cannot assume that libgcc_s will be found in some standard location. I have searched a lot on the web. I am also trying to compile gcc with --disable-shared option. I am running into some issues while trying to compile gcc. 1) How to modify Tomcat native's configure script to link libgcc statically? 2) What are the prerequisites before doing step 1)? We are using Tomcat 5.5.23. I am using tcnative-1.1.8-src with OpenSSL-0.9.8b. --Thanks Lakshmi -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Sunday, May 13, 2007 1:45 AM To: Tomcat Users List Subject: Re: [SOLVED]Tomcat native library Not found in Solaris 9 It's very likely, that it depends on the same lib in RedHat. You can check by using "ldd libtcnative-1.so". The difference is: gcc is a fundamental part of the OS with Linux, so libgcc_s.so is ususally installed in a standard library location for Linux. Under Solaris it's an optional add-on installed in a separate place. Personally I always find it anoying, that gcc put's a dependency on its own runtime lib into the compiled code. You could prevent it doing so, by changing its specs file (tehreby compiling in its convenience routines statically). Regards, Rainer Lakshmi Venkataraman wrote: > > I attached an eclipse debugger and found that an UnsatsfiedLinkError > was thrown due to the Fact that libtcnative-1.so depends on > libgcc_s.1.so. > Then I included /usr/local/lib in LD_LIBRAY_PATH. > Tomcat's Http11AprProtocol connector starts up without any problem. > > It is still not clear why on solaris 9 libtcnative-1.so depends on > libgcc_s.1.so Whereas in Lunux redhat 4 it does NOT do do. > > Lakshmi > > -Original Message- > From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 12, 2007 5:33 PM > To: Tomcat Users List > Subject: RE: Tomcat native library Not found in Solaris 9 > > > > I upgraded Tomcat to Tomcat 5.5.23 on Solaris 9. I also compiled > APR-1.2.8, tomcat-native-1.1.8-src and openssl-0.9.8b on Solaris. > I have placed the libtcnative-1.so in /export/home/lakshmi/Ivt55/bin. > Ivt55 is the application directory and have INCLUDED it in > LD_LIBRARY_PATH and PATH. > > Yet Tomcat is unable to find libtcnative-1.so. I get this message: > > The Apache Tomcat Native library which allows optimal performance in > production environments was not found on the java.library.path: > /export/home/lakshmi/Ivt55/jre/lib/sparc/client:/export/home/lakshmi/I > vt > 55/jre/lib/sparc:/export/home/lakshmi/Ivt55/jre/../lib/sparc:/export/h > om > e/lakshmi/Ivt55/3rdPartyPackages/Tomcat/bin:/export/home/lakshmi/Ivt55 > /b in:/export/home/lakshmi/Ivt55/database::/usr/lib > > > I did NOT have a problem on Linux redhat 4 or Windows. > > What else is missing on Solaris? > > Thanks in advance for your reply, > Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache Portable Runtime
You have to compile libtcnative as well. In addition to the documentation mentioned by Rainer, also look in the archives for the threads "Tomcat native library Not found in Solaris 9" and "Tomcat 5.5, IPv6, APR, HTTP and HTTPS" Lakshmi -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 9:22 AM To: Tomcat Users List Subject: Re: Apache Portable Runtime The APR libs are not enough for the APR connector. Have a look at http://tomcat.apache.org/tomcat-5.5-doc/apr.html Regards, Rainer James Rome wrote: > When Tomcat starts, I get: > Jul 27, 2007 10:06:11 AM org.apache.catalina.core.AprLifecycleListener > lifecycleEvent > INFO: The Apache Tomcat Native library which allows optimal > performance in production environments was not found on the java.library.path: > /usr/lib/jvm/java-1.5.0-sun-1.5.0_12/jre/lib/i386/client:/usr/lib/jvm/ > java-1.5.0-sun-1.5.0_12/jre/lib/i386:/usr/lib/jvm/java-1.5.0-sun-1.5.0 > _12/jre/../lib/i386 > > I have libapr1.so in /usr/lib, and I copied it to the above i386 > directory, but Tomcat still does not see it. > > How do I get Tomcat to see this. Or is it looking for something else? > > Thanks, > Jim Rome - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Windows Native lib
Okay, I am glad that 1.1.7-ipv4 is working. 1.1.9 would have worked with the "address=0.0.0.0" attribute since it is the IPv6 version. A README file in http://tomcat.heanet.ie/native/ would have been helpful. IPv4 is the 32 bit IP address of a device(computer, router etc.), for example 192.1.1.1. Since the world is running out of IPv4 addresses, IPv6 is the new standard with 128 bit address space. http://www.ipv6.org/ >From your mail, it seems you are on IPv4, so you don't have to worry about IPv6. Yes, the Tomcat folks could have done a little more on APR documentation. I spent a few days unravelling everything on all 3 OS - Windows, Solaris, Linux. Everything had to work in my organization - HTTPS and HTTP transport over both IPv4 and IPv6 on all the 3 OS. So I documented my experience in the posting "Tomcat 5.5, APR, IPv6, HTTP and HTTPS". I was hoping either Mark Thomas or Mladen Turk would comment on my post, update some document or delve into why 1.1.10 gives the errors that are not present when any of the earlier versions were used. But there was no discussion on this thread and I have moved on with my working combination. Lakshmi -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 5:45 PM To: 'Tomcat Users List' Subject: RE: Windows Native lib Ok, say have downloaded version 1.1.7/tcnative-1-ipv4.dll and renamed it as tcnative-1.dll without changing anything else. Now everything seems to work ok - ie no more exceptions. So what is the difference between ipv4 and ipv6 and why dont later versions mention them. They just DONT work so why have they been released? c -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: 26 June 2007 01:29 To: 'Tomcat Users List' Subject: RE: Windows Native lib Lakshmi, Thanks for the reply. If what you say is true then this 'feature' of Tomcat is obviously beyond the understanding of us 'mere mortals'. I have an application to maintain without having to get to grips with the detailed ins-and-outs of the guts of each Web/App/EJB server, etc, that I'm runing on. What an 'ipv4' is, and how it compares to an 'ipv6', is quite frankly too dull to explore. I had just assumed that there was a dll that replaced parts of the java Tomcat runtime and hence ran faster. Either it was loaded and 'stuff' ran faster, or it wasn't and 'stuff' went more slowly. Call me naive. Why have they released version 1.1.10 if it 'just does not work'? I don't think that I'm trying to do anything weird - I'm just trying to deploy a WAR file. So if you, or anyone else, can advise the exact details of how to make this 'plug-in' actually 'plug in' then great. Sorry - this isn't a rant - and its not aimed at anyone. But how do you install the native stuff on 5.5.23 for Windows - surely someone has done it! Some simple instructions from someone please! C -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: 25 June 2007 23:03 To: Tomcat Users List Subject: RE: Windows Native lib No, don't try 1.1.0. I had problems with it on all platforms. I compiled the source on Solaris and Linux. If 1.1.9 does not work, check your server.xml configuration file for your connector. Use address ="0.0.0.0" atribute if you care for Ipv4 only. Please refer to my posting to this group on 05/22 under the heading "Tomcat 5.5, APR, IPv6, HTTP,HTTPS" Upto 1.1.8, whether the tcnative.dll is ipv4 version or ipv6 is mentioned as part of the name. If you want both to work you have to download the ipv6 version and specify two connector elements with appropriate address attributes. Lakshmi -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 2:41 PM To: 'Tomcat Users List' Subject: RE: Windows Native lib Due to the ascii sorted list on a volume then the last entry in http://tomcat.heanet.ie/native/ is actually Version 1.1.9 - and so this is the version I actually have tried, not 1.1.10. OK - so you will now say 'try version 1.1.10' - which I've done and it gives exactly the same exception. Aaargh. -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: 25 June 2007 22:23 To: Tomcat Users List Subject: RE: Windows Native lib >From my own experience documented in my postings to this group under >the subject heading: "Tomcat 5.5, IPv6, APR, HTTP,HTTPS", tcnative-1.1.10 does not work properly. Please try tcnative-1.1.8 or tcnative-1.1.9. --Lakshmi -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 2:04 PM To: 'Tomcat Users List' Subject: RE: Windows Native lib Hi Nathan, Yep: http://tomcat.heanet.ie/native/ is where I do
RE: Windows Native lib
No, don't try 1.1.0. I had problems with it on all platforms. I compiled the source on Solaris and Linux. If 1.1.9 does not work, check your server.xml configuration file for your connector. Use address ="0.0.0.0" atribute if you care for Ipv4 only. Please refer to my posting to this group on 05/22 under the heading "Tomcat 5.5, APR, IPv6, HTTP,HTTPS" Upto 1.1.8, whether the tcnative.dll is ipv4 version or ipv6 is mentioned as part of the name. If you want both to work you have to download the ipv6 version and specify two connector elements with appropriate address attributes. Lakshmi -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 2:41 PM To: 'Tomcat Users List' Subject: RE: Windows Native lib Due to the ascii sorted list on a volume then the last entry in http://tomcat.heanet.ie/native/ is actually Version 1.1.9 - and so this is the version I actually have tried, not 1.1.10. OK - so you will now say 'try version 1.1.10' - which I've done and it gives exactly the same exception. Aaargh. -----Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: 25 June 2007 22:23 To: Tomcat Users List Subject: RE: Windows Native lib >From my own experience documented in my postings to this group under >the subject heading: "Tomcat 5.5, IPv6, APR, HTTP,HTTPS", tcnative-1.1.10 does not work properly. Please try tcnative-1.1.8 or tcnative-1.1.9. --Lakshmi -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 2:04 PM To: 'Tomcat Users List' Subject: RE: Windows Native lib Hi Nathan, Yep: http://tomcat.heanet.ie/native/ is where I downloaded the tcnative-1.dll and openssl.exe from before. And these downloads give me the Tomcat runtime error mentioned in my original email. So if the downloads are correct - then what else can cause the '730047' error code ? -Original Message- From: Nathan Hook [mailto:[EMAIL PROTECTED] Sent: 25 June 2007 22:02 To: users@tomcat.apache.org Subject: RE: Windows Native lib To get rid of this error message and speed up Tomcat just a small amount you need to install the tcnative-1.dll You can find this .dll file at: http://tomcat.apache.org/tomcat-5.5-doc/apr.html The link to the download area is: http://tomcat.heanet.ie/native/ You will then want to get the latest version and place it in your $TOMCAT_HOME/bin directory. Original Message Follows From: "Clive Webster" <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" To: Subject: Windows Native lib Date: Mon, 25 Jun 2007 21:55:10 +0100 Have spent the last 8 hours trying to work out how to use the 'native' library for Tomcat 5.5.23 - without any success. Have managed to download lots of C++ source code - which is useless since I don't have an MS C++ compiler and don't want to buy one as I live in a Java world not a C++ world !!! Further digging revealed binaries for 'tcnative-1.dll' and 'openssl.exe' but having put these onto my PATH then I no longer get the warning re not using the native stuff but instead I get:- SEVERE: Error initializing endpoint java.lang.Exception: Socket bind failed: [730047] An address incompatible with the requested protocol was used. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:576) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:1 16) at org.apache.catalina.connector.Connector.initialize(Connector.java:1017) at org.apache.catalina.core.StandardService.initialize(StandardService.java :578 ) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:7 82) at org.apache.catalina.startup.Catalina.load(Catalina.java:504) at org.apache.catalina.startup.Catalina.load(Catalina.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:267) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Have Googled error code 730047 and got 3 answers (including 2 in Japanese) - no help there. Does anyone know how to make this work? (Sorry - not meant to sound rude, but am starting to get a bit frustrated having gone round in circles for a day!). Apologies if the answer is 'obvious' but have searched FAQs etc etc to no end. Small point - but since the 'native lib' is much hyped in the docs then why is it so bloomin hard to find a download for it that is deployable !! Got Tomcat itself working in a few minutes.
RE: Windows Native lib
>From my own experience documented in my postings to this group under the subject heading: "Tomcat 5.5, IPv6, APR, HTTP,HTTPS", tcnative-1.1.10 does not work properly. Please try tcnative-1.1.8 or tcnative-1.1.9. --Lakshmi -Original Message- From: Clive Webster [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 2:04 PM To: 'Tomcat Users List' Subject: RE: Windows Native lib Hi Nathan, Yep: http://tomcat.heanet.ie/native/ is where I downloaded the tcnative-1.dll and openssl.exe from before. And these downloads give me the Tomcat runtime error mentioned in my original email. So if the downloads are correct - then what else can cause the '730047' error code ? -Original Message- From: Nathan Hook [mailto:[EMAIL PROTECTED] Sent: 25 June 2007 22:02 To: users@tomcat.apache.org Subject: RE: Windows Native lib To get rid of this error message and speed up Tomcat just a small amount you need to install the tcnative-1.dll You can find this .dll file at: http://tomcat.apache.org/tomcat-5.5-doc/apr.html The link to the download area is: http://tomcat.heanet.ie/native/ You will then want to get the latest version and place it in your $TOMCAT_HOME/bin directory. Original Message Follows From: "Clive Webster" <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" To: Subject: Windows Native lib Date: Mon, 25 Jun 2007 21:55:10 +0100 Have spent the last 8 hours trying to work out how to use the 'native' library for Tomcat 5.5.23 - without any success. Have managed to download lots of C++ source code - which is useless since I don't have an MS C++ compiler and don't want to buy one as I live in a Java world not a C++ world !!! Further digging revealed binaries for 'tcnative-1.dll' and 'openssl.exe' but having put these onto my PATH then I no longer get the warning re not using the native stuff but instead I get:- SEVERE: Error initializing endpoint java.lang.Exception: Socket bind failed: [730047] An address incompatible with the requested protocol was used. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:576) at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:1 16) at org.apache.catalina.connector.Connector.initialize(Connector.java:1017) at org.apache.catalina.core.StandardService.initialize(StandardService.java :578 ) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:7 82) at org.apache.catalina.startup.Catalina.load(Catalina.java:504) at org.apache.catalina.startup.Catalina.load(Catalina.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:267) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Have Googled error code 730047 and got 3 answers (including 2 in Japanese) - no help there. Does anyone know how to make this work? (Sorry - not meant to sound rude, but am starting to get a bit frustrated having gone round in circles for a day!). Apologies if the answer is 'obvious' but have searched FAQs etc etc to no end. Small point - but since the 'native lib' is much hyped in the docs then why is it so bloomin hard to find a download for it that is deployable !! Got Tomcat itself working in a few minutes. All help greatfully received. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Make every IM count. Download Messenger and join the i'm Initiative now. It's free. http://im.live.com/messenger/im/home/?source=TAGHM_June07 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 6 jsp compilation
One of the things to do is to ensure that you have app specific web.xml placed in an appropriate location. This web.xml must have and defined for every precompiled jsp file as follows: ImageImport jsp.imageupload ImageImport /jsp/imageupload.jsp --Lakshmi -Original Message- From: Manca Davide [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 8:37 AM To: Tomcat Users List Subject: Tomcat 6 jsp compilation Hello, how can I say to Tomcat 6 to NOT compile jsp into .class files? This because we have more machines with a Tomcat 6 each one and they should read a read-only nfs file system in which we have precompiled .class files. Thank you. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ServletContextListener
-Original Message- From: lightbulb432 [mailto:[EMAIL PROTECTED] Sent: Saturday, June 09, 2007 10:30 AM To: users@tomcat.apache.org Subject: ServletContextListener >Can requests potentially arrive at a servlet before the ServletContextListener's contextInitialized method has >completed? I ask because the method occurs as a notification once the servlet context is ready to accept requests. >Is there a chance, then, that a request could begin being served while your contextInitialized method is being >carried out (especially if it's long-running)? >Is contextInitialized suitable only for things like logging the fact that a context is ready, or can it be used for >setup that MUST occur before the first request is accepted? If not the latter, what can be used to serve this >function? ContextInitialized can be used for setting up various services in the backend before accepting the first request. --lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Javac instead of JDT to compile JSPs
CORRECTION: In step 5, I mean and NOT . -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 4:41 PM To: Tomcat Users List Subject: RE: Using Javac instead of JDT to compile JSPs I have been successfully using something other than Jasper in my development enviroment. This is what I did: 1) Remove jasper-compiler-jdt.jar from /common/lib 2) Add /lib/tools.jar in /common/lib 3) Add ant.jar also to /common/lib. The ant.jat that was compatible with Tomcat5.5.23 was apache-ant-1.6/lib/ant.jar 4) Make sure the application specific web.xml does NOT have any and MAPPINGS for the JSPs that need to be compiled on the fly. If these mappings exist, Tomcat 5.5.23 tries to look for precompiled classes. 5) In my /conf/web.xml which is the global web.xml, I have the following to enable compilation. jsp org.apache.jasper.servlet.JspServlet fork false xpoweredBy false compilerTargetVM 1.5 compilerSourceVM 1.5 3 Hope that helps Lakshmi -Original Message- From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 9:29 AM To: 'Tomcat Users List' Subject: Using Javac instead of JDT to compile JSPs Has anyone tried to get the jasper compiler to be something other than the JDT? I tried several things, each of them not working. The docs say an alternative compiler can be specified, but makes no mention of how to specify it. This seems to be controlled by settings in the web.xml. Below is a part of my web.xml from my latest try (which failed). Thanks, Mark web.xml section --- jsp org.apache.jasper.servlet.JspServlet compiler com.sun.tools.javac.main.JavaCompiler fork true xpoweredBy false 3 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Javac instead of JDT to compile JSPs
I have been successfully using something other than Jasper in my development enviroment. This is what I did: 1) Remove jasper-compiler-jdt.jar from /common/lib 2) Add /lib/tools.jar in /common/lib 3) Add ant.jar also to /common/lib. The ant.jat that was compatible with Tomcat5.5.23 was apache-ant-1.6/lib/ant.jar 4) Make sure the application specific web.xml does NOT have any and MAPPINGS for the JSPs that need to be compiled on the fly. If these mappings exist, Tomcat 5.5.23 tries to look for precompiled classes. 5) In my /conf/web.xml which is the global web.xml, I have the following to enable compilation. jsp org.apache.jasper.servlet.JspServlet fork false xpoweredBy false compilerTargetVM 1.5 compilerSourceVM 1.5 3 Hope that helps Lakshmi -Original Message- From: Mark Claassen [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 9:29 AM To: 'Tomcat Users List' Subject: Using Javac instead of JDT to compile JSPs Has anyone tried to get the jasper compiler to be something other than the JDT? I tried several things, each of them not working. The docs say an alternative compiler can be specified, but makes no mention of how to specify it. This seems to be controlled by settings in the web.xml. Below is a part of my web.xml from my latest try (which failed). Thanks, Mark web.xml section --- jsp org.apache.jasper.servlet.JspServlet compiler com.sun.tools.javac.main.JavaCompiler fork true xpoweredBy false 3 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Native Library Breaks SSL
Also, use tcnative-1.1.9. I also encountered problems with 1.1.10. --Lakshmi -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Monday, May 28, 2007 7:38 AM To: Tomcat Users List Subject: RE: Tomcat Native Library Breaks SSL > From: Mike Grandmaison [mailto:[EMAIL PROTECTED] > Subject: Tomcat Native Library Breaks SSL > > Windows XP > Tomcat 5.5.23 > http://tomcat.heanet.ie/native/1.1.10/binaries/win32/ > > I followed the openssl instructions at > http://www.galatea.com/flashguides/tomcat-ssl-5-unix > to setup my ssl. You might try following the real documentation: http://tomcat.apache.org/tomcat-5.5-doc/apr.html#HTTPS - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Excluding JSP compiler from Tomcat
I am a Tomcat newbie. We use Tomcat 5.5.23, *Nix and Windows. My recent experience was that in my development environment, if I had the application web.xml (as opposed to global web.xml under conf directory) with the mappings as specified below, then Tomcat refused to compile and was looking for precompiled classes. Then, I removed the mappings from the application web.xml, put ant.jar and tools.jar in $Catalina_HOME/commmon/lib and removed jasper-compiler-jdt.jar from the same place for Tomcat to compile the JSP files on the fly. In the production environment, with the web.xml as defined below, and with precompiled classes placed in the proper location, Tomcat does not try to compile at all, as desired. So in summary, I did not do anything special to "disable" compilation but rather I had to do the steps outlined above to "enable" compilation. --Lakshmi -Original Message- From: lightbulb432 [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 12:32 PM To: users@tomcat.apache.org Subject: RE: Excluding JSP compiler from Tomcat In your production environment have you "disabled" or "excluded" the actual Tomcat piece that does the JSP compilation, to decrease the size and memory usage (no matter how small) of the production Tomcat install? The part of the JSP spec that I referred to in my original post seemed to indicate that it might be possible depending on your container. As Tomcat is the RI, I'm wondering whether this capability is available. Lakshmi Venkataraman wrote: > > In our development environment we compile JSPs on the fly. > In our production environment we have precompiled JSP classes. > > In the PRODUCTION environment, webapps/WEB-INF/web.xml have > and defined for every JSP page. > For example: > >MyAppJsp1 >jsp.myAppJsp1 > > > MyAppJsp1 > /jsp/MyAppJsp1.jsp > > > The precompiled JSP classes are placed inside WEB-INF/classes/jsp. I > guess you can also probably archive these files in a WAR file. > > > --Lakshmi > > -Original Message- > From: lightbulb432 [mailto:[EMAIL PROTECTED] > Sent: Friday, May 25, 2007 10:31 AM > To: users@tomcat.apache.org > Subject: Excluding JSP compiler from Tomcat > > > The JSP spec says that if you precompile JSPs you can reduce the JSP > container footprint by excluding the JSP compiler. How can this be > done in Tomcat? > > Thanks. > -- > View this message in context: > http://www.nabble.com/Excluding-JSP-compiler-from-Tomcat-tf3817429.htm > l# > a10807251 > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > - > To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, > e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, > e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Excluding-JSP-compiler-from-Tomcat-tf3817429.html# a10809085 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Excluding JSP compiler from Tomcat
In our development environment we compile JSPs on the fly. In our production environment we have precompiled JSP classes. In the PRODUCTION environment, webapps/WEB-INF/web.xml have and defined for every JSP page. For example: MyAppJsp1 jsp.myAppJsp1 MyAppJsp1 /jsp/MyAppJsp1.jsp The precompiled JSP classes are placed inside WEB-INF/classes/jsp. I guess you can also probably archive these files in a WAR file. --Lakshmi -Original Message- From: lightbulb432 [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 10:31 AM To: users@tomcat.apache.org Subject: Excluding JSP compiler from Tomcat The JSP spec says that if you precompile JSPs you can reduce the JSP container footprint by excluding the JSP compiler. How can this be done in Tomcat? Thanks. -- View this message in context: http://www.nabble.com/Excluding-JSP-compiler-from-Tomcat-tf3817429.html# a10807251 Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Native library on java.library.path ?
Recently, I saw a similar problem on Solaris9 with Tomcat 5.5.23. Then ldd tcnative-1.so revealed that a certain library (in this case, libgcc.so) was not in the path. By adding that library to the path, Tomcat stopped complaining about not being able to find the native library. On windows, download tomcat source files, create an eclipse project with the tomcat source. Open Catalina.bat, modify the java command line that starts Tomcat and add debug options. DEBUG_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005 Notice suspend=y. This will suspend Tomcat until you attach a debugger. You can put a break point in Library.java or APRLifeCycleListener.java and see what is going on. --Lakshmi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, May 24, 2007 5:52 PM To: users@tomcat.apache.org Subject: Tomcat Native library on java.library.path ? Hello, I recently installed Apache Tomcat 6.0.10 and have been getting the following message upon startup: INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: On Windows XP, I have the following paths added to the PATH environment variable: C:\apache-tomcat-6.0.10\bin;C:\apache-tomcat-6.0.10\lib;%PATH%; I'm a bit stumped: Surely the Native library is the apache-tomcat-6.0.10\lib folder, and surely the java.library.path refers to PATH. So what library needs to be added where? I posted a more in depth question regarding this on jGuru here: http://www.jguru.com/forums/view.jsp?EID=1337110 I've also noticed several other beginners out there with the same or a similar question. Please somebody help. If there's any information I haven't provided that might clarify an explanation, please let me know and I will respond asap. Kind regards, troy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [SOLVED] Tomcat 5.5, IPv6, APR, HTTP and HTTPS
Correction to Linux section. -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 22, 2007 8:59 AM To: Tomcat Users List Subject: RE:[SOLVED] Tomcat 5.5, IPv6, APR, HTTP and HTTPS My application has to work on both Unix and Windows over both IPv4 and IPv6 transport using Http or Https. I am documenting my experience for a "newbie". Here is a summary of what works on what platform. Windows: (See apache bug 41973 for additional comments) tcnative-1.1.8-ipv4.dll works only for IPv4 {tcnative-1.1.7-ipv6, tcnative-1.1.8-ipv6, tcnative-1.1.9.dll} works for both IPv4 and IPv6 providing you define two HTTP connectors both listening to port 80 (whatever port) with address="0.0.0.0" and address="::" Likewise, you have to define two HTTPS connectors both listening to port 443. tcnative-1.1.10 - I got an error "Error starting EndPoint.No Such host". I did not pursue this because of the above working options. Solaris 9: Compiled APR 1.2.8, tcnative-1.1.8, openssl-0.9.8b to produce libtcnative-1.1.8.so In addition to libc.so, this also needed libgcc.so. Once this was included in the path, HTTP and HTTPS transport over IPv4 and IPv6 worked like a charm without any additional configuration changes like Windows. Linux RH4: Compiled APR 1.2.8, tcnative-1.1.8. The server that I was working on already had openSSL-0.9.8b. So did not have to compile this. While compiling tcnative, used --with ssl option and gave its location. Produced libtcnative-1.1.8.so. Again both HTTP and HTTPS worked over both IPV4 and IPv6 transport. Regards Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 02, 2007 8:03 PM To: Tomcat Users List Subject: RE: Tomcat 5.5, IPv6, APR, HTTP and HTTPS Corrections: Here is a summary of what works and what does not. Tomcat 5.5.23, WinXP, JDK 1.5, OpenSSL-0.9.8b is the base configuration. tcnative-1-ipv4.dll (ver 1.1.7) works for both HTTP and HTTPS. tcnative-1-ipv6.dll (ver 1.1.7) works for HTTP and HTTPS only with ipv6 transport between client and server. It DOES NOT support ipv4 transport. Questins 1) Should not an ipv6 library support both ipv4 and ipv6 transport? tcnative-1.dll (version 1.1.9) DOES not work at all for both HTTP and HTTPS in ipv4 or ipv6 mode. tcnative-1.dll (version 1.1.10) works for HTTP and HTTPS with ipv4 transport between client and server. Both 1.1.9 and 1.1.0 do not have a separate ipv6 versions. In all cases above, Tomcat 5.5 server and my application services come up. DOES NOT WORK means the following: When I try to bring my web app in my browser, I see ClassNotFoundException caused by java.net.ConnectionException:Connection Refused in the Java Console. Question 2) Is this a bug in tcnative-1-ipv6.dll or am I missing something? Question 3) Why do versions 1.1.9 and 1.1.10 do not have a separate ipv6 library? Ideally you want to have the same library for both ipv4 and ipv6. Thanks Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 02, 2007 4:57 PM To: Tomcat Users List Subject: Tomcat 5.5, IPv6, APR, HTTP and HTTPS My setup: Tomcat 5.5.23, JDK 1.5, WIN XP I am also using tcnative-1.dll and OpenSSL 0.9.8b Client browser: IE6, Firefox 1.5 for IPv4 IE7 for IPv6. I successfully tested Tomcat 5.5.23 by enabling ipV6 without using APR. SUCCESS: If I use tcnative-ipv4.dll (version 1.1.8) I find that I am able to start Tomcat and other service in the backend. And my web application comes up in both HTTP and HTTPS mode. However, if I use tcnative-ipv6.dll (version 1.1.8), Tomcat and other backend services start successfully. FAILURE: My web application does not come up either in HTTP or HTTPS using ipv4 or ipv6. Java console shows ClassNotFoundException caused by java.net.ConnectionException:Connection Refused. Anybody has any clue as to why I am getting the above exception for both http://localhost and https://localhost using ipv4? Also http://[3000::211] or https://[3000::211] does not work either in IE 7. I also tried tcnative-1.dll (version) 1.1.9. Same problem as tcnative-ipv6.dll (ver 1.1.8). I feel there is something missing in my configuration. Thanks in advance for your help, Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For addit
RE:[SOLVED] Tomcat 5.5, IPv6, APR, HTTP and HTTPS
My application has to work on both Unix and Windows over both IPv4 and IPv6 transport using Http or Https. I am documenting my experience for a "newbie". Here is a summary of what works on what platform. Windows: (See apache bug 41973 for additional comments) tcnative-1.1.8-ipv4.dll works only for IPv4 {tcnative-1.1.7-ipv6, tcnative-1.1.8-ipv6, tcnative-1.1.9.dll} works for both IPv4 and IPv6 providing you define two HTTP connectors both listening to port 80 (whatever port) with address="0.0.0.0" and address="::" Likewise, you have to define two HTTPS connectors both listening to port 443. tcnative-1.1.10 - I got an error "Error starting EndPoint.No Such host". I did not pursue this because of the above working options. Solaris: Compiled APR 1.2.8, tcnative-1.1.8, openssl-0.9.8b to produce libtcnative-1.1.8.so In addition to libc.so, this also needed libgcc.so. Once this was included in the path, HTTP and HTTPS transport over IPv4 and IPv6 worked like a charm without any additional configuration changes like Windows. Linux RH4: Compiled APR 1.2.8, tcnative-1.1.8. It already had openSSL-0.9.8b. Produced libtcnative-1.1.8.so. Again both HTTP and HTTPS worked over both IPV4 and IPv6 transport. Regards Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 02, 2007 8:03 PM To: Tomcat Users List Subject: RE: Tomcat 5.5, IPv6, APR, HTTP and HTTPS Corrections: Here is a summary of what works and what does not. Tomcat 5.5.23, WinXP, JDK 1.5, OpenSSL-0.9.8b is the base configuration. tcnative-1-ipv4.dll (ver 1.1.7) works for both HTTP and HTTPS. tcnative-1-ipv6.dll (ver 1.1.7) works for HTTP and HTTPS only with ipv6 transport between client and server. It DOES NOT support ipv4 transport. Questins 1) Should not an ipv6 library support both ipv4 and ipv6 transport? tcnative-1.dll (version 1.1.9) DOES not work at all for both HTTP and HTTPS in ipv4 or ipv6 mode. tcnative-1.dll (version 1.1.10) works for HTTP and HTTPS with ipv4 transport between client and server. Both 1.1.9 and 1.1.0 do not have a separate ipv6 versions. In all cases above, Tomcat 5.5 server and my application services come up. DOES NOT WORK means the following: When I try to bring my web app in my browser, I see ClassNotFoundException caused by java.net.ConnectionException:Connection Refused in the Java Console. Question 2) Is this a bug in tcnative-1-ipv6.dll or am I missing something? Question 3) Why do versions 1.1.9 and 1.1.10 do not have a separate ipv6 library? Ideally you want to have the same library for both ipv4 and ipv6. Thanks Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 02, 2007 4:57 PM To: Tomcat Users List Subject: Tomcat 5.5, IPv6, APR, HTTP and HTTPS My setup: Tomcat 5.5.23, JDK 1.5, WIN XP I am also using tcnative-1.dll and OpenSSL 0.9.8b Client browser: IE6, Firefox 1.5 for IPv4 IE7 for IPv6. I successfully tested Tomcat 5.5.23 by enabling ipV6 without using APR. SUCCESS: If I use tcnative-ipv4.dll (version 1.1.8) I find that I am able to start Tomcat and other service in the backend. And my web application comes up in both HTTP and HTTPS mode. However, if I use tcnative-ipv6.dll (version 1.1.8), Tomcat and other backend services start successfully. FAILURE: My web application does not come up either in HTTP or HTTPS using ipv4 or ipv6. Java console shows ClassNotFoundException caused by java.net.ConnectionException:Connection Refused. Anybody has any clue as to why I am getting the above exception for both http://localhost and https://localhost using ipv4? Also http://[3000::211] or https://[3000::211] does not work either in IE 7. I also tried tcnative-1.dll (version) 1.1.9. Same problem as tcnative-ipv6.dll (ver 1.1.8). I feel there is something missing in my configuration. Thanks in advance for your help, Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [SOLVED]Tomcat native library Not found in Solaris 9
I attached an eclipse debugger and found that an UnsatsfiedLinkError was thrown due to the Fact that libtcnative-1.so depends on libgcc_s.1.so. Then I included /usr/local/lib in LD_LIBRAY_PATH. Tomcat's Http11AprProtocol connector starts up without any problem. It is still not clear why on solaris 9 libtcnative-1.so depends on libgcc_s.1.so Whereas in Lunux redhat 4 it does NOT do do. Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Saturday, May 12, 2007 5:33 PM To: Tomcat Users List Subject: RE: Tomcat native library Not found in Solaris 9 I upgraded Tomcat to Tomcat 5.5.23 on Solaris 9. I also compiled APR-1.2.8, tomcat-native-1.1.8-src and openssl-0.9.8b on Solaris. I have placed the libtcnative-1.so in /export/home/lakshmi/Ivt55/bin. Ivt55 is the application directory and have INCLUDED it in LD_LIBRARY_PATH and PATH. Yet Tomcat is unable to find libtcnative-1.so. I get this message: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /export/home/lakshmi/Ivt55/jre/lib/sparc/client:/export/home/lakshmi/Ivt 55/jre/lib/sparc:/export/home/lakshmi/Ivt55/jre/../lib/sparc:/export/hom e/lakshmi/Ivt55/3rdPartyPackages/Tomcat/bin:/export/home/lakshmi/Ivt55/b in:/export/home/lakshmi/Ivt55/database::/usr/lib I did NOT have a problem on Linux redhat 4 or Windows. What else is missing on Solaris? Thanks in advance for your reply, Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat native library Not found in Solaris 9
I upgraded Tomcat to Tomcat 5.5.23 on Solaris 9. I also compiled APR-1.2.8, tomcat-native-1.1.8-src and openssl-0.9.8b on Solaris. I have placed the libtcnative-1.so in /export/home/lakshmi/Ivt55/bin. Ivt55 is the application directory and have INCLUDED it in LD_LIBRARY_PATH and PATH. Yet Tomcat is unable to find libtcnative-1.so. I get this message: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /export/home/lakshmi/Ivt55/jre/lib/sparc/client:/export/home/lakshmi/Ivt 55/jre/lib/sparc:/export/home/lakshmi/Ivt55/jre/../lib/sparc:/export/hom e/lakshmi/Ivt55/3rdPartyPackages/Tomcat/bin:/export/home/lakshmi/Ivt55/b in:/export/home/lakshmi/Ivt55/database::/usr/lib I did NOT have a problem on Linux redhat 4 or Windows. What else is missing on Solaris? Thanks in advance for your reply, Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Context Descriptors
In the one month that I have been in this forum, people ask this question in so many different words under so many different subject headings. My own question, the newbie that I am started out with similar questions. Documentation is NOT CLEAR. I hope somebody who has the authority to change the documentation does so. Another suggestion, Chuck, since you are always responding to any context related qeustion, if you find some time, may be you should mail an FAQ post on this forum on the topic of "contexts and deployments" with example directory layouts. Thanks Lakshmi -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Friday, May 11, 2007 6:13 AM To: Tomcat Users List Subject: RE: Context Descriptors > From: lightbulb432 [mailto:[EMAIL PROTECTED] > Subject: Context Descriptors > > The following regarding Context Descriptors is in the documentation > for Tomcat 6. I'm wondering why the included contexts such as > /examples, /docs, /host-manager, and ROOT (/) don't have Context > Descriptors generated as described below. Because those apps are simple enough not to need one. > If a Context Descriptor is not provided for a Context, Tomcat > automatically creates one and places it in (1) with a filename of > [webappname].xml The above statement is not true; the doc needs updating. Tomcat creates the internal data structures for the webapp's , but does not store it in any persistent location. > although if manually created, the filename need not match the web > application name That statement is also not true - the filename must match, unless the element is in server.xml, in which case there is no filename. [Mark - the above somewhat out-of-date statements are in: http://tomcat.apache.org/tomcat-6.0-doc/deployer-howto.html#A%20word%20o n%20Contexts] > Why, under /manager, do I see the following in > /manager/manager.xml: As far as I can tell, that's left-over junk from previous levels; that .xml file used to end up in conf/Catalina/localhost. Regardless, the location cited above isn't used during deployment or running of the app. > And the following in /manager/META-INF/context.xml? Why the presence > of two context descriptors? That's the real one; the first is no longer used. > And finally, why do I see the docBase as > "${catalina.home}/server/webapps/manager" in the previous manager.xml, > when the default Tomcat 6 installation doesn't even have a server > directory? Again, left-over artifacts from previous Tomcat levels. > What confuses me is how it still works even when that directory isn't > there or created. Because that .xml file is completely ignored. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connection refused when using Tomcat 6.0.10 with APR ...
I posted a similar email asking abour Connection Refuesed question under a different thread. I have also summarised my findings. Can you take a look? The subject is "Tomcat 5.5, IPv6, APR, HTTP and HTTPS" --Thanks Lakshmi -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Saturday, May 05, 2007 11:33 AM To: Tomcat Users List Subject: Re: Connection refused when using Tomcat 6.0.10 with APR ... Bertrand wrote: > > Any ideas ? Am I missing something ? How can I debug that problem ? > APR on BSD was compiled with IPV6 support. However IPV6 support on BSD (as well on Windows, because Microsoft winsock is BSD sockets) do not support IPv4-mapped IPv6 address. See: http://issues.apache.org/bugzilla/show_bug.cgi?id=41973 So, the solution is to add the address="127.0.0.1" or any other IPV4 address to the (by default its null and IPV6 is used) Regards, Mladen. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
Andras, Please refer to the directory structure posted earlier in this thread. The only way I could get my application to work is to have a ROOT.xml inside ${catalina.home}/conf/localhost. docBase="C:\/app". This is outside the default appBase="webapps" specified in ${catalina.home}/conf/server.xml. Then I could access my applcation as http://localhost. Hope this helps, Lakshmi P.s: The documentation is not very clear on these points. I hope some expert out there will update Tomcat FAQ. -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, May 04, 2007 4:34 AM To: Tomcat Users List Subject: Re: Tomcat deployment question Andras Laczi wrote: > If someone succeed to deploy an web application trough manager on > 5.5.23 tomcat which path is "/" (root ) and the web application > directory is not ROOT please let me know. > It's making me crazy, i migrating from 5.0.16 with working > configuration and on 5.5.23 same conf works a completely different ways. > Andras The closest you'll get to the 5.0.x behaviour is anything.war located outside the host's appBase and a ROOT.xml pointing towards it. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.5, IPv6, APR, HTTP and HTTPS
Corrections: Here is a summary of what works and what does not. Tomcat 5.5.23, WinXP, JDK 1.5, OpenSSL-0.9.8b is the base configuration. tcnative-1-ipv4.dll (ver 1.1.7) works for both HTTP and HTTPS. tcnative-1-ipv6.dll (ver 1.1.7) works for HTTP and HTTPS only with ipv6 transport between client and server. It DOES NOT support ipv4 transport. Questins 1) Should not an ipv6 library support both ipv4 and ipv6 transport? tcnative-1.dll (version 1.1.9) DOES not work at all for both HTTP and HTTPS in ipv4 or ipv6 mode. tcnative-1.dll (version 1.1.10) works for HTTP and HTTPS with ipv4 transport between client and server. Both 1.1.9 and 1.1.0 do not have a separate ipv6 versions. In all cases above, Tomcat 5.5 server and my application services come up. DOES NOT WORK means the following: When I try to bring my web app in my browser, I see ClassNotFoundException caused by java.net.ConnectionException:Connection Refused in the Java Console. Question 2) Is this a bug in tcnative-1-ipv6.dll or am I missing something? Question 3) Why do versions 1.1.9 and 1.1.10 do not have a separate ipv6 library? Ideally you want to have the same library for both ipv4 and ipv6. Thanks Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 02, 2007 4:57 PM To: Tomcat Users List Subject: Tomcat 5.5, IPv6, APR, HTTP and HTTPS My setup: Tomcat 5.5.23, JDK 1.5, WIN XP I am also using tcnative-1.dll and OpenSSL 0.9.8b Client browser: IE6, Firefox 1.5 for IPv4 IE7 for IPv6. I successfully tested Tomcat 5.5.23 by enabling ipV6 without using APR. SUCCESS: If I use tcnative-ipv4.dll (version 1.1.8) I find that I am able to start Tomcat and other service in the backend. And my web application comes up in both HTTP and HTTPS mode. However, if I use tcnative-ipv6.dll (version 1.1.8), Tomcat and other backend services start successfully. FAILURE: My web application does not come up either in HTTP or HTTPS using ipv4 or ipv6. Java console shows ClassNotFoundException caused by java.net.ConnectionException:Connection Refused. Anybody has any clue as to why I am getting the above exception for both http://localhost and https://localhost using ipv4? Also http://[3000::211] or https://[3000::211] does not work either in IE 7. I also tried tcnative-1.dll (version) 1.1.9. Same problem as tcnative-ipv6.dll (ver 1.1.8). I feel there is something missing in my configuration. Thanks in advance for your help, Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.5, IPv6, APR, HTTP and HTTPS
My setup: Tomcat 5.5.23, JDK 1.5, WIN XP I am also using tcnative-1.dll and OpenSSL 0.9.8b Client browser: IE6, Firefox 1.5 for IPv4 IE7 for IPv6. I successfully tested Tomcat 5.5.23 by enabling ipV6 without using APR. SUCCESS: If I use tcnative-ipv4.dll (version 1.1.8) I find that I am able to start Tomcat and other service in the backend. And my web application comes up in both HTTP and HTTPS mode. However, if I use tcnative-ipv6.dll (version 1.1.8), Tomcat and other backend services start successfully. FAILURE: My web application does not come up either in HTTP or HTTPS using ipv4 or ipv6. Java console shows ClassNotFoundException caused by java.net.ConnectionException:Connection Refused. Anybody has any clue as to why I am getting the above exception for both http://localhost and https://localhost using ipv4? Also http://[3000::211] or https://[3000::211] does not work either in IE 7. I also tried tcnative-1.dll (version) 1.1.9. Same problem as tcnative-ipv6.dll (ver 1.1.8). I feel there is something missing in my configuration. Thanks in advance for your help, Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
Hi Rashmi, Thanks! Worked! :) By renaming myApp.xml to ROOT.xml and changing path="" in both ROOT.xml and myApp/context.xml, I can access my application as http://localhost:8080. But I am curious, why http://localhost:8080/myApp did NOT work? Thanks Lakshmi -Original Message- From: Rashmi Rubdi [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 25, 2007 8:25 PM To: Tomcat Users List Subject: Re: Tomcat deployment question Hi Lakshmi, I'll explain the way I got it to work - I think it's correct because I can access my app at the root context http://localhost:8080/ Please find my replies below: Of course you can undo all the changes mentioned below and bring it back to the original state at anytime. On 4/25/07, Lakshmi Venkataraman <[EMAIL PROTECTED]> wrote: > > Here's my dierctory set up: > > >--Tomcat55 {catalina.home} > --bin > -- conf >-- Catalina > --localhost > myApp.xm In the above change myApp.xml to ROOT.xml > --common > --server > --webapps > >-- myApp >context.xml >index.html >--bin >--html >--jsp >--css >--jar >--WEB-INF > web.xml > --classes > --lib > > > > > myApp.xml has the following: > privileged="true"> > > Now myApp.xml is renamed to ROOT.xml , keep the path attribute empty as in path="" the docBase attibute looks correct. It is also fine to keep your project outside Tomcat's webapps folder, it makes it easier to upgrade Tomcat in the future. > context.xml under myApp has > Also change path to path="" in context.xml > > http://localhost:8080 brings up the default Tomcat homepage. After making the above configuration changes in ROOT.xml and context.xml the app should be accessible at http://localhost:8080/ > I am NOT able to access my application as http://localhost:8080/myApp > Ideally, I would like to access my application as http://localhost:8080. > So what am I missing in my definitions in myApp.xml or > myApp/context.xml? > > Thanks a lot > Lakshmi > The concept is that ROOT.xml represents the root context which corresponds to the first slash / after http://localhost:8080 If the context is called myApp.xml then naturally it is not the root context so it appears under the myApp context. Hope this clears things up. Regards -Rashmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
I have upgraded from Tomcat 3.3 to Tomcat 5.5.23. It is running on WinXP and I am using Java 1.5. I asked this question before with a different directory set up in which the "myApp" directory was under Tomcat heirarchy. As Rashmi Rubdi suggested, by renaming myApp.xml to ROOT.xml, I could access my application using http://localhost:8080 Chuck Caldarale said it is preferable to have myApp outside Tomcat's directory heirarchy. I am playing with a different directory structure as shown below. Here Tomcat heirarchy is outside the myApp heirarchy. Here's my dierctory set up: --Tomcat55 {catalina.home} --bin -- conf -- Catalina --localhost myApp.xml --common --server --webapps -- myApp context.xml index.html --bin --html --jsp --css --jar --WEB-INF web.xml --classes --lib myApp.xml has the following: context.xml under myApp has http://localhost:8080 brings up the default Tomcat homepage. I am NOT able to access my application as http://localhost:8080/myApp Ideally, I would like to access my application as http://localhost:8080. So what am I missing in my definitions in myApp.xml or myApp/context.xml? Thanks a lot Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
Thanks Chuck! See my comments inline starting with Lakshmi: -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 12:58 PM To: Tomcat Users List Subject: RE: Tomcat deployment question > From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] > Subject: RE: Tomcat deployment question > > Please refer to the directory structure in the original message or At > the bottom of this email. > > Given that directory structure, I have working configuration with > appBase="webapps" in server.xml (seems like a dummy value since we > don't have anything in that directory). The appBase attribute defines the default location for webapps. You don't have to use it, since it's often easier to keep your webapps completely outside of the Tomcat directory structure. >> In ${catalina.home}/conf/catalina/localhost/ROOT.xml I have defined >> the element with docBase="${catalina.home}/htdocs". >This is probably not a good idea. If you're not going to put your webapps under the appBase directory, you're >probably better off keeping them entirely outside of the Tomcat directory structure. Throwing things into >arbitrary locations can be a maintenance mess, especially at upgrade time >> Previously, I had appBase="htdocs" and ROOT.xml was called >> htdocs.xml. >> 1) When absolute path such as ${catalina.home}/htdocs is specified why >> does it look for ${catalina.home}/htdocs/htdocs/ >I don't really understand the above question. Who is "it"? Where is the "absolute path" specified? What makes >you think anyone or anything was looking for ${catalina.home}/htdocs/htdocs/? Lakshmi: "It" is Tomcat. I am referring to ${catalina.home}/htdocs as "absoulte path". It becomes absolute after ${catalina.home} is expanded. When tomcat is started and starts reading htdocs.xml, I get the following message: Warning: a docBase w:\INM\Apache\htdocs\htdocs inside the host appBase has been defined and will be ignored. In addition, I get java.lang.IllegalArgumentException saying that the ROOT directory does not exist or is unreadable. > 2) Why does it expect a ROOT directory under htdocs? Because you specified appBase to be "htdocs" and did not have a ROOT.xml to override the default location. > 3) What is special about ROOT? Should not the configuration be totally > under application Developer's control? Some means of specifying the default webapp is necessary, and the Tomcat developers chose to use ROOT as the default. It's all in the docs: http://tomcat.apache.org/tomcat-5.5-doc/config/context.html > 4) What is path? The path attribute for the element is no longer used, unless the element is within server.xml (strongly discouraged). "Path" in this instance refers to the URL sent by a client to access a webapp. > It is not very clear from the documenatation. It took me a while to > get to the current working Configuration. It may be working, but I wouldn't leave it that way. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
Please refer to the directory structure in the original message or At the bottom of this email. Given that directory structure, I have working configuration with appBase="webapps" in server.xml (seems like a dummy value since we don't have anything in that directory). In ${catalina.home}/conf/catalina/localhost/ROOT.xml I have defined the element with docBase="${catalina.home}/htdocs". Here are the questions: Previously, I had appBase="htdocs" and ROOT.xml was called htdocs.xml. 1) When absolute path such as ${catalina.home}/htdocs is specified why does it look for ${catalina.home}/htdocs/htdocs/ 2) Why does it expect a ROOT directory under htdocs? 3) What is special about ROOT? Should not the configuration be totally under application Developer's control? 4) What is path? It is not very clear from the documenatation. It took me a while to get to the current working Configuration. I will appreciate it if one of you can clarify these concepts. Thanks in advance, Lakshmi -Original Message- From: Lakshmi Venkataraman Sent: Wednesday, April 18, 2007 11:21 PM To: 'Tomcat Users List' Subject: RE: Tomcat deployment question I have finally a working configuration. Please refer to the bottom of this email for the directory structure. In server.xml I changed appBase="webapps" (original value) htdocs.xml is renamed as ROOT.xml as Rashmi suggested with docBase="${catalina.home}/htdocs Then I am able to type http://localhost:8080 which in turn looks up index.html from the htdocs directory Even so, I have some more questions and my understanding is not that clear yet. I will post the questions in my next email. Thanks Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 9:33 PM To: Tomcat Users List Subject: RE: Tomcat deployment question Hi Rashmi, Thanks! I renamed htdocs.xml to ROOT.xml. http://localhost:8080 did not work. However, http://localhost:8080/htdocs/index.html worked which is some progress. I think my organization would prefer only http://localhost:8080 I am confused between the concepts appBase, docBase and path. So given the directory structure below, what should be the values of appBase, docBase and path so http://localhost:8080 looks for index.html under htdocs. Thanks again Lakshmi -Original Message- From: Rashmi Rubdi [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 9:04 PM To: Tomcat Users List Subject: Re: Tomcat deployment question Hi Lakshmi, Rename the context file from htdocs.xml to ROOT.xml then you should be able to access the app at http://localhost:8080/ -Rashmi ---Original posting by Lakshmi --- I have upgraded from Tomcat 3.3 to Tomcat 5.5.23. It is running on WinXP and I am using Java 1.5. Here's my dierctory set up: ${Catalina.Home} -- conf -- Catalina --localhost htdocs.xml -- htdocs index.html --bin --html --jsp --css --jar --WEB-INF web.xml --classes --lib --webapps In server.xml, I modified the element to have {appBase="htdocs" autoDeploy="false"} I am using htdocs.xml in ${Catalina.home}/Catalina/localhost as the context descriptor and is defined as follows: WEB-INF/web.xml Tomcat is able to load appClassLoader. However, when I type, http://localhost:8080, it is not able to load the index.html found under the htdocs directory. If I create ROOT directory and move the index.html over there it is able to load it. I guess, my main problem is how can I maintain the same directory structure as above without having to create ROOT and move everything below it? The above directory structure worked in Tomcat 3.3. What am I missing? Thanks Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
I have finally a working configuration. Please refer to the bottom of this email for the directory structure. In server.xml I changed appBase="webapps" (original value) htdocs.xml is renamed as ROOT.xml as Rashmi suggested with docBase="${catalina.home}/htdocs Then I am able to type http://localhost:8080 which in turn looks up index.html from the htdocs directory Even so, I have some more questions and my understanding is not that clear yet. I will post the questions in my next email. Thanks Lakshmi -Original Message- From: Lakshmi Venkataraman [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 9:33 PM To: Tomcat Users List Subject: RE: Tomcat deployment question Hi Rashmi, Thanks! I renamed htdocs.xml to ROOT.xml. http://localhost:8080 did not work. However, http://localhost:8080/htdocs/index.html worked which is some progress. I think my organization would prefer only http://localhost:8080 I am confused between the concepts appBase, docBase and path. So given the directory structure below, what should be the values of appBase, docBase and path so http://localhost:8080 looks for index.html under htdocs. Thanks again Lakshmi -Original Message- From: Rashmi Rubdi [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 9:04 PM To: Tomcat Users List Subject: Re: Tomcat deployment question Hi Lakshmi, Rename the context file from htdocs.xml to ROOT.xml then you should be able to access the app at http://localhost:8080/ -Rashmi ---Original posting by Lakshmi --- I have upgraded from Tomcat 3.3 to Tomcat 5.5.23. It is running on WinXP and I am using Java 1.5. Here's my dierctory set up: ${Catalina.Home} -- conf -- Catalina --localhost htdocs.xml -- htdocs index.html --bin --html --jsp --css --jar --WEB-INF web.xml --classes --lib --webapps In server.xml, I modified the element to have {appBase="htdocs" autoDeploy="false"} I am using htdocs.xml in ${Catalina.home}/Catalina/localhost as the context descriptor and is defined as follows: WEB-INF/web.xml Tomcat is able to load appClassLoader. However, when I type, http://localhost:8080, it is not able to load the index.html found under the htdocs directory. If I create ROOT directory and move the index.html over there it is able to load it. I guess, my main problem is how can I maintain the same directory structure as above without having to create ROOT and move everything below it? The above directory structure worked in Tomcat 3.3. What am I missing? Thanks Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat deployment question
Hi Rashmi, Thanks! I renamed htdocs.xml to ROOT.xml. http://localhost:8080 did not work. However, http://localhost:8080/htdocs/index.html worked which is some progress. I think my organization would prefer only http://localhost:8080 I am confused between the concepts appBase, docBase and path. So given the directory structure below, what should be the values of appBase, docBase and path so http://localhost:8080 looks for index.html under htdocs. Thanks again Lakshmi -Original Message- From: Rashmi Rubdi [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 9:04 PM To: Tomcat Users List Subject: Re: Tomcat deployment question Hi Lakshmi, Rename the context file from htdocs.xml to ROOT.xml then you should be able to access the app at http://localhost:8080/ -Rashmi ---Original posting by Lakshmi --- I have upgraded from Tomcat 3.3 to Tomcat 5.5.23. It is running on WinXP and I am using Java 1.5. Here's my dierctory set up: ${Catalina.Home} -- conf -- Catalina --localhost htdocs.xml -- htdocs index.html --bin --html --jsp --css --jar --WEB-INF web.xml --classes --lib In server.xml, I modified the element to have {appBase="htdocs" autoDeploy="false"} I am using htdocs.xml in ${Catalina.home}/Catalina/localhost as the context descriptor and is defined as follows: WEB-INF/web.xml Tomcat is able to load appClassLoader. However, when I type, http://localhost:8080, it is not able to load the index.html found under the htdocs directory. If I create ROOT directory and move the index.html over there it is able to load it. I guess, my main problem is how can I maintain the same directory structure as above without having to create ROOT and move everything below it? The above directory structure worked in Tomcat 3.3. What am I missing? Thanks Lakshmi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat deployment question
I have upgraded from Tomcat 3.3 to Tomcat 5.5.23. It is running on WinXP and I am using Java 1.5. Here's my dierctory set up: ${Catalina.Home} -- conf -- Catalina --localhost htdocs.xml -- htdocs index.html --bin --html --jsp --css --jar --WEB-INF web.xml --classes --lib In server.xml, I modified the element to have {appBase="htdocs" autoDeploy="false"} I am using htdocs.xml in ${Catalina.home}/Catalina/localhost as the context descriptor and is defined as follows: WEB-INF/web.xml Tomcat is able to load appClassLoader. However, when I type, http://localhost:8080, it is not able to load the index.html found under the htdocs directory. If I create ROOT directory and move the index.html over there it is able to load it. I guess, my main problem is how can I maintain the same direstory structure as above without having to create ROOT and move everything below it? The above directory structure worked in Tomcat 3.3. What am I missing? Thanks Lakshmi