Re: Connector build error
Adam Fowler wrote: > > Hi, > > This made me a bit miffed too. The developers have changed the > jk/native2/README.txt to explain how to do it natively. Here is the post to > the dev list below. > > If you get some annoying message saying "could not find library -lapr-0" > then fear not. You either: > a) edit the jk/native2/server/apache2/Makefile file. Line 57 I think where > it says "-lapr-0" and change it to "-lapr". then run make again. > b) Install libapr-0. > > I chose the first option and it worked fine. It puts the so file in > /build/jk2/apach2/ tho so be warned. Its a horrible horrible hack but it > will allegedly be fixed in the upcoming 2.0.4 release. Yes, this works. Also, apache 2.0.48 contains an apr-0 lib, so the -1apr hack was not necessary with 2.0.48 Thanks for the assistance! -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connector build error
Am trying to build the .so connector to integrate tomcat 4.1.30 with apache 2.0.48 on debian linux. Both tomcat and apache are up and running just fine individually, but need a mod_jk2.so Ajp13 connector to get a servlet working. The current connectors source distribution jakarta-tomcat-connectors-jk2-2.0.2-src fails as follows: -- $ cd jakarta-tomcat-connectors-jk2-2.0.2-src/jk jk$ ant Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED /fs/hdb9/hdc4/home/gnu/net/www/apache/connectors/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/build.xml:105: Warning: Could not find file /fs/hdb9/hdc4/home/gnu/net/www/apache/connectors/jakarta-tomcat-connectors-jk2-2.0.2-src/coyote/build/lib/tomcat-coyote.jar to copy. --- Sure enough, build/lib does not contain any tomcat-coyote.jar file. In fact, lib is totally empty. The current connector source distro appears to be missing some needed files. Well, all I need is the binary connector, so let's just try: jk$ ant native Buildfile: build.xml jkant: BUILD FAILED /fs/hdb9/hdc4/home/gnu/net/www/apache/connectors/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/build.xml:232: srcdir "/fs/hdb9/hdc4/home/gnu/net/www/apache/connectors/jakarta-tomcat-connectors-jk2-2.0.2-src/jk/jkant/java" does not exist! Turns out it is looking for a file jkant/java/ant.tasks, which also does not exist in the current distro. Can anyone supply 1. tomcat-coyote.jar 2. ant.tasks or, better stiil 3. A complete version of the connectors source distro that works? Thanks very much. PS: apache 2.0.48 built flawlessly using 'make' on debian. Real slick! The connectors source should do at least as well since it is java-based (and java is less error prone than c ;-) -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stubborn simple servlet
Rick Lutowski wrote: > > Mike Curwen wrote: > > if it's the other, try: > > http://localhost:8080/ship_pix/pix.pxhtml?base=CV10";> > > With > http://localhost:8080/ship_pix/pix_servlet/pix.pxhtml?base=CV10";> > the error is > "404 -- /ship_pix/pix_servlet/pix.pxhtml is not available" With further fussing, this works! I had changed web.xml to key on "/pix_servlet/*.pxhtml" as an experiment. When I changed it back to the original "*.pxhtml" and used the Context base 'ship_pix' in the URL (either absolute or relative), everything started clicking. Thanks for the help! :-)) BTW -- Read in some web doc that the plan is to write a tool tool for _generating_ all these config files rather than having to tweak them by hand. A good config tool would certainly have helped avoid a lot of head bashing. If anyone on this list knows of someone who is contemplating writing a tomcat config tool, please let me know. I know some requirements methodology approaches that can be applied when scoping such tools to help make them more user friendly and more maintainable. Be happy to teach these techniques to the folks involved. Thanks again. -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stubborn simple servlet
Mike Curwen wrote: > > Is the servlet configured under the jreality webapp or the ship_pix one? The /ship_pix context. No servlets are under /jreality > If it's the jreality, try linking: > > > if it's the other, try: > http://localhost:8080/ship_pix/pix.pxhtml?base=CV10";> Good thought, but no joy: "404 -- /ship_pix/pix.pxhtml is not available" With http://localhost:8080/ship_pix/pix_servlet/pix.pxhtml?base=CV10";> the error is "404 -- /ship_pix/pix_servlet/pix.pxhtml is not available" > your link has /servlet in it, so yes, the invoker servlet being off by > default in 4.1.30 is likely(?) coming into play. Frames always confuse > the issue for me, so maybe I'm not entirely understanding your page > layouts and how/when servlets are being called. Rechecked server.xml and you are right, invoker is not included. This might be the problem. Will look into enabling it (unless there is another way to launch simple servlets.) > Also , when did 'pix_servlet' come into it? what is that? "pix_servlet" is just a rename of the "servlet" subdirectory in case 4.1.30 blacklists "servlet" for being a 'dirty word'. However, the rename made no difference. -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stubborn simple servlet
Wendy Smoak wrote: > > Rick Lutowski wrote: > > Probably not the problem. > > Okay, but you still haven't told us what URL gives the 404. That you're > getting a 404 means that Tomcat cannot map the URL you're providing to > anything it has to offer. > > > > reloadable="true" crossContext="true"> > >> prefix="ship_pix_log." suffix=".txt" > > timestamp="true"/> > > > > Where is the 'ship_pix' directory and what does it contain? ship_pix is a soft link in webapps to the actual directory. In case the link might be causing the problem, also tried an absolute path in the Context, e.g.: I did discover that 3.2.3 accepted a link to jar files in WEB-INF/lib but 4.1.30 did not. So I moved all the jars physically into WEB-INF/lib. After that all startup errors in the 4.1.30 log files went away and the jars are now deploying properly (based on the logs). > Are you sure that the context is starting? Any errors in catalina.out, > or in the context log files on startup, or right after you get the 404? No errors in any log files. All log messages are INFO and appear to reflect normal operation. No, am not sure the context is starting. 3.2.3 printed context activation messages to the screen on startup but 4.1.30 does not. Rather 4.1.30 prints log messages about contexts being ignored (or somesuch) if there are errors. Assume this means that 'no news is good news' in the logs. The logs are no longer printing bad news about contexts. That's all I know for sure. > My money is on a config problem. Personally I do not mess with > server.xml other than to change the hostname and port number. So if I > had to debug this problem locally, I would put server.xml back the way > it was, put the contexts directly under 'webapps' and watch the logs > closely. Am sure you are right; am also assuming it is a config problem. Have also tried deleting the 's from server xml and letting it deploy with defaults based on what is in webapps. According to the logs the jars deploy the same as before. Same problem -- 404 -- so went back to explicit in server.xml since I know that worked in 3.2.3. Also allows some refinements like separate log files, which _is_ working so the 's are at least partly correct. I usually get these things to go by beating them 'every which way but loose" but this time nothing has been able to 'make my day.' Appreciate the help. -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stubborn simple servlet
Mike Curwen wrote: > > What URL are you using to access a given page (one that gives you a > 404)? > something like: > > http://www.foo.com/ship_pix/index.pxhtml ? That is the next step. Currently just trying to get standalone working, so the URL is more like: http://localhost:8080/jreality/ldj/l.ships/servlet/pix.pxhtml?base=CV10 This is the resolved path that appears in the browser. The link in the html file is The parent html file is in jreality/ldj/l.ships which is correctly resolved by 4.1.30 via the /jreality Context. On the off chance that /servlet may be a problem in 4.1.30, also tried changing the path to pix_servlet, i.e., http://localhost:8080/jreality/ldj/l.ships/pix_servlet/pix.pxhtml?base=CV10 in the web.xml and the parent html files. Same 404 error: "HTTP status 404 - the resource /jreality/ldj/l.ships/pix_servlet/pix.pxhtml?base=CV10 is not available" -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stubborn simple servlet
Wendy Smoak wrote: > > > From: [EMAIL PROTECTED] > > An trying to convert a simple servlet of the HelloWorld > > variety (pure HTML -- no JSP, EJB, JDBC, etc) from > > tomcat 3.2.3 to 4.1.30. It works fine with tomcat 3.2.3 > > in standalone mode but gives a 404 error in 4.1.30 with > > both netscape and mozilla. > > What URL are you visiting when you get the 404 error? Any chance it has > /servlet/ in it? If so, read here: > http://test.javaranch.com/wiki/view?InvokerServlet Probably not the problem. The following 's were added to the end of the distro server.xml: The above pairs with the following in the servlet web.xml file: LdjServlet Generates dynamic pages for the LDJ web site. Currently this consists of frame list pages for displaying selected ship photos. The pages generated have the names pix_dir.html for the list of ship photo subdirectories (the upper left list of the photo frame) and pix_[subdir].html for the list of photos in one subdirectory (the lower left list of the photo frame). com.jreality.ldj.l_ships.LdjServlet LdjServlet *.pxhtml The above does not appear to match the 'invoker' patterns shown in the referenced URL's. The above works in tomcat 3.2.3. -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Stubborn simple servlet
An trying to convert a simple servlet of the HelloWorld variety (pure HTML -- no JSP, EJB, JDBC, etc) from tomcat 3.2.3 to 4.1.30. It works fine with tomcat 3.2.3 in standalone mode but gives a 404 error in 4.1.30 with both netscape and mozilla. The 4.1.30 demos work so tomcat is installed ok. My servlet's web.xml is unchanged from 3.2.3, where it works. The servlet was added to the demo tomcat conf/server.xml file in the 4.1.30 style and the demos still work (so the conf file cannot be botched too badly!) My servlet even shows up in the 'manager' listing as deployed and active. The logs show no errors either on tomcat start or stop. Everything looks fine except for the darn 404 error. Have tried inserting println's into my servlet to see if the servlet is actually entered on the assumption that servlet println's will get dumped to the log files. None of this output shows up in the logs, so either 4.1.30 is not executing the servlet or my println assumption is false (or both). I'm at a loss what to do next to fix this config problem (as it must surely be). Any suggestions appreciated. -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] http://www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
404 with 3.2.3
Am at the end of my rope trying to get tomcat 3.2.3 to run a simple webapp on my debian linux server. The same tomcat binary runs the webapp fine on my development debian linux system in tomcat standalone mode, but gets a 404 error (page not found) when run with apache on the server box. Figured it has to be a simple stupid problem with the apache-tomcat adapter config. Have tried everything in the docs about setting up the adapter and still keep getting 404. Have both mod_jserv.so and mod_jk.so installed in the apache libexec directory, and have pointed httpd.conf alternately to tomcat-apache.conf and mod_jk.conf-auto, but nothing makes any difference. Keeping getting 404. This is a simple servlet, not a jsp although am currently using a .jsp extension for the generated pages. Was originally using an app-specific extension for the generated files, which also works fine on the development system standalone but gives 404 with apache on the server. Being a Java developer, have considered bugging the tomcat source with printlns to see where the problem might be, but there are a lot of .java files and I don't have a clue re the tomcat architecture to know what to instrument and recompile to get a handle on this using that approach (not that I think the problem is in the tomcat code, but it might give a clue as to what in the config files is incorrect. Have also downloaded tomcat 4 in exasperation and considered junking tomcat 3.2.3, but tomcat 4 has a while new set of config files, and I've just started getting used to the structure of the 3.2.3 config files. My mind is about fried and can't handle learning a whole new tomcat config set up at this point. Have been beating my head against the wall for a couple weeks on this. (A nice tomcat config tool where you enter the name of the servlet, the classpath to the servlet, the path to to the webapps file, and other simple data like that, and have the various config files gen'd automatically would probably solve my problem.) Have checked this group's archive logs for 404 errors to see if anyone else has had this problem, but there are 15800 messages related to 404 problems! Maybe someone has, but tough to find it in that big a pile. So my apologies for yet another 404 post, but this is driving me nuts (and not doing my web site any good either.) Any clues or ideas as to the solution would be appreciated. Thanks. -- Rick Lutowski Principal, JReality [EMAIL PROTECTED] www.jreality.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
