Re: Tomcat error-page not working (was: RE: Tomcat and checked vs. unchecked exceptions)
Wendy: Here's your problem: location/WEB-INF/jsp/exceptions/ServletException.jsp/location JSPs can't be run from inside the WEB-INF directory. Try moving your jsp/exceptions directory up one level. Jerry Wendy Smoak wrote: From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Try exception-typejava.lang.RuntimeException/exception-type, as that's the superclass for unchecked exceptions and you probably want to handle them all the same (if you want to handle them at all, which apparently you do). I don't understand. :( I don't know if this is related to the original question, but I have this in web.xml: error-page exception-typejavax.servlet.ServletException/exception-type location/WEB-INF/jsp/exceptions/ServletException.jsp/location /error-page (in the appropriate place, at the bottom just above /web-app) When this code executes: if ( report == null || report.equals( ) ) { log.debug( doGet: no data! Need to forward to an error page. ); throw new ServletException( No data found in HOLD file ); } I _still_ get this in the browser: type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: No data found in HOLD file at edu.asu.vpia.webapp.PDFServlet.doGet(PDFServlet.java:94) Yansheng Lin suggested using Struts declarative exception handling, but this is a plain-old Servlet, not a Struts Action. The same error-page tag works fine in a different webapp, I'm at a loss as to why it fails in this one. The JSP is present in the location given in the tag. What am I missing, why do I get a Tomcat-generated error page and not the JSP I specified? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disable Directory Listing for Specific Apps.
Ben: The proverbial $.02 of opinion: If the customer owns the directory, then doesn't the customer also own the decision to allow files in it to be listed? Seems like it is an easier documentation problem to explain how to prevent listings (include an index.html file in your directory if you don't want...blah blah blah) than to explain how to edit the global web.xml file. Also a less perilous task for the user, since a typo in the web.xml file could screw up everything. Jerry Ben Souther wrote: That would do except that we are allowing customers to create directories and have no guarantee that the welcome file will exist there. It would be nice if we could disable directory listing for the entire app from within the war file. We have no guarantee that they won't be using the same instance of Tomcat for other apps and we are hoping to avoid walking customers through editing the global web.xml file. It's starting to look like this isn't possible.. :-( On Thursday 19 February 2004 05:44 pm, Parsons Technical Services wrote: If I understand the notes correctly, if you simply include a welcome file then TC will not serve up the directory listing. This is also how my setup acts. It will not show the directory for my app which has an index file. And the global web.xml is untouched. See the notes in the global web.xml and Servlet 2.4 specifications. Doug www.parsonstechnical.com - Original Message - From: Ben Souther [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, February 19, 2004 4:54 PM Subject: Disable Directory Listing for Specific Apps. Is it possible to disable directory listings for a specific web app as opposed to editing the global web.xml file in TOMCAT_HOME/conf/web.xml? We would like to ship our app as a war file and don't want require that our customers make global changes to Tomcat for it to behave properly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp files won't run outside of example directories.
David: I just fought my way through this same problem. Solved it this weekend, with help from this forum. Search for messages posted here last week with jsp deployment in the subject for details. Short answer for me: don't use Tomcat's invoker servlet. Even though the invoker is supposedly for mapping servlets, its presence prevented my webapp from working when I added a JSP page. Removing the invoker servlet-mapping element from my web.xml file and mapping each servlet individually solved the problem. Jerry David Grant wrote: Hi All, I am having trouble getting .jsp files working outside the default webapps directory used by Tomcat to display examples. The examples work just fine, and if I put any .jsp file under the jsp-examples directory, they work fine too. The other directory I have setup (myapp) is within my website. The directory structure goes like this: /var/www/www.mysite.com /jsp-bin /myapp /WEB-INF index.html hello.jsp I get an error requested resource not available from Tomcat when I try to access the /myapp/ directory or anything in it: http://www.mysite.com/myapp/ I have edited server.xml and workers2.properties shown below. server.xml: --- !-- The defualt for examples - works when accessing examples directory -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false /Host !-- My directory - does not work -- Host name=mysite.com debug=1 appBase=/var/www/www.mysite.com/jsp-bin unpackWARs=true Aliaswww.mysite.com/Alias /Host -- workers2.properties --- #Virtual Host from Apache [uri:mysite.com:80/myapp/*] worker=ajp13:localhost:8009 #Beta virtual Host from Apache. [uri:www.mysite.com:80/myapp/*] worker=ajp13:localhost:8009 These are snippets from my configs, and the sections that I have been focusing on, just let me know if you need any more details. I am running Red Hat Linux, Apache 2 and Tomcat 5. Any help is appreciated, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment-- Clarification of Invoker
Well, that was certainly fun :) I have made it work, and I think I sort of know how. Not *why* the fix works, just *how* to get my app functional once again. And you are correct, Doug, in aiming me at the invoker servlet as the culprit. The solution that worked for me is to remove the invoker servlet-mapping element from my web app and map each servlet individually. (Though beware---all servlets must be defined before any mapping elements are added to the web.xml file, or else the parser will throw an exception. Spent a good couple of hours or more fighting that little firefight on the sidelines.) Don't understand why the presence of the invoker should foul up the operation of the jsp, but when I removed it and got the servlet/servlet-mapping order straight, suddenly the webapp worked, including the jsp, and both using Tomcat by itself and going through Apache. Thanks for all who helped. Jerry Parsons Technical Services wrote: My understanding of invoker and my attempt to explain invoker and mapping. Please correct any error I have made. Jerry Ford wrote: I don't fully understand the invoker servlet myself, but here's what I think I know: The invoker mapping only applies to servlets, not html or jsps, and the servlets are working (at least through Apache). True. But if you have any links in the html or jsp page, it can prevent them from being displayed, at least this was true in my case. If the invoker mapping specifies /servlets/* then servlets must be included in the URL. By taking it out of the invoker mapping, it does not need to be included in the URL. So, http://localhost/servlets/do_something is required if the mapping is as you say it should be, and http://localhost/do_something is the URL if the mapping is as I have it. My current understanding is that without the invoker you have to use the full path including the package designation. Unless.. See below. With the invoker it will run ANY servlet in you app by entering the desired or undesired URL. IE it is a security issue. http://localhost/servlets/? when a value matching any of your servlets is entered it is run. As I stated earlier I wastn't hitting any servlets directly from the URL so I cannot attest to if this will work as you have it. All I know at this point is that my setup would not work this way /* but did with /servlet/*. But you are correct that you must have servlet in the URL in order for it to match the pattern with it my way. Now for the kicker. As stated above, the invoker is considered a security risk and should not be used. Instead you should define mapping for your servlets. Once this is done you can access only servlets that you want to be available from the outside and protect the ones you don't. And on top of that you can use any name you wish rather then the name of the servlet. From you web.xml you have: servlet servlet-name set_config /servlet-name servlet-class catseye.ebook.set_config /servlet-class /servlet This can be mapped by: servlet-mapping servlet-nameset_config/servlet-name url-pattern/sconfig/url-pattern servlet-mapping You can the call this servlet from within a html or jsp page with ./sconfig (don't miss leading period) or from the URL with http://localhost/EBook/sconfig . As pointed out in several articles if you change the name of the servlet the only change you have is in the mapping. All references will still point to sconfig that is mapped to the desired servlet. And yes I had code issues that cause me to require the invoker. Once I changed them to ./name the mapping then worked and I was able to remove the invoker completely. Sorry for the long post but thought I would pass along what I found out. Hope it helps. Doug Parsons www.parsonstechnical.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Tomcat manager shows EBook is running. And, when I request it through Apache, Tomcat does serve it up. When I request it through port 8080, Tomcat says it's not available: Workshttp://localhost/EBook Doesn't workhttp://localhost:8080/EBook Works---http://localhost/examples/jsp Works---http://localhost:8080/examples/jsp Jerry BAO RuiXian wrote: Jerry Ford wrote: Sorry, that's a cut-and-paste error that does not appear in the real server.xml. Only one /context end tag; the root context is closed before the EBook context begins: context... / The configuration seems okay then. BTW, can you run http://localhost:8080/manager/list to see what apps you have installed? If you can not find 'EBook', then you need to install it by running http://localhost:8080/manager/install?war=EBook Best Bao Jerry Thomas Tang wrote: Bill is correct. This portions seems off. Try separating them. I dont think you should be seeing /Context followed by and another /Context. !-- ROOT context -- Context path= docBase=ROOT debug=0/ !-- EBook context -- Context path=/EBook docBase=EBook debug=0 reloadable=true crossContext=true !-- EBook logger (localhost_EBook_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_EBook_log. suffix=.txt timestamp=true / /Context /Context Bill Haake [EMAIL PROTECTED] 02/13/2004 12:03 PM Please respond to Tomcat Users List [EMAIL PROTECTED] To Tomcat Users List [EMAIL PROTECTED] cc Subject RE: jsp deployment You have the EBook context nested inside the default (ROOT). -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 11:50 AM To: Tomcat Users List Subject: Re: jsp deployment from server.xml (minus realm, user database resource and a couple of extraneous contexts): Server port=8005 shutdown=SHUTDOWN debug=0 !-- Service -- Service name=Tomcat-Standalone !-- Port 8080 Connector -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / !-- Apache Connector (mod_jk) -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Engine -- Engine name=Standalone defaultHost=localhost debug=0 !-- Engine logger (catalina_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ !-- Host (localhost) -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true !-- Host logger (localhost_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=localhost_log. suffix=.txt timestamp=true/ !-- ROOT context -- Context path= docBase=ROOT debug=0/ !-- EBook context -- Context path=/EBook docBase=EBook debug=0 reloadable=true crossContext=true !-- EBook logger (localhost_EBook_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_EBook_log. suffix=.txt timestamp=true / /Context /Context !-- examples context -- Context path=/examples docBase=examples debug=0 reloadable=true crossContext=true !-- examples logger (localhost_examples_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_examples_log
Re: jsp deployment
BAO RuiXian wrote: Jerry Ford wrote: Tomcat manager shows EBook is running. And, when I request it through Apache, Tomcat does serve it up. When I request it through port 8080, Tomcat says it's not available: I suggest for now you forget running via Apache totally, Agreed. since if it is not working directly from Tomcat, it cannot be running via Apache. What you see Tomcat is serving via Apache, actually it is not, rather the Apache itself is serving it. But Tomcat has to be serving up something; the servlets that are part of EBook do work and Apache can't serve them without Tomcat. You say Tomcat manager shows EBook is running, did you run localhost:8080//manager/list? Can you post the result of the url? Here is the output: OK - Listed applications for virtual host localhost /EBook:running:0:/usr/local/webserver/tomcat/webapps/EBook /manager:running:0:/usr/local/webserver/tomcat/server/webapps/manager /examples:running:0:examples /j_tools:running:0:/usr/local/webserver/webapps/j_tools /tomcat-docs:running:0:/usr/local/webserver/jakarta-tomcat-4.1.27/webapps/tomcat-docs /webdav:running:0:/usr/local/webserver/jakarta-tomcat-4.1.27/webapps/webdav /admin:running:0:/usr/local/webserver/tomcat/server/webapps/admin /:running:0:ROOT To further debug, can you do the following: 1. Make a 'test' directory under your webapps directory, i.e. paralell to examples and EBook; 2. Make a Context block in the server.xml file for 'test' by copy/paste/modify the Context block for examples; 3. Install this 'test' app by running localhost:8080/manager/install?war=test Then run localhost:8080/test, what happens? I get a Tomcat-generated directory listing for / Listing is, of course, empty, since there are no files in test. BTW, I really appreciate your help. Thanks. Best Bao Workshttp://localhost/EBook Doesn't workhttp://localhost:8080/EBook Works---http://localhost/examples/jsp Works---http://localhost:8080/examples/jsp Jerry BAO RuiXian wrote: Jerry Ford wrote: Sorry, that's a cut-and-paste error that does not appear in the real server.xml. Only one /context end tag; the root context is closed before the EBook context begins: context... / The configuration seems okay then. BTW, can you run http://localhost:8080/manager/list to see what apps you have installed? If you can not find 'EBook', then you need to install it by running http://localhost:8080/manager/install?war=EBook Best Bao - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Yes, I agree, Apache is an unnecessary complication for the moment and I am focused now on getting things to work through port 8080. But Tomcat does serve up pages when I run the app through Apache---for one thing, the error messages are Tomcat-generated, not Apache, and for another, the servlets do work, which Apache cannot make happen without Tomcat. I don't fully understand the invoker servlet myself, but here's what I think I know: The invoker mapping only applies to servlets, not html or jsps, and the servlets are working (at least through Apache). If the invoker mapping specifies /servlets/* then servlets must be included in the URL. By taking it out of the invoker mapping, it does not need to be included in the URL. So, http://localhost/servlets/do_something is required if the mapping is as you say it should be, and http://localhost/do_something is the URL if the mapping is as I have it. Is that not correct? Jerry Parsons Technical Services wrote: Tomcat manager shows EBook is running. And, when I request it through Apache, Tomcat does serve it up. When I request it through port 8080, Tomcat says it's not available: I suggest for now you forget running via Apache totally, since if it is not working directly from Tomcat, it cannot be running via Apache. What you see Tomcat is serving via Apache, actually it is not, rather the Apache itself is serving it. You say Tomcat manager shows EBook is running, did you run localhost:8080//manager/list? Can you post the result of the url? Jerry, I think BAO is right about apache here. I have a stand alone setup and did a quick test of something. You have in your web.xml: servlet-mapping servlet-nameinvoker/servlet-name url-pattern/*/url-pattern /servlet-mapping When I set mine to this I get 404 resource not found. Curiously, even though it gave a 404 resource not found, the manager showed it running. But with this it works fine. servlet-mapping servlet-nameinvoker/servlet-name url-pattern/servlet/*/url-pattern /servlet-mapping I had this same problem myself. Sorry I didn't spot it sooner. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Well, that's odd I followed your advice, BAO RuiXian. I created a dirctory called test and deployed it, with successful results as noted in previous e-mail. Since it did deploy successfully, I wondered what would happen if I copied the contents of the EBook directory---all of it, including html, jps, servlets, and xml files---into the test directory and ran the EBook app from there. And it worked. Everything, including the jsp file that triggered my initial question to the forum. The EBook app works find from the test directory, as the test webapp. Then I went a step further and configured Apache to recognize the test app. And it worked, too. So, my EBook app works whether called directly from Tomcat or from Tomcat via Apache, if deployed in the test directory, but not in the EBook directory, even though the context in server.xml is identical in every respect except directory name. I don't get it. Now I need to get it to work under the name EBook, not test. This is really strange. Jerry Jerry Ford wrote: BAO RuiXian wrote: Jerry Ford wrote: Tomcat manager shows EBook is running. And, when I request it through Apache, Tomcat does serve it up. When I request it through port 8080, Tomcat says it's not available: I suggest for now you forget running via Apache totally, Agreed. since if it is not working directly from Tomcat, it cannot be running via Apache. What you see Tomcat is serving via Apache, actually it is not, rather the Apache itself is serving it. But Tomcat has to be serving up something; the servlets that are part of EBook do work and Apache can't serve them without Tomcat. You say Tomcat manager shows EBook is running, did you run localhost:8080//manager/list? Can you post the result of the url? Here is the output: OK - Listed applications for virtual host localhost /EBook:running:0:/usr/local/webserver/tomcat/webapps/EBook /manager:running:0:/usr/local/webserver/tomcat/server/webapps/manager /examples:running:0:examples /j_tools:running:0:/usr/local/webserver/webapps/j_tools /tomcat-docs:running:0:/usr/local/webserver/jakarta-tomcat-4.1.27/webapps/tomcat-docs /webdav:running:0:/usr/local/webserver/jakarta-tomcat-4.1.27/webapps/webdav /admin:running:0:/usr/local/webserver/tomcat/server/webapps/admin /:running:0:ROOT To further debug, can you do the following: 1. Make a 'test' directory under your webapps directory, i.e. paralell to examples and EBook; 2. Make a Context block in the server.xml file for 'test' by copy/paste/modify the Context block for examples; 3. Install this 'test' app by running localhost:8080/manager/install?war=test Then run localhost:8080/test, what happens? I get a Tomcat-generated directory listing for / Listing is, of course, empty, since there are no files in test. BTW, I really appreciate your help. Thanks. Best Bao Workshttp://localhost/EBook Doesn't workhttp://localhost:8080/EBook Works---http://localhost/examples/jsp Works---http://localhost:8080/examples/jsp Jerry BAO RuiXian wrote: Jerry Ford wrote: Sorry, that's a cut-and-paste error that does not appear in the real server.xml. Only one /context end tag; the root context is closed before the EBook context begins: context... / The configuration seems okay then. BTW, can you run http://localhost:8080/manager/list to see what apps you have installed? If you can not find 'EBook', then you need to install it by running http://localhost:8080/manager/install?war=EBook Best Bao - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Good suggestions, but, no, didn't work. There are no config issues preventing Tomcat from serving files from my webapp---html and servlets all work. And I know Tomcat is serving jsp files correctly; Tomcat's default examples work. Tomcat simply will not serve my .jsp file regardless of filetype (tried it as .txt). Permissions and file ownership are identical to the permissions of the Tomcat example .jsp files, which do work. I restart Tomcat everytime I make a change. Still get the 404 when I call the jsp, even though the html files in the same directory work fine, as do the servlets in the same webapp space. Jerry Parsons Technical Services wrote: Jerry, Just for a test, change the file name to end with .txt and see if the page is displayed. If it still fails. I would double check the permissions/ownership on that file. If it works, then try a restart. After a restart if it still fails, check your configs for an entry that might be blocking or redirecting the request. Just a novice throwing out ideas. Doug Parsons www.parsonstechnical.com - Original Message - From: Jerry Ford [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, February 12, 2004 2:33 PM Subject: Re: jsp deployment Permissions on the .jsp file are identical to permissions on all of the html, javascript, and servlet class files in the webapp, all of which work: -rw--r--r-- owner/group is jford:user (which is the uid under which tomcat was started). And I know it will serve .jsp's, the Tomcat example .jsp's all work. Jerry QM wrote: : Tomcat chokes when the jsp is requested. I get a 404 : error, the requested resoruce is not available. : : What do I need to configure to get Tomcat to serve the jsp? Chances are it's a permissions issue on the file. (Unless you've tweaked Tomcat's config, it should already be able to serve JSPs.) -QM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Logs show class-not-found exception for open.jsp. Which brings me back to my original question---what do I need to configure to let Tomcat know about this jsp? It already knows where my webapp is and is able to serve my servlets just fine, as well as the html files that are in the same directory as the jsp. thanks. Jerry Thomas Tang wrote: Hi all, Do the logs give any indication as to where Tomcat is looking for the jsp files? A 404 error does not sound like a permissions problem. It sounds like a context setting might be off somewhere. Thomas Jerry Ford [EMAIL PROTECTED] 02/13/2004 11:03 AM Please respond to Tomcat Users List [EMAIL PROTECTED] To Tomcat Users List [EMAIL PROTECTED] cc Subject Re: jsp deployment Good suggestions, but, no, didn't work. There are no config issues preventing Tomcat from serving files from my webapp---html and servlets all work. And I know Tomcat is serving jsp files correctly; Tomcat's default examples work. Tomcat simply will not serve my .jsp file regardless of filetype (tried it as .txt). Permissions and file ownership are identical to the permissions of the Tomcat example .jsp files, which do work. I restart Tomcat everytime I make a change. Still get the 404 when I call the jsp, even though the html files in the same directory work fine, as do the servlets in the same webapp space. Jerry Parsons Technical Services wrote: Jerry, Just for a test, change the file name to end with .txt and see if the page is displayed. If it still fails. I would double check the permissions/ownership on that file. If it works, then try a restart. After a restart if it still fails, check your configs for an entry that might be blocking or redirecting the request. Just a novice throwing out ideas. Doug Parsons www.parsonstechnical.com - Original Message - From: Jerry Ford [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, February 12, 2004 2:33 PM Subject: Re: jsp deployment Permissions on the .jsp file are identical to permissions on all of the html, javascript, and servlet class files in the webapp, all of which work: -rw--r--r-- owner/group is jford:user (which is the uid under which tomcat was started). And I know it will serve .jsp's, the Tomcat example .jsp's all work. Jerry QM wrote: : Tomcat chokes when the jsp is requested. I get a 404 : error, the requested resoruce is not available. : : What do I need to configure to get Tomcat to serve the jsp? Chances are it's a permissions issue on the file. (Unless you've tweaked Tomcat's config, it should already be able to serve JSPs.) -QM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Hmmm...when I go to http://localhost/mywebapp, it works fine. When I bypass Apache and go to http://localhost:8080, I get Tomcat's home page, and http://localhost:8080/examples/jsp, I get the Tomcat examples. But when I go to http://localhost:8080/mywebapp, I get 404, resource not available. Jerry BAO RuiXian wrote: Jerry Ford wrote: Good suggestions, but, no, didn't work. There are no config issues preventing Tomcat from serving files from my webapp---html and servlets all work. And I know Tomcat is serving jsp files correctly; Tomcat's default examples work. Have you tried run your jsp file directly from Tomcat instead of via Apache? How about you copy one of the jsp files from the example jsp files to this directory to see it still works? I think your problem is just very trivial, somewhere wrong. Best Bao Tomcat simply will not serve my .jsp file regardless of filetype (tried it as .txt). Permissions and file ownership are identical to the permissions of the Tomcat example .jsp files, which do work. I restart Tomcat everytime I make a change. Still get the 404 when I call the jsp, even though the html files in the same directory work fine, as do the servlets in the same webapp space. Jerry Parsons Technical Services wrote: Jerry, Just for a test, change the file name to end with .txt and see if the page is displayed. If it still fails. I would double check the permissions/ownership on that file. If it works, then try a restart. After a restart if it still fails, check your configs for an entry that might be blocking or redirecting the request. Just a novice throwing out ideas. Doug Parsons www.parsonstechnical.com - Original Message - From: Jerry Ford [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, February 12, 2004 2:33 PM Subject: Re: jsp deployment Permissions on the .jsp file are identical to permissions on all of the html, javascript, and servlet class files in the webapp, all of which work: -rw--r--r-- owner/group is jford:user (which is the uid under which tomcat was started). And I know it will serve .jsp's, the Tomcat example .jsp's all work. Jerry QM wrote: : Tomcat chokes when the jsp is requested. I get a 404 : error, the requested resoruce is not available. : : What do I need to configure to get Tomcat to serve the jsp? Chances are it's a permissions issue on the file. (Unless you've tweaked Tomcat's config, it should already be able to serve JSPs.) -QM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Yes, yes, and yes...JDK 1.4, $JAVA_HOME is set to /usr/java/j2sdk1.4.0, and Tomcat is able to compile the example jsps that come in the webserver package. Jerry David Ramsey wrote: Do you have a JDK installed? Do you have a JAVA_HOME environment variable set? Can Jasper find the java compiler (javac)? --- Jerry Ford [EMAIL PROTECTED] wrote: Logs show class-not-found exception for open.jsp. Which brings me back to my original question---what do I need to configure to let Tomcat know about this jsp? It already knows where my webapp is and is able to serve my servlets just fine, as well as the html files that are in the same directory as the jsp. thanks. Jerry Thomas Tang wrote: Hi all, Do the logs give any indication as to where Tomcat is looking for the jsp files? A 404 error does not sound like a permissions problem. It sounds like a context setting might be off somewhere. Thomas Jerry Ford [EMAIL PROTECTED] 02/13/2004 11:03 AM Please respond to Tomcat Users List [EMAIL PROTECTED] To Tomcat Users List [EMAIL PROTECTED] cc Subject Re: jsp deployment Good suggestions, but, no, didn't work. There are no config issues preventing Tomcat from serving files from my webapp---html and servlets all work. And I know Tomcat is serving jsp files correctly; Tomcat's default examples work. Tomcat simply will not serve my .jsp file regardless of filetype (tried it as .txt). Permissions and file ownership are identical to the permissions of the Tomcat example .jsp files, which do work. I restart Tomcat everytime I make a change. Still get the 404 when I call the jsp, even though the html files in the same directory work fine, as do the servlets in the same webapp space. Jerry Parsons Technical Services wrote: Jerry, Just for a test, change the file name to end with .txt and see if the page is displayed. If it still fails. I would double check the permissions/ownership on that file. If it works, then try a restart. After a restart if it still fails, check your configs for an entry that might be blocking or redirecting the request. Just a novice throwing out ideas. Doug Parsons www.parsonstechnical.com - Original Message - From: Jerry Ford [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, February 12, 2004 2:33 PM Subject: Re: jsp deployment Permissions on the .jsp file are identical to permissions on all of the html, javascript, and servlet class files in the webapp, all of which work: -rw--r--r-- owner/group is jford:user (which is the uid under which tomcat was started). And I know it will serve .jsp's, the Tomcat example .jsp's all work. Jerry QM wrote: : Tomcat chokes when the jsp is requested. I get a 404 : error, the requested resoruce is not available. : : What do I need to configure to get Tomcat to serve the jsp? Chances are it's a permissions issue on the file. (Unless you've tweaked Tomcat's config, it should already be able to serve JSPs.) -QM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
from server.xml (minus realm, user database resource and a couple of extraneous contexts): Server port=8005 shutdown=SHUTDOWN debug=0 !-- Service -- Service name=Tomcat-Standalone !-- Port 8080 Connector -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / !-- Apache Connector (mod_jk) -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Engine -- Engine name=Standalone defaultHost=localhost debug=0 !-- Engine logger (catalina_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ !-- Host (localhost) -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true !-- Host logger (localhost_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=localhost_log. suffix=.txt timestamp=true/ !-- ROOT context -- Context path= docBase=ROOT debug=0/ !-- EBook context -- Context path=/EBook docBase=EBook debug=0 reloadable=true crossContext=true !-- EBook logger (localhost_EBook_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_EBook_log. suffix=.txt timestamp=true / /Context /Context !-- examples context -- Context path=/examples docBase=examples debug=0 reloadable=true crossContext=true !-- examples logger (localhost_examples_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_examples_log. suffix=.txt timestamp=true/ /Context /Host /Engine /Service /Server Webapp's web.xml (complete): ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; !-- Java version of ebook generating utility. -- web-app display-nameCat's Eye EBook Builder/display-name description EBook generator web application /description servlet servlet-name book_builder /servlet-name servlet-class catseye.ebook.book_builder /servlet-class /servlet servlet servlet-name set_config /servlet-name servlet-class catseye.ebook.set_config /servlet-class /servlet servlet servlet-name get_config /servlet-name servlet-class catseye.ebook.get_config /servlet-class /servlet servlet-mapping servlet-nameinvoker/servlet-name url-pattern/*/url-pattern /servlet-mapping /web-app Thomas Tang wrote: Cut and paste your context settings. Thomas Jerry Ford [EMAIL PROTECTED] 02/13/2004 11:33 AM Please respond to Tomcat Users List [EMAIL PROTECTED] To Tomcat Users List [EMAIL PROTECTED] cc Subject Re: jsp deployment Hmmm...when I go to http://localhost/mywebapp, it works fine. When I bypass Apache and go to http://localhost:8080, I get Tomcat's home page, and http://localhost:8080/examples/jsp, I get the Tomcat examples. But when I go to http://localhost:8080/mywebapp, I get 404, resource not available. Jerry BAO RuiXian wrote: Jerry Ford wrote: Good suggestions, but, no, didn't work. There are no config issues preventing Tomcat from serving files from my webapp---html and servlets all work. And I know Tomcat is serving jsp files correctly; Tomcat's default examples work. Have you tried run your jsp file directly from Tomcat instead of via Apache? How about you copy one
Re: jsp deployment
No, root context is defined in a single, self-closing tag: context... / It's unchanged from Tomcat's default server.xml. But...on second look, there is an extra closing tag after Ebook's context in this cut-and-paste (I cut and paste in multiple steps; couldn't get the whole thing in one vi window): /context /context But the active server.xml does not have two of them, only one. Jerry Bill Haake wrote: You have the EBook context nested inside the default (ROOT). -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 11:50 AM To: Tomcat Users List Subject: Re: jsp deployment from server.xml (minus realm, user database resource and a couple of extraneous contexts): Server port=8005 shutdown=SHUTDOWN debug=0 !-- Service -- Service name=Tomcat-Standalone !-- Port 8080 Connector -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / !-- Apache Connector (mod_jk) -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Engine -- Engine name=Standalone defaultHost=localhost debug=0 !-- Engine logger (catalina_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ !-- Host (localhost) -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true !-- Host logger (localhost_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=localhost_log. suffix=.txt timestamp=true/ !-- ROOT context -- Context path= docBase=ROOT debug=0/ !-- EBook context -- Context path=/EBook docBase=EBook debug=0 reloadable=true crossContext=true !-- EBook logger (localhost_EBook_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_EBook_log. suffix=.txt timestamp=true / /Context /Context !-- examples context -- Context path=/examples docBase=examples debug=0 reloadable=true crossContext=true !-- examples logger (localhost_examples_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_examples_log. suffix=.txt timestamp=true/ /Context /Host /Engine /Service /Server Webapp's web.xml (complete): ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; !-- Java version of ebook generating utility. -- web-app display-nameCat's Eye EBook Builder/display-name description EBook generator web application /description servlet servlet-name book_builder /servlet-name servlet-class catseye.ebook.book_builder /servlet-class /servlet servlet servlet-name set_config /servlet-name servlet-class catseye.ebook.set_config /servlet-class /servlet servlet servlet-name get_config /servlet-name servlet-class catseye.ebook.get_config /servlet-class /servlet servlet-mapping servlet-nameinvoker/servlet-name url-pattern/*/url-pattern /servlet-mapping /web-app Thomas Tang wrote: Cut and paste your context settings. Thomas Jerry Ford [EMAIL PROTECTED] 02/13/2004 11:33 AM Please respond to Tomcat Users List [EMAIL PROTECTED] To Tomcat Users List [EMAIL PROTECTED] cc Subject Re: jsp deployment Hmmm...when I go to http://localhost/mywebapp, it works fine. When I bypass
Re: jsp deployment
Sorry, that's a cut-and-paste error that does not appear in the real server.xml. Only one /context end tag; the root context is closed before the EBook context begins: context... / Jerry Thomas Tang wrote: Bill is correct. This portions seems off. Try separating them. I dont think you should be seeing /Context followed by and another /Context. !-- ROOT context -- Context path= docBase=ROOT debug=0/ !-- EBook context -- Context path=/EBook docBase=EBook debug=0 reloadable=true crossContext=true !-- EBook logger (localhost_EBook_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_EBook_log. suffix=.txt timestamp=true / /Context /Context Bill Haake [EMAIL PROTECTED] 02/13/2004 12:03 PM Please respond to Tomcat Users List [EMAIL PROTECTED] To Tomcat Users List [EMAIL PROTECTED] cc Subject RE: jsp deployment You have the EBook context nested inside the default (ROOT). -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 11:50 AM To: Tomcat Users List Subject: Re: jsp deployment from server.xml (minus realm, user database resource and a couple of extraneous contexts): Server port=8005 shutdown=SHUTDOWN debug=0 !-- Service -- Service name=Tomcat-Standalone !-- Port 8080 Connector -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / !-- Apache Connector (mod_jk) -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Engine -- Engine name=Standalone defaultHost=localhost debug=0 !-- Engine logger (catalina_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ !-- Host (localhost) -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true !-- Host logger (localhost_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=localhost_log. suffix=.txt timestamp=true/ !-- ROOT context -- Context path= docBase=ROOT debug=0/ !-- EBook context -- Context path=/EBook docBase=EBook debug=0 reloadable=true crossContext=true !-- EBook logger (localhost_EBook_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_EBook_log. suffix=.txt timestamp=true / /Context /Context !-- examples context -- Context path=/examples docBase=examples debug=0 reloadable=true crossContext=true !-- examples logger (localhost_examples_log.txt) -- Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_examples_log. suffix=.txt timestamp=true/ /Context /Host /Engine /Service /Server Webapp's web.xml (complete): ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; !-- Java version of ebook generating utility. -- web-app display-nameCat's Eye EBook Builder/display-name description EBook generator web application /description servlet servlet-name book_builder /servlet-name servlet-class
jsp deployment
The webapp I am writing has until today used html pages, JavaScript, and servlets, but no jsp files. Now I want to add one, so I placed the file open.jsp in the webapp's root directory (where the html files are). I thought that's all I needed to do, but Tomcat chokes when the jsp is requested. I get a 404 error, the requested resoruce is not available. What do I need to configure to get Tomcat to serve the jsp? My setup is: Apache 1.3.27 - Tomcat 4.1.27 via mod_jk, on a Linux box. All Tomcat examples (jsps and servlets) work fine, my webapp servlets work fine. Apache config includes this statement: JkMount /mywebapp/* .jsp ajp13 (and anyway the error comes from Tomcat, so I know I'm getting through Apache). I have not made any jsp-related changes to my webapp's web.xml file, which is where I define the servlets. All the docs I have on Tomcat agree with this statement in the O'Reilly book Tomcat: The Definitive Guide: JSPs can be installed anywhere in a web applicationJSPs can be copied to the root of your web application or placed in any subdirectory other than WEB-INF. So here's my structure: $TOMCAT_HOME '---webapps '---mywebapp ...'---index.html ...'---open.jsp index.html hands off to open.jsp by way of this JasvaScript statement: document.location=open.jsp And Tomcat serves up the 404 error. What to do? Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jsp deployment
Permissions on the .jsp file are identical to permissions on all of the html, javascript, and servlet class files in the webapp, all of which work: -rw--r--r-- owner/group is jford:user (which is the uid under which tomcat was started). And I know it will serve .jsp's, the Tomcat example .jsp's all work. Jerry QM wrote: : Tomcat chokes when the jsp is requested. I get a 404 : error, the requested resoruce is not available. : : What do I need to configure to get Tomcat to serve the jsp? Chances are it's a permissions issue on the file. (Unless you've tweaked Tomcat's config, it should already be able to serve JSPs.) -QM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: javax.mail
Just a guess here, but have you tried using a fully qualified domain name for the host, as mysmtphost.mydomain.com? Jerry Duncan Smith wrote: Hi, sorry if this is the wrong mailing list but I think most people here are Java programmers so: I am using javax.mail to send a mail to myself if a particular problem occurs on the server. My code seems to work but, but it does not use the smtp server which I am specifying. I cannot find a problem in my code as it seems to be identical to examples which I have found. I use the line: props.put(mail.smtp.host, mysmtphost); to specify the smtp server (which is on a differant computer) but the mail is being sent through the smtp server running on the same machine as the jsp. Has anyone else had this problem at all, or am I just doing something wrong? -Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: javax.mail
Just a guess here, but have you tried using a fully qualified domain name for the host, as mysmtphost.mydomain.com? Jerry Duncan Smith wrote: Hi, sorry if this is the wrong mailing list but I think most people here are Java programmers so: I am using javax.mail to send a mail to myself if a particular problem occurs on the server. My code seems to work but, but it does not use the smtp server which I am specifying. I cannot find a problem in my code as it seems to be identical to examples which I have found. I use the line: props.put(mail.smtp.host, mysmtphost); to specify the smtp server (which is on a differant computer) but the mail is being sent through the smtp server running on the same machine as the jsp. Has anyone else had this problem at all, or am I just doing something wrong? -Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: javax.mail
Just a guess here, but have you tried using a fully qualified domain name for the host, as mysmtphost.mydomain.com? Jerry Duncan Smith wrote: Hi, sorry if this is the wrong mailing list but I think most people here are Java programmers so: I am using javax.mail to send a mail to myself if a particular problem occurs on the server. My code seems to work but, but it does not use the smtp server which I am specifying. I cannot find a problem in my code as it seems to be identical to examples which I have found. I use the line: props.put(mail.smtp.host, mysmtphost); to specify the smtp server (which is on a differant computer) but the mail is being sent through the smtp server running on the same machine as the jsp. Has anyone else had this problem at all, or am I just doing something wrong? -Duncan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: System.out.println, Where art thou?
System.out.println text should be going to the file catalina.out in tomcat's logs directory, if you haven't changed any of the default logging configurations. At least, that's where they go in my 4.1.27 setup. Jerry John B. Moore wrote: Moved up to Tomcat 4.1.18 (from 3.x) and I've seemed to have lost the ability to see stdout statments in the log files.. In addition my Log4j loging output failing to appear. (another issue, but maybe related..) what is most puzzling at this point is that basic System.out.printlin(some text here...); ..does not appear ANYWHERE!!! An obviously I need to resolve this issue first.. (as it may provide some hints as to what is happening to the configuration of Log4j..since I use basic out.println to debug the various configuration settings. ) I'm assuming/hopping I need to turn something on... (that was formerly default on in the previous version I was using) I added a SystemOutLogger to both the Host context and the specific webapp context.. nada.. (all that did was log stuff that was already showing up).. what is interesting is that when I use Tomcat IN JBuilder (version 4.1.27) all the logging shows up and all the expected log files show up.. Looking at the server.xml that is generated by JBuilder I can not see that it is setting anything special... obviously something is different. So.. anyone have any ideas as to how to surface the output of the basic System.out.println...??? Any clues as to what I can try next is appreciated.. John.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: $JAVA_HOME error
Tony: Try it with just the startup.sh command, without the leading sh. Jerry Tony Sutton wrote: Hi there, I'm new to using jakart. I'm trying to get jakart v4.1.29 to run under Mandrake 9.1 I have downloaded and installed JRE from Sun, version 1.4.2_03. The installation went well. Here's the output from my Linux box: [EMAIL PROTECTED] tony]$ which java /usr/java/j2re1.4.2_03/bin/java [EMAIL PROTECTED] tony]$ echo $JAVA_HOME /usr/java/j2re1.4.2_03 [EMAIL PROTECTED] tony]$ OK so far. However, I tried to start jakart by going to the jakarta-tomcat-4.1.29/bin/ directory and typed in: sh startup.sh I get this error message: [EMAIL PROTECTED] bin]$ sh startup.sh The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program [EMAIL PROTECTED] bin]$ I can't figure out what I am doing wrong. I have tried googling for it, but it came back very little. Does anyone know why I am getting this error message? Thanks, Tony Sutton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: writing a file from a servlet
Daniel: Great, got it, it works. Thanks. Jerry Daniel wrote: Hi Jerry, You can use: servletContext.getRealPath(/path_relative_to_webapp_root/); Regards, Daniel On Sun, 1 Feb 2004, Jerry Ford wrote: I want to write a config file from a servlet implemented in /usr/local/webserver/tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, to a myWebapp/conf directory. The directory exists, and there are no permissions issues---I can write the config file if I hardcode a full path to the file. The following works: FileWriter fwrite; try { fwrite = new File Writer(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. } catch(IOException e) { // ...etc. } But if I change the path in the new FileWriter statement to any of the following, it does not work: /myWebapps/conf (relative to tomcat's servlets root) conf/ (relative to the docBase declared in the webapp's context) ../../../../conf (relative to the class file) I get a FileNotFound...(No such file or directory) exception. What does tomcat consider to be the relative path to the myWebapp/conf directory? relative to what? BTW, this is a private, internal app that won't be deployed in a public website, so there are no concerns about writing files to the server's disk. But I want to reserve the option of deploying to a Windows machine or keeping it on the Linux box, and I don't want to be tied to a specific directory location on either box. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a file from a servlet
From a servlet implemented in tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, I am trying to write a config file to the directory myWebapp/conf. The conf directory does exist; and there are no permissions issues---I can write the file to the conf directory from the servlet if I hardcode the full path. The following code works: FileWriter fwrite; try { fwrite = new FileWriter(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. } catch(IOException e) { // ... etc. } But if I change the path in fwrite = new FileWriter() to ../../../../conf/ (making it relative to the class file) or to /myWebapp/conf/ (relative to tomcat's servlets root; with or without the leading /) or to conf/ (relative to the myWebapp directory, which is the docBase declared in the context element in server.xml), I get a FileNotFound (No such file or directory) exception. How do I make the path relative to the servlet, so I don't have to hard code the path? The app won't be deployed on a public web server, so writing a file to the server is not a problem, though I would like to have some flexibility about where things get deployed---may end up on a Windows machine, may stay on the Linux box. But I want to make that decision external to the code. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a file from a servlet
I want to write a config file from a servlet implemented in /usr/local/webserver/tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, to a myWebapp/conf directory. The directory exists, and there are no permissions issues---I can write the config file if I hardcode a full path to the file. The following works: FileWriter fwrite; try { fwrite = new FileWriter(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. } catch(IOException e) { // ...etc. } But if I change the path in the new FileWriter statement to any of the following, it does not work: /myWebapps/conf (relative to tomcat's servlets root) conf/ (relative to the docBase declared in the webapp's context) ../../../../conf (relative to the class file) I get a FileNotFound...(No such file or directory) exception. What does tomcat consider to be the relative path to the myWebapp/conf directory? relative to what? BTW, this is a private, internal app that won't be deployed in a public website, so there are no concerns about writing files to the server's disk. But I want to reserve the option of deploying to a Windows machine or keeping it on the Linux box, and I don't want to be tied to a specific directory location on either box. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a file from a servlet
I want to write a config file from a servlet implemented in /usr/local/webserver/tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, to a myWebapp/conf directory. The directory exists, and there are no permissions issues---I can write the config file if I hardcode a full path to the file. The following works: FileWriter fwrite; try { fwrite = new File Writer(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. } catch(IOException e) { // ...etc. } But if I change the path in the new FileWriter statement to any of the following, it does not work: /myWebapps/conf (relative to tomcat's servlets root) conf/ (relative to the docBase declared in the webapp's context) ../../../../conf (relative to the class file) I get a FileNotFound...(No such file or directory) exception. What does tomcat consider to be the relative path to the myWebapp/conf directory? relative to what? BTW, this is a private, internal app that won't be deployed in a public website, so there are no concerns about writing files to the server's disk. But I want to reserve the option of deploying to a Windows machine or keeping it on the Linux box, and I don't want to be tied to a specific directory location on either box. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a file from a servlet
From a servlet implemented in tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, I am trying to write a config file to the directory myWebapp/conf. The conf directory does exist; and there are no permissions issues---I can write the file to the conf directory from the servlet if I hardcode the full path. The following code works: FileWriter fwrite; fwrite = new FileWriter(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. But if I change the path to ../../../../conf/ (making it relative to the class file) or to /myWebapp/conf/ (relative to tomcat's servlets root; with or without the leading /) or to conf/ (relative to the myWebapp directory, which is the docBase declared in the context element in server.xml), I get a FileNotFound (No such file or directory) exception. How do I make the path relative to the servlet, so I don't have to hard code the path? The app won't be deployed on a public web server, so writing a file to the server is not a problem, though I would like to have some flexibility about where things get deployed---may end up on a Windows machine, may stay on the Linux box. But I want to make that decision external to the code. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a file from a servlet
From a servlet implemented in tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, I am trying to write a config file to the directory myWebapp/conf. The conf directory does exist; and there are no permissions issues---I can write the file to the conf directory from the servlet if I hardcode the full path. The following code works: FileWriter fwrite; try { fwrite = new FileWriter(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. } catch(IOException e) { // ... etc. } But if I change the path in fwrite = new FileWriter() to ../../../../conf/ (making it relative to the class file) or to /myWebapp/conf/ (relative to tomcat's servlets root; with or without the leading /) or to conf/ (relative to the myWebapp directory, which is the docBase declared in the context element in server.xml), I get a FileNotFound (No such file or directory) exception. How do I make the path relative to the servlet, so I don't have to hard code the path? The app won't be deployed on a public web server, so writing a file to the server is not a problem, though I would like to have some flexibility about where things get deployed---may end up on a Windows machine, may stay on the Linux box. But I want to make that decision external to the code. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a file from a servlet
From a servlet implemented in tomcat/webapps/myWebapp/WEB-INF/classes/my/package/myWebapp.class, I am trying to write a config file to the directory myWebapp/conf. The conf directory does exist; and there are no permissions issues---I can write the file to the conf directory from the servlet if I hardcode the full path. The following code works: FileWriter fwrite; try { fwrite = new FileWriter(/usr/local/webserver/tomcat/webapps/myWebapp/conf/ + project + .conf); // ...etc. } catch(IOException e) { // ... etc. } But if I change the path in fwrite = new FileWriter() to ../../../../conf/ (making it relative to the class file) or to /myWebapp/conf/ (relative to tomcat's servlets root; with or without the leading /) or to conf/ (relative to the myWebapp directory, which is the docBase declared in the context element in server.xml), I get a FileNotFound (No such file or directory) exception. How do I make the path relative to the servlet, so I don't have to hard code the path? The app won't be deployed on a public web server, so writing a file to the server is not a problem, though I would like to have some flexibility about where things get deployed---may end up on a Windows machine, may stay on the Linux box. But I want to make that decision external to the code. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Really DUMB question...
Robert: They're *from* anybody who posts to the list. Filter on messages where to and cc include tomcat-user. Jerry Robert Keddie wrote: Im trying to make rules for the emails form this list and I looked at headers... Which dang address are these emails coming from?! Thanks. Robert Keddie Web Development Board of County Commissioners Marion County Florida - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RTFM
Okay, from this detailed description---which sounds to me like it should work---here's my SWAG (silly wild-ass guess): After your response.sendRedirect() in the servlett, do you, um, well, include an explicit return statement? Jerry Jerald Powel wrote: OK, what I am trying to do is simple in theory. I have loaded in the browser an app - app1/. From a servlet in app1 I want to simply redirect to another app (app2 - different context) - to be loaded in the same browser window. By which means I forward I'm not fussed. Currently I am using RequestDispatcher or response.sendRedirect from a servlet in app1. But in the window, app2 appeqars to be loading in the address bar, but app1 is in fact loaded but with broken image links/error messages etc. So it appears to looking in the right place...just for the wrong things! I have checked docBase for each context in server.xml - they are fine. Each app runs fine if loaded from new windows, but when I try to link the two togethertrouble. Any thoughts please? I am ready to throw in the towel! G. Justin Ruthenbeck [EMAIL PROTECTED] wrote: It'd difficult from your poast to figure out what you're trying to accomplish. The phrase forward control from one context to another is quite ambiguous: * Are you trying to create a response that includes output from resources from multiple contexts? * While using one app, do you want to direct the user to pages in a different app? * Are you talking client side or server side? * Can you give us the scenario you're addressing? Often people ask questions that aren't phrased properly, so it's important to understand exactly what you're trying to do before going off and suggesting one of a hundred different possible answers. justin BTW: I would suggest trying not to be guilty of stiring interest any more. It's not looked fondly upon by those who can most help you. Your previous post was not answered because it was ambiguous, so it'd be best to include copious information from the beginning (so you don't have to wait so long for a reply or cause subject pollution). At 04:45 PM 1/14/2004, you wrote: Both! The answer to my query may well lie in my ignorance and I was willing ot accept this, hence the subject title. But I am guilty of hoping it stired more of an interest than a previous post onthe same topic, with different subject (no replies)...and I still dont have the answer! I guess it just shows how much perceptions can vary with Email. I read your first paragraph and formed the impression that the subject was designed to generate additional interest and to work to prioritize your request for help. -Original Message- From: Jerald Powel [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 5:33 PM To: Tomcat Users List Subject: RE: RTFM in traditional fashion, the subject was related to the contents of body of the email. George Sexton wrote:I generally don't think it is required to resort to things like this to get our attention. -Original Message- From: Jerald Powel [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 3:11 PM To: Tomcat Users List Subject: RTFM Hi, Now I have your attention, will someone tell me if it is possible to forward control (either by JSP or Servlet) from one context to another, in the same browser window? i.e: - Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
webapp works through Apache, not Tomcat directly
I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
Chakravarthy, Sundar wrote: Could be a permission issue: docBase=/usr/local/webserver/webapps/MyApp Tomcat is unable to read directory under =/usr/local/webserver/webserver. Both /usr/local/webserver/webapps where MyApp is located and $TOMCAT_HOME/webapps where examples are located are world readable: drwxr-xr-x Jerry -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 1:44 PM To: Tomcat Users List Subject: webapp works through Apache, not Tomcat directly I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
The symbolic link is to $TOMCAT_HOME (in /usr/local/webserver, I've defined symbolic links to both tomcat and apache: tomcat - jakarta.tomcat-4.1.27, and apache-apache_1.3.27), and Tomcat has no problem using it. It just won't run my webapp when called directly through port 8080. The webapp works fine when the request comes through Apache. It's still Tomcat that runs it and its servlet. Jerry Daniel Gibby wrote: Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie needing help in deploying servlet
David: Try this; In your server.xml, add this context to the Host element: Context path=/testapp docBase=/webapps/testapp reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_testapp_log. suffix=.txt timestamp=true / /Context Create your web.xml in testapp/WEB_INF as follows: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; web-app display-nametest app/display-name description My test web application. /description servlet servlet-name Testservlet /servlet-name servlet-class Testservlet.class /servlet-class /servlet servlet-mapping servlet-nameinvoker/servlet-name url-pattern/*/url-pattern /servlet-mapping /web-app Shutdown and restart Tomcat then direct your browser to: http://localhost:8080/testapp/form.html (If you want your URL to be .../servlet/form.html, replace the asterisk with the word servlet in the servlet-mapping element of the testapp web.xml file.) Jerry David wrote: I'm trying tomcat-4.1.24 out and have it up and running ok. But when I try to deploy a new servlet it is not seen (404) by tomcat. I have it like this: $CATALINA_HOME/webapps/testapp/form.html $CATALINA_HOME/webapps/testapp/WEB-INF/classes/Testservlet.class I can access the form.html-page on http://localhost:8080/testapp/form.html but not the servlet on http://localhost:8080/testapp/servlet/Testservlet. If I put the class in $CATALINA_HOME/examples/WEB_INF/classes/ it works ok. I've restarted tomcat, tried it with and without a web.xml in WEB-INF, tried to add it as a Context in server.xml but I still just gets that awful 404... Could someone give me any hints please? regards /David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie needing help in deploying servlet
Perhaps I mispoke about prevserving servlet in the URL; instead of replacing the asterisk in my sample web.xml, add servlet to it: /servlet/* Jerry Jerry Ford wrote: David: Try this; In your server.xml, add this context to the Host element: Context path=/testapp docBase=/webapps/testapp reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_testapp_log. suffix=.txt timestamp=true / /Context Create your web.xml in testapp/WEB_INF as follows: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; web-app display-nametest app/display-name description My test web application. /description servlet servlet-name Testservlet /servlet-name servlet-class Testservlet.class /servlet-class /servlet servlet-mapping servlet-nameinvoker/servlet-name url-pattern/*/url-pattern /servlet-mapping /web-app Shutdown and restart Tomcat then direct your browser to: http://localhost:8080/testapp/form.html (If you want your URL to be .../servlet/form.html, replace the asterisk with the word servlet in the servlet-mapping element of the testapp web.xml file.) Jerry David wrote: I'm trying tomcat-4.1.24 out and have it up and running ok. But when I try to deploy a new servlet it is not seen (404) by tomcat. I have it like this: $CATALINA_HOME/webapps/testapp/form.html $CATALINA_HOME/webapps/testapp/WEB-INF/classes/Testservlet.class I can access the form.html-page on http://localhost:8080/testapp/form.html but not the servlet on http://localhost:8080/testapp/servlet/Testservlet. If I put the class in $CATALINA_HOME/examples/WEB_INF/classes/ it works ok. I've restarted tomcat, tried it with and without a web.xml in WEB-INF, tried to add it as a Context in server.xml but I still just gets that awful 404... Could someone give me any hints please? regards /David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
The linux equivalent of shared files is to make them world readable, which the webapp directory and all files in it are: drwxr-xr-x Still doesn't work. Jerry FRANCOIS Dufour wrote: FOR MEE I AD TO SHARE FILES THAT I WANT TO BEE ACESS FROM THE WEB VIA:8080 IF I DONT SHARE THE FILE IT COMME OUT THE RESOURCE IS NOT AVAILABLE COULD IT BEE THIS ON YOUR PLATFORM TOO WONDERING ON OS=XP ITS LIKE THAT [EMAIL PROTECTED] crazy-wilys webmaster From: Daniel Gibby [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: webapp works through Apache, not Tomcat directly Date: Tue, 06 Jan 2004 12:55:34 -0800 Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: webapp works through Apache, not Tomcat directly
No. /usr/local/webserver/webapps/MyApp Jerry Ben Souther wrote: Are the files in a particular user's directory? I.E: /home/someUser On Tuesday 06 January 2004 09:28 pm, you wrote: The linux equivalent of shared files is to make them world readable, which the webapp directory and all files in it are: drwxr-xr-x Still doesn't work. Jerry FRANCOIS Dufour wrote: FOR MEE I AD TO SHARE FILES THAT I WANT TO BEE ACESS FROM THE WEB VIA:8080 IF I DONT SHARE THE FILE IT COMME OUT THE RESOURCE IS NOT AVAILABLE COULD IT BEE THIS ON YOUR PLATFORM TOO WONDERING ON OS=XP ITS LIKE THAT [EMAIL PROTECTED] crazy-wilys webmaster From: Daniel Gibby [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: webapp works through Apache, not Tomcat directly Date: Tue, 06 Jan 2004 12:55:34 -0800 Maybe you are using a symbolic link and tomcat 4 doesn't follow them by default because of performance. Daniel Gibby Jerry Ford wrote: I have a webapp deployed in Tomcat 4.1.27 which I am able to reach through Apache 1/3/27 (via mod_jk; sorry, didn't build it myself, obtained it as a binary and don't know version---how can I tell?) but cannot reach it by going directly to Tomcat. Tomcat is configured to listen directly on port 8080 and through mod_jk on port 8009 and in fact I can reach and execute the example servlets by going to either http://localhost:8080/examples/servlets or http://localhost/examples servlets. I can reach my webapp by going to http://localhost/MyApp. But when I try to reach http://localhost:8080/MyApp, Tomcat reports resource not available. The only difference (that I can recall) is that the examples are in their default location, $TOMCAT_HOME/webapps/examples, while my app has been moved to /usr/local/webserver/webapps/MyApp. The context to MyApp in server.xml is identical to the examples context except for path and name: Context path=/MyApp docBase=/usr/local/webserver/webapps/MyApp debug=0 reloadable=true crossContext=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_MyApp_log. suffix=.txt timestamp=true / /Context Nothing is written to the MyApp log when I try to access the app through port 8080 (or when I successfully access it through Apache, either, for that matter). All are running under Linux (RedHat 9.0). Any suggestions about what's wrong? While this condition might otherwise be acceptable (I don't really want to use port 8080), it appears to be interfering with the setting and reading of cookies---I can set them on one page but cannot read them from another, even though Mozilla's cookie manager shows them to be (apparently correctly) configured. Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: servlet gets smtp relay denied error
Thanks for the ideas, all are welcome :) See answers to your questions inline: Doug Parsons wrote: When I invoke it from a browser on the same network as the server, it works as expected. An email is sent to the specified address, with the attachment. But when I invoke it from a browser outside of my network, the message does not get sent. I don't have first hand experience in this class, but I got a theory. One possible problem is that your mail server is not looking at the connection to determine if it is a relay but at the message. Have the servlet write out the text of the message to a file or console OR look at one of the messages sent from inhouse to see how the message is formed. Good idea. Will try it. Also does/can your mail server send a response to the address attempting the relay? That could help determine why the mail server thinks it's a relay. The mail server is configured to deny relays for anybody not on the LAN, but there is no relay request---the servlet runs on the same box as the smtp server (which is, in fact, on the same box as my Apache, Tomcat and DNS servers). Why does it matter where the browser that sends the request resides? Now for a real stretch, does your server have a public or private IP assigned or both? Both. Server sits behind a router/firewall, with a private IP, router has public IP and forwards mail, and http traffic to the server. If both, then consider that the request is being associated with the public IP when attached from outside and the private when from inside. If TC is using the public IP in the request to the mail server then is the mail server set to allow a relay from it's public IP? Not such a wild idea. You might be on to something here. Not currently configured to relay from the external address. Not sure that's what I want, either---isn't that a security hole? to relay from a public address? Will need to freshen up on sendmail before I take that step, but definitely worth pursuing. Thanks again. Jerry I know this might end up being a bunch of fertilizer, but no one had resonded and every now and then I get lucky. Good Luck Doug Parsons SCJP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: servlet gets smtp relay denied error
Doug Parsons wrote: Now for a real stretch, does your server have a public or private IP assigned or both? If both, then consider that the request is being associated with the public IP when attached from outside and the private when from inside. If TC is using the public IP in the request to the mail server then is the mail server set to allow a relay from it's public IP? I know this might end up being a bunch of fertilizer, but no one had resonded and every now and then I get lucky. Doug: You got lucky---I added the external IP address to the sendmail relay_domains file, and boom...it works. Still would like some input from a sendmail guru as to the security issues involved in allowing relays from a public address, but, hey, it works. Thanks. Jerry Good Luck Doug Parsons SCJP - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MOD_JK (Apache+Tomcat)
Here's how I did it: http://www.katzenjammer.us/~jford/apache/tomcat/connectors/mod_jk_setup.shtml Not exactly your setup (I use Apache 1.3.27 and Red Hat 9.0) but maybe it will help. Jerry HARI OM wrote: any update on this? - Original Message - From: HARI OM [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 30, 2003 10:16 AM Subject: MOD_JK (Apache+Tomcat) Hello, I am using APache 2.0.47 and Tomcat 4.1.27 on SuSE Linux 8.1 I am working on the Connector MOD_JK.SO which I build from the source and put in /modules directory. When I run my Tomcat first and then Apache and then acceess http://My.domian.name/kuki it does not work... it says Page cannot be found wonder why? I also try to see MOD_JK.LOG file but I cannot find this file anywhere. Can anyone help me out in connecting Apache and Tomncat. Here are my Config Files: --- SERVER.XML --- # added following after Server Port=8005 Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=/usr/local/apache2/modules/mod_jk.so jkDebug=info workersConfig=/usr/local/tomcat4/conf/jk/workers.properties jkLog=/usr/local/tomcat4/logs/mod_jk.log/ Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Host name=my.domain.name debug=0 appBase=webapps unpackWARs=true autoDeploy=true Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true / Context path=/kuki docBase=/home/kuki/kuki/webapps/kuki reloadable=true ~~~ --- WORKERS.PROPERTIES --- workers.CATALINA_HOME=/usr/local/tomcat4 workers.java_home=$(JAVA_HOME) ps=/ worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=my.domain.name worker.ajp13.type=ajp13 worker.ajp13.lbfactor=5 ~~~ --- MOD_JK.CONF this file is AUTO GENERATED --- ## Auto generated on Mon Dec 29 14:10:45 MST 2003## IfModule !mod_jk.c LoadModule jk_module /usr/local/apache2/modules/mod_jk.so /IfModule JkWorkersFile /usr/local/tomcat4/conf/jk/workers.properties JkLogFile /usr/local/tomcat4/logs/mod_jk.log JkLogLevel info VirtualHost my.domain.name ServerName my.domain.name JkMount /kuki ajp13 JkMount /kuki/* ajp13 JkMount /examples ajp13 JkMount /examples/* ajp13 /VirtualHost ~~~ HTTPD.CONF Listen My.IP.ADDR.ESS:80 IfModule !mod_jk.c LoadModule jk_module modules/mod_jk.so /IfModule ServerName my.domain.name:80 JkWorkersFile /usr/local/tomcat4/conf/jk/workers.properties JkLogFile /usr/local/apache2/logs/mod_jk.log JkLogLevel debug JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /kuki ajp13 JkMount /kuki/* ajp13 ~~~ Can anyone please GUIDE me on this Connection Process? THANKS! and HAPPY NEW YEAR! HARI OM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MOD_JK (Apache+Tomcat)
Hari: You're trying to do too much too soon. Get the Apache - Tomcat connection through mod_jk to work before you try to get your own webapp to work. Use the Tomcat example servlets to verify that mod_jk is correctly installed and functional. If you can run the servlets through Apache (without :8080 in the URL) then you know mod_jk is okay, and you can focus exclusively on your webapp. Webapp deployment and mod_jk are both complicated enough on their own without trying to mix the issues together. Jerry Hari Om wrote: Hello, I am using APache 2.0.47 and Tomcat 4.1.27 on SuSE Linux 8.1 I am working on the Connector MOD_JK.SO which I build from the source and put in /modules directory. When I run my Tomcat first and then Apache and then acceess http://My.domian.name/kuki it does not work... it says Page cannot be found wonder why? I also try to see MOD_JK.LOG file but I cannot find this file anywhere. Can anyone help me out in connecting Apache and Tomncat. Here are my Config Files: --- SERVER.XML --- # added following after Server Port=8005 Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=/usr/local/apache2/modules/mod_jk.so jkDebug=info workersConfig=/usr/local/tomcat4/conf/jk/workers.properties jkLog=/usr/local/tomcat4/logs/mod_jk.log/ Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Host name=my.domain.name debug=0 appBase=webapps unpackWARs=true autoDeploy=true Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true / Context path=/kuki docBase=/home/kuki/kuki/webapps/kuki reloadable=true ~~~ --- WORKERS.PROPERTIES --- workers.CATALINA_HOME=/usr/local/tomcat4 workers.java_home=$(JAVA_HOME) ps=/ worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=my.domain.name worker.ajp13.type=ajp13 worker.ajp13.lbfactor=5 ~~~ --- MOD_JK.CONF this file is AUTO GENERATED --- ## Auto generated on Mon Dec 29 14:10:45 MST 2003## IfModule !mod_jk.c LoadModule jk_module /usr/local/apache2/modules/mod_jk.so /IfModule JkWorkersFile /usr/local/tomcat4/conf/jk/workers.properties JkLogFile /usr/local/tomcat4/logs/mod_jk.log JkLogLevel info VirtualHost my.domain.name ServerName my.domain.name JkMount /kuki ajp13 JkMount /kuki/* ajp13 JkMount /examples ajp13 JkMount /examples/* ajp13 /VirtualHost ~~~ HTTPD.CONF Listen My.IP.ADDR.ESS:80 IfModule !mod_jk.c LoadModule jk_module modules/mod_jk.so /IfModule ServerName my.domain.name:80 JkWorkersFile /usr/local/tomcat4/conf/jk/workers.properties JkLogFile /usr/local/apache2/logs/mod_jk.log JkLogLevel debug JkMount /examples ajp13 JkMount /examples/* ajp13 JkMount /kuki ajp13 JkMount /kuki/* ajp13 ~~~ Can anyone please GUIDE me on this Connection Process? THANKS! and HAPPY NEW YEAR! HARI OM _ Get reliable dial-up Internet access now with our limited-time introductory offer. http://join.msn.com/?page=dept/dialup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
servlet gets smtp relay denied error
I have written a JavaMail servlet to mail documents at user request. (User selects a document from the web page and enters an email address; when the Mail it now button is clicked, the servlet is called and the document sent as an attachment to an email message.) The servlet is deployed as a Tomcat webapp, which is called by Apache through mod_jk.. When I invoke it from a browser on the same network as the server, it works as expected. An email is sent to the specified address, with the attachment. But when I invoke it from a browser outside of my network, the message does not get sent. Catalina.out shows the servlet throwing the following exceptions: Transport exception: javax.mail.SendFailedException: Sending failed; nested exception is: class javax.mail.SendFailedException: Invalid Addresses; nested exception is: class javax.mail.SendFailedException: 550 5.7.1 [EMAIL PROTECTED]... Relaying denied The email address is correct and valid---I can send a test message and receive it at that address. The mail server is configured to deny relays for anybody not on the LAN, but there is no relay request---the servlet runs on the same box as the smtp server (which is, in fact, on the same box as my Apache, Tomcat and DNS servers). Why does it matter where the browser that sends the request resides? Thanks for whatever help you can offer. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Context docBase + linux
Algirdas: Maybe this will help: http://www.katzenjammer.us/~jford/apache/tomcat/webapps.pdf Jerry Algirdas M. wrote: Hello, I've created user /home/webapptest (with WEB-INF/classes, etc.) for java web applications and added in server.xml line Context docBase=/home/webapptest path=/w... restarted Tomcat. And application with path /w doesn't work. Tomcat logs are showing: StandardContext[/w]: Error initializing resources: Document base /home/webapptest does not exist or is not a readable directory How to do that directory readable? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: admin app is forbidden
Yes, both admin and manager roles are defined in tomcat-users.xml. The manager app uses the same auth mechanism, doesn't it? But manager works, and admin doesn't. Jerry [EMAIL PROTECTED] wrote: Jerry Ford wrote: I have Tomcat 4.1.27 running with Apache 1.3.27, using mod_jk, on a Linux box (Red Hat 9.0, but custom-installed Apache and Tomcat in /usr/local). I am able to run Tomcat's example servlets, as well as my own custom servlets (installed as a webapp), and the Manager webapp, but when I try to view the Admin app, I get a 403 - resource has been forbidden message. http://localhost/manager works fine, login screen is displayed, I log in and the app runs, but http://localhost/admin is forbidden to me. I cannot find anything in the configs that would allow one but prohibit the other. The Manager app shows /admin as running, and so do the logs. I just can't get to it. Can anyone tell me why I can't even get to the login screen before the admin app rejects my attempt? Thanks. Jerry Did you already insert following lines into your $CatalinaHome/conf/tomcat-users.xml? role rolename=admin/ user username=somebody password=tomcat roles=admin/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MOD_JK2 and MOD_JK on SuSE
do you still have the Coyote connector defined in the tomcat server.xml? Hari Om wrote: Thanks Jerry I tried to delete the MOD_JK2.SO from my APACHE/MODULESA Directory...but still my CATALINA.OUT files hsows reference of it wonder why. From: Jerry Ford [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [EMAIL PROTECTED] Re: MOD_JK2 and MOD_JK on SuSE Date: Wed, 24 Dec 2003 14:07:31 -0800 Hari: To remove mod_jk2, just delete mod_jk2.so from your apache/libexec directory and delete the references to it from your Apache config (httpd.conf). As for tomcat continuing to listen, that's because you have a mod_jk2 connector defined in tomcat's server.xml. Just because tomcat is listening for it does not mean mod_jk2 is working. Somebody else will have to address the questions about value---I don't use mod_jk2, I have mod_jk, but I also don't use apache 2.x, I have apache 1.3. I believe jk2 is designed for apache 2. As for jk2 references in jk configs, yes, jk2 shows up in my catalina.out, too, and I've never installed mod_jk2. It appears to just be some sloppy reference in a log message. It doesn't mean anything significant. I mean, it all still works. :) Jerry Hari Om wrote: I am using Apache 2.0.47 and Tomcat 4.1.27 and JDK 1.4 on SuSE Linux 8.0. I would like to use Connector for integrating Apache Tomcat. I have installed MOD_JK2 and want to get rid of it. How can I uninstall it? WHen I run my Tomcat it still refers to JK2 settings. I wanted to use JK instead. Can anyone please help me on this. Few more questions: 1) Is it worth using MOD_JK2 v/s MOD_JK? 2) I already installed MOD_JK2 and it does NOT seems to WORK...so wanted to get rid of it. I wanted to see if MOD_JK works. How is this possible? Deleting the jk2.properties and worker2.properties DOES NOT WORKcatalina.out file still shows TOMCAT is refereing to JK as shown below: --- INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 24, 2003 11:33:56 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Dec 24, 2003 11:33:56 AM org.apache.jk.server.JkMain start --- Can anyone please Help Me. Thanks and Merry XMAS! HARI OM _ Enjoy a special introductory offer for dial-up Internet access limited time only! http://join.msn.com/?page=dept/dialup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - The official User-To-User support forum of the Apache HTTP Server Project. See URL:http://httpd.apache.org/userslist.html for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Worried about inbox overload? Get MSN Extra Storage now! http://join.msn.com/?PAGE=features/es - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MOD_JK2 and MOD_JK on SuSE
Hari: Not sure what you are looking for at this point. As I recall, after you removed mod_jk2.so from your $APACHE_HOME/libexec directory and removed references to mod_jk2 from httpd.conf, you were still seeing JK2 references in catalina.out. Is that what you are still wondering about? The answer is, it's because you still have the Coyote connector and listener elements defined in tomcat's server.xml file. Catalina.out is tomcat's log file, so as long as you define a Coyote connector in the server.xml file you're going to se JK/JK2 references there, regardless of whether or not you are actually still using mod_jk2. That only means tomcat is listening for handoffs from Apache. Since you no longer have mod_jk2.so installed, there's nothing for tomcat to hear, but that doesn't stop it from listening. Put comment strings around those elements ( !-- ... -- ) and restart Tomcat, then check your catalina.out. The references to JK should be gone. Jerry Hari Om wrote: Any update son the following: Thanks! These are the ONLY things I added to my SERVER.XML: Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=/usr/local/apache2/modules/mod_jk.so jkDebug=info workersConfig=/usr/local/tomcat4/conf/jk/workers.properties jkLog=/usr/local/tomcat4/logs/mod_jk.log/ Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true / THANKS! HARI OM From: Hari Om [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [EMAIL PROTECTED] Re: MOD_JK2 and MOD_JK on SuSE Date: Fri, 26 Dec 2003 17:59:07 + Thanks! These are the ONLY things I added to my SERVER.XML: Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=/usr/local/apache2/modules/mod_jk.so jkDebug=info workersConfig=/usr/local/tomcat4/conf/jk/workers.properties jkLog=/usr/local/tomcat4/logs/mod_jk.log/ Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true / THANKS! HARI OM From: Jerry Ford [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: [EMAIL PROTECTED] Re: MOD_JK2 and MOD_JK on SuSE Date: Fri, 26 Dec 2003 09:38:09 -0800 do you still have the Coyote connector defined in the tomcat server.xml? Hari Om wrote: Thanks Jerry I tried to delete the MOD_JK2.SO from my APACHE/MODULESA Directory...but still my CATALINA.OUT files hsows reference of it wonder why. From: Jerry Ford [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: [EMAIL PROTECTED] Re: MOD_JK2 and MOD_JK on SuSE Date: Wed, 24 Dec 2003 14:07:31 -0800 Hari: To remove mod_jk2, just delete mod_jk2.so from your apache/libexec directory and delete the references to it from your Apache config (httpd.conf). As for tomcat continuing to listen, that's because you have a mod_jk2 connector defined in tomcat's server.xml. Just because tomcat is listening for it does not mean mod_jk2 is working. Somebody else will have to address the questions about value---I don't use mod_jk2, I have mod_jk, but I also don't use apache 2.x, I have apache 1.3. I believe jk2 is designed for apache 2. As for jk2 references in jk configs, yes, jk2 shows up in my catalina.out, too, and I've never installed mod_jk2. It appears to just be some sloppy reference in a log message. It doesn't mean anything significant. I mean, it all still works. :) Jerry Hari Om wrote: I am using Apache 2.0.47 and Tomcat 4.1.27 and JDK 1.4 on SuSE Linux 8.0. I would like to use Connector for integrating Apache Tomcat. I have installed MOD_JK2 and want to get rid of it. How can I uninstall it? WHen I run my Tomcat it still refers to JK2 settings. I wanted to use JK instead. Can anyone please help me
admin app is forbidden
I have Tomcat 4.1.27 running with Apache 1.3.27, using mod_jk, on a Linux box (Red Hat 9.0, but custom-installed Apache and Tomcat in /usr/local). I am able to run Tomcat's example servlets, as well as my own custom servlets (installed as a webapp), and the Manager webapp, but when I try to view the Admin app, I get a 403 - resource has been forbidden message. http://localhost/manager works fine, login screen is displayed, I log in and the app runs, but http://localhost/admin is forbidden to me. I cannot find anything in the configs that would allow one but prohibit the other. The Manager app shows /admin as running, and so do the logs. I just can't get to it. Can anyone tell me why I can't even get to the login screen before the admin app rejects my attempt? Thanks. Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MOD_JK2 and MOD_JK on SuSE
Hari: To remove mod_jk2, just delete mod_jk2.so from your apache/libexec directory and delete the references to it from your Apache config (httpd.conf). As for tomcat continuing to listen, that's because you have a mod_jk2 connector defined in tomcat's server.xml. Just because tomcat is listening for it does not mean mod_jk2 is working. Somebody else will have to address the questions about value---I don't use mod_jk2, I have mod_jk, but I also don't use apache 2.x, I have apache 1.3. I believe jk2 is designed for apache 2. As for jk2 references in jk configs, yes, jk2 shows up in my catalina.out, too, and I've never installed mod_jk2. It appears to just be some sloppy reference in a log message. It doesn't mean anything significant. I mean, it all still works. :) Jerry Hari Om wrote: I am using Apache 2.0.47 and Tomcat 4.1.27 and JDK 1.4 on SuSE Linux 8.0. I would like to use Connector for integrating Apache Tomcat. I have installed MOD_JK2 and want to get rid of it. How can I uninstall it? WHen I run my Tomcat it still refers to JK2 settings. I wanted to use JK instead. Can anyone please help me on this. Few more questions: 1) Is it worth using MOD_JK2 v/s MOD_JK? 2) I already installed MOD_JK2 and it does NOT seems to WORK...so wanted to get rid of it. I wanted to see if MOD_JK works. How is this possible? Deleting the jk2.properties and worker2.properties DOES NOT WORKcatalina.out file still shows TOMCAT is refereing to JK as shown below: --- INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 24, 2003 11:33:56 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Dec 24, 2003 11:33:56 AM org.apache.jk.server.JkMain start --- Can anyone please Help Me. Thanks and Merry XMAS! HARI OM _ Enjoy a special introductory offer for dial-up Internet access limited time only! http://join.msn.com/?page=dept/dialup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk only usable from localhost
Jeremy: I just solved the exact same problem on my setup (Apache 1.3.27 - Tomcat 4.1.27 via mod_jk). In my case, it was because I had enclosed the Tomcat config statements in httpd.conf in a virtual host block. I forget why I had done that, but I had asked a lot of questions on this forum during the initial setup period and those posts led me to the configuration I was using; once I got it working on localhost, I was happy for the time being, until it came time to port the setup from my staging machine to the live web. Anyway, as soon as I removed the virtual host config statement, it worked. See http://www.katzenjammer.us/~jford/apache/tomcat/ for details. Jerry Chakravarthy, Sundar wrote: 1. Make sure machine is visible ping computername 2. Make sure apache is serving pages http://computername 3. Make sure tomcat works in standalone mode http://computername:8080 4. Then edit httpd.conf , tomcat's server.xml ( see docs ) http://computername/context -Original Message- From: Jeremy Whitlock [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 6:45 PM To: Tomcat Subject: mod_jk only usable from localhost Tomcat List, I have installed Apache+Tomcat via mod_jk. I have it configured so that I can use Tomcat from Apache but it only works from the localhost. If I: http://localhost/tomcat-docs it works but if I do: http://computername/tomcat-docs http://computerip/tomcat-docs it doesn't work. Is there something special you have to do to make mod_jk work from computers other than localhost? Thanks, Jeremy Whitlock --- MCP/MCSA IT Manager for Star Precision, Inc. Phone: (970) 535-4795 Metro: (303) 926-0559 Fax: (970) 535-0780 Metro Fax: (303) 926-8557 http://www.starprecision.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: localhost works, www does not; why?
Thanks. Problem has been solved. In httpd.conf, the Tomcat configs were enclosed in a virtual host block. When I removed the VirtualHost ... /VirtualHost tags, the problem went away and it now works correctly. BTW, I also observed the changing URL; that, too, has gone away. Jerry Adam Hardy wrote: On 12/16/2003 05:55 PMnbsp;jford wrote: This may have been asked many times before, but I can't find it, in part because I don't quite know what to search for and in part because it may not even be a Tomcat-specific issue. But it occurs because I'm trying to make Tomcat work, so here goes... (if I'm wrong and the question needs to be redirected, I'm sure someone will politely point it out to me :) I have Apache 1.3.27 and Tomcat 4.1.27 running under Red Hat 9.0 Linux. The two webservers are connected by mod_jk. When I go to http://localhost from the browser on the Linux box, I get Apache's index page. http://localhost:8080 gets me Tomcat's index page. And http://localhost/examples gets me the Tomcat examples directory listing with an Apache port 80 slug at the bottom. When I drill down to the examples themselves, they work. So I know the Apache-mod_jK-Tomcat connection is correctly configured. But when I try it from the live web, using my domain name, I cannot get to the Tomcat pages. http://www.katzenjammer.us gets me my website. http://www.katzenjammer.us:8080 gets me Tomcat's index page, and, again, I am able to drill down into the examples themselves and they work. But http://www.katzenjammer.us/examples and http://www.katzenjammer.us/examples/jsp/index.jsp get me 404 page not found errors. My webserver sits behind a Netgear firewall router, which has been configured to allow ports 80, 8080, and 8009 to get through to the webserver. Can somebody tell me what Im doing wrong? There is another thread on this subject called url changing to localhost where the poster mentioned something about Apache's ProxyPass setting. No idea what it is myself, but it might help :) Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT]JSP defense - can you point me in the right direction
Found this by searching Google : http://www.apl.jhu.edu/~hall/java/Servlet-Tutorial/Servlet-Tutorial-Overview.html Denise Mangano wrote: Hi all :) I'm not sure if this is technically off topic, but just in case I threw in the [OT]... I have a dilemma at hand. I have a team that wishes to include me in on a project that they are working on. This project consists of hosting a secure site that contains a gazillion forms for people to fill out, then write the responses back to a mySQL database, as well as build an admin section for querying the database. Seeing as how I am going to be doing the web dev part, while the others deal with the complex database structure and project management tasks, I am trying to sell them on using JSP/Tomcat. They are insisting on using CGI scripts, which I personally feel is too fundamental for the task at hand. Can anyone point me in the right direction to getting stats to back up my claim that JSP is the better choice? Or if anyone can tell me why CGI would be the better choice then I'm all ears... Thanks in advance!!! Denise - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache 2+Tomcat 4.1.12: how to disable the Coyote HTTP connector?
Looks like you conmmented out the wrong connector. The one you have removed is identified as the one for port 8009, which is the one Apache uses. Restore that connector and comment out the one that is identified as for port 8080. Jerry Manuel González Castro wrote: Hi, I'm running Apache HTTP Server 2.0.43 + Tomcat 4.1.12 + mod_jk and everything is working fine, Apache can talk to Tomcat to serve *.jsp pages. Now I'd like to disable the default non-SSL Coyote HTTP/1.1 Connector on port 8080 because I don't like everybody getting into http://mydomain.com:8080 and seeing the Tomcat congratulations page, manager, admin page, ... I just want Tomcat to serve JSP pages to Apache using mod_jk. I commented the default Coyote HTTP/1.1 Connector and leaved the AJP 1.3 as the only Connector in my server.xml file: !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ But when I request a JSP file to Apache, Tomcat doesn't answer, I get this error: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Is there any way to prevent people from accesing http://mydomain:8080 and leave AJP 1.3 as the only Connector ? Thanks in advance! Manuel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat Ant custom taks
I believe there is an O'Reilly book on using Ant. Gee Jee wrote: Hi, I've been sort of using the Tomcat library for Ant custom tasks. I got some of it to work by using the information on the Tomcat website. However, I did not find a consise overview of this library. Is this available somewhere? It seems very useful as a part of my build scripts. Gerard Janssen -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
How I got mod_jk running (Was: Re: Yes!!! It works!!!)
Well, I could not make auto-conf work, and the system does work without it. If anybody is interested in my experience, go here: http://www.katzenjammer.us/~jford/apache/tomcat/connectors/mod_jk_setup.shtml And, again, thanks to everybody for helping me out. Jerry Turner, John wrote: My guess is the virtual hosting configuration was messed up somehow. Couldn't say more without trying the problem config files on one of my systems, but I don't have the time right now to do it. The auto-generation works like a charm, I can attest to that as can others. AFAIK, the only way using auto-gen would cause JK NOT to work is if the auto-gen was generating Apache VirtualHost containers and JkMount statements that didn't apply, weren't used, or were overridden somehow with other configuration directives in httpd.conf. John -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Friday, December 27, 2002 10:09 AM To: 'Tomcat Users List' Subject: RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting c loser) Justin - Any thoughts on why that did the trick? As I mentioned, those directives are not commented out on my config, but it works?? Just curious is all... Thanks! Denise -Original Message- From: Justin L. Spies [mailto:[EMAIL PROTECTED]] Sent: Friday, December 27, 2002 10:01 AM To: 'Tomcat Users List' Subject: RE: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer) This was a message I thought I had sent to the list, but I somehow managed to send it to Jerry directly... Congratulations Jerry! Glad to hear that you've got a working system now! Just for the benefit of the other list members out there, the pieces we commented out were the following: !-- This listener was immediately after the Server port=... directive. -- !-- Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=/usr/local/webserver/apache/libexec/mod_jk.so jkDebug=debug workersConfig=/usr/local/webserver/tomcat/conf/jk/workers.properties jkLog=/usr/local/webserver/tomcat/logs/mod_jk.log/ -- --- AND --- !-- This listener was immediately after the Host name=... directive inside of the Server port=... directive. -- !-- Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true forwardAll=false/ -- Has anyone else out there had good experience setting up the Apache auto configuration? Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 26, 2002 5:31 PM To: Justin L. Spies Cc: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer) Justin, I owe you a beer... I removed the two listener statements that you commented out in my server.xml file and now servlets work from Apache without a port setting. Thank you thank you thank you. (And thanks to everyone else who put up with my whining over the past few days and offered help---especially Denise, John, and Jeff :) (BTW, it's academic now, but, yes, on my box tomcat is a symbolic link to jakarta-tomcat-4.1.12-LE-jdk14.) Jerry Justin L. Spies wrote: Jerry, I've updated and simplified the configuration files that you supplied previously. Any changes I made are denoted by the following: NOTE NOTE NOTE NOTE These changes cause your system to have the same config that I first used to get my system working. I'm not sure about your directory structure and whether or not you have symlinks setup, however I did notice that in some of the configuration files you were using two different directories that should point to the same directories. Here is an example from httpd.conf: You had the following for the JkWorkersFile: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pr o perties But just below that you had the following apache directive: Directory /usr/local/webserver/tomcat/webapps/examples These should be the same directory above the /conf directory and above the /webapps directory. On my system, I have tomcat installed in /var/tomcat4, so I have the following directives: JkWorkersFile /var/tomcat4/conf/jk/workers.properties -- and -- Directory /var/tomcat4/webapps/examples See how they are the same first two? /conf and /webapps should be a subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless you have a symlink (in your case) from /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to /usr/local/webserver/tomcat. Does that make sense, or did I just completely confuse everyone? Jerry, when you restart Apache and Tomcat, could you send us copies of the apache error log and the tomcat catalina.out files? Also, if you could confirm the directory structure, that would be a big
Re: mod_jk---still trying, getting closer
Yes. Same results. PELOQUIN,JEFFREY (HP-Boise,ex1) wrote: Your http.conf shows that apache is running as nobody have you tried changing that so it runs as the owner of the apache and tomcat directory structure? -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 26, 2002 12:32 AM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer John: Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way. As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache: http://localhost opens Apache's index page http://localhost:8080 opens Tomcat's index page, and servlets work http://localhost/examples/servlets opens the servlets index page, but servlets don't work Catalina.out in Tomcat's logs directory says mod_jk is running: Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properti es Stopping service Tomcat-Standalone Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 11:26:18 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 11:26:18 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 11:26:19 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/277 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properti es But the Apache error log says Apache cannot open the workers file, even though the path specified is correct and permissions to the file are -rw-rw-r-- and to all directories drwxrwxr-x: [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Wed Dec 25 15:14:36 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) Jerry Turner, John wrote: Whoa, I have NEVER seen a worker called ajp.13 before. I can't imagine that that would work at all, as . is a separator in workers.properties. Is there a reason you are using that instead of ajp13 or something else? Also, what exact URL are you trying to access? What URL is not working? From your httpd.conf, the only possible URL that would work, aside from the examples, the manager app, and the admin app, is: http://localhost/j_tools/servlet/HelloWorld and http://localhost/j_tools/some.jsp Are those what you are trying? John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 25, 2002 6:22 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Denise: Other than path names, the major differences between your set up and mine is that you use SSL, and I don't, and you have a lot more modules loaded than I do (in addition to mod_jk). But I don't see those differences as having anything to do with why yours works and mine doesn't. For one thing, this installation of Apache is on my development workstation, and I just installed it to test the tomcat connection. So, it doesn't need to be a fully functional web server. At least, not yet. Also, I removed the comments from my conf file so I can find things :) I have tried it both ways---with an include statement pointing to mod_jk.conf in tomcat/conf/auto, and with statements inside httpd.conf. Same results. I have also experimented with a variety of permissions on both files and directories. My configuration files are attached. Thanks. Jerry Denise Mangano wrote: Jerry - My config is now working with the files that I had posted. Did you notice any major differences between those and yours? I had also gotten this same Apache error message at one point as well. But it just sort of went away when I put the JkMount statements right into httpd.conf and made a different workers.properties file than the one that was posted on the HOW-TO. Here are the contents of my
Re: mod_jk---still trying, getting closer
I use the mod_jk binary obtained from John Turner's how-to page, and the httpd.conf and server.xml statements are the same as the statements in the configurations several other people here have provided as examples, I think. I have also tried to follow John Turner's suggested confuguration statements. I've tried just about every combination of configurations that have been suggested. It's possible that by now I have mixed up different people's advice, but I don't know what needs to be changed. I don't know why JK2 is in there, other than the coyote packages that are referenced in sever.xml. But if I don't use those, what do I use? I'm beginning to think mod_webapp.so is looking like my only hope of getting Tomcat and Apache to work together. Jerry Jerry Milt Epstein wrote: On Wed, 25 Dec 2002, Jerry Ford wrote: John: Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way. One things I don't understand, it seems like you have JK2 running on the Tomcat side, but you refer to workers.properties, which is a JK file, JK2 doesn't use it, I don't believe. Could that be related to the problem? As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache: http://localhost opens Apache's index page http://localhost:8080 opens Tomcat's index page, and servlets work http://localhost/examples/servlets opens the servlets index page, but servlets don't work Catalina.out in Tomcat's logs directory says mod_jk is running: Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properties Stopping service Tomcat-Standalone Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 11:26:18 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 11:26:18 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 11:26:19 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/277 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properties But the Apache error log says Apache cannot open the workers file, even though the path specified is correct and permissions to the file are -rw-rw-r-- and to all directories drwxrwxr-x: [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Wed Dec 25 15:14:36 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) [ ... ] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: mod_jk---still trying, getting closer
Have tried it both ways; added quotes because it wasn't working without them and I wanted to see what would happen. Same results. Jerry PELOQUIN,JEFFREY (HP-Boise,ex1) wrote: Just for chuckles try it without putting quote around the file names this is how I have it my http.conf JkWorkersFile /opt_apps/hpapache2/conf/workers.properties JkLogFile /opt_apps/hpapache2/logs/mod_jk.log JkLogLevel info if that does not work try moving the files local to the apache conf and log directories Jeff -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 26, 2002 11:54 AM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Yes. Same results. PELOQUIN,JEFFREY (HP-Boise,ex1) wrote: Your http.conf shows that apache is running as nobody have you tried changing that so it runs as the owner of the apache and tomcat directory structure? -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 26, 2002 12:32 AM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer John: Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way. As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache: http://localhost opens Apache's index page http://localhost:8080 opens Tomcat's index page, and servlets work http://localhost/examples/servlets opens the servlets index page, but servlets don't work Catalina.out in Tomcat's logs directory says mod_jk is running: Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.propert i es Stopping service Tomcat-Standalone Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 11:26:18 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 11:26:18 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 11:26:19 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/277 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.propert i es But the Apache error log says Apache cannot open the workers file, even though the path specified is correct and permissions to the file are -rw-rw-r-- and to all directories drwxrwxr-x: [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Wed Dec 25 15:14:36 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) Jerry Turner, John wrote: Whoa, I have NEVER seen a worker called ajp.13 before. I can't imagine that that would work at all, as . is a separator in workers.properties. Is there a reason you are using that instead of ajp13 or something else? Also, what exact URL are you trying to access? What URL is not working? From your httpd.conf, the only possible URL that would work, aside from the examples, the manager app, and the admin app, is: http://localhost/j_tools/servlet/HelloWorld and http://localhost/j_tools/some.jsp Are those what you are trying? John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 25, 2002 6:22 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Denise: Other than path names, the major differences between your set up and mine is that you use SSL, and I don't, and you have a lot more modules loaded than I do (in addition to mod_jk). But I don't see those differences as having anything to do with why yours works and mine doesn't. For one thing, this installation of Apache is on my development workstation, and I just installed it to test the tomcat connection. So, it doesn't need to be a fully functional web server. At least, not yet. Also, I removed the comments from my conf file so I can find things :) I have tried it both ways
Re: mod_jk---still trying, getting closer
mod_jk.so Justin L. Spies wrote: Jerry, Just to clarify, are you using the mod_jk.so or mod_jk2.so? Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 26, 2002 2:00 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer I use the mod_jk binary obtained from John Turner's how-to page, and the httpd.conf and server.xml statements are the same as the statements in the configurations several other people here have provided as examples, I think. I have also tried to follow John Turner's suggested confuguration statements. I've tried just about every combination of configurations that have been suggested. It's possible that by now I have mixed up different people's advice, but I don't know what needs to be changed. I don't know why JK2 is in there, other than the coyote packages that are referenced in sever.xml. But if I don't use those, what do I use? I'm beginning to think mod_webapp.so is looking like my only hope of getting Tomcat and Apache to work together. Jerry Jerry Milt Epstein wrote: On Wed, 25 Dec 2002, Jerry Ford wrote: John: Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way. One things I don't understand, it seems like you have JK2 running on the Tomcat side, but you refer to workers.properties, which is a JK file, JK2 doesn't use it, I don't believe. Could that be related to the problem? As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache: http://localhost opens Apache's index page http://localhost:8080 opens Tomcat's index page, and servlets work http://localhost/examples/servlets opens the servlets index page, but servlets don't work Catalina.out in Tomcat's logs directory says mod_jk is running: Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.pr operties Stopping service Tomcat-Standalone Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 11:26:18 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 11:26:18 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 11:26:19 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/277 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.pr operties But the Apache error log says Apache cannot open the workers file, even though the path specified is correct and permissions to the file are -rw-rw-r-- and to all directories drwxrwxr-x: [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Wed Dec 25 15:14:36 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) [ ... ] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Yes!!! It works!!! (was: Re: mod_jk---still trying, getting closer)
Justin, I owe you a beer... I removed the two listener statements that you commented out in my server.xml file and now servlets work from Apache without a port setting. Thank you thank you thank you. (And thanks to everyone else who put up with my whining over the past few days and offered help---especially Denise, John, and Jeff :) (BTW, it's academic now, but, yes, on my box tomcat is a symbolic link to jakarta-tomcat-4.1.12-LE-jdk14.) Jerry Justin L. Spies wrote: Jerry, I've updated and simplified the configuration files that you supplied previously. Any changes I made are denoted by the following: NOTE NOTE NOTE NOTE These changes cause your system to have the same config that I first used to get my system working. I'm not sure about your directory structure and whether or not you have symlinks setup, however I did notice that in some of the configuration files you were using two different directories that should point to the same directories. Here is an example from httpd.conf: You had the following for the JkWorkersFile: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties But just below that you had the following apache directive: Directory /usr/local/webserver/tomcat/webapps/examples These should be the same directory above the /conf directory and above the /webapps directory. On my system, I have tomcat installed in /var/tomcat4, so I have the following directives: JkWorkersFile /var/tomcat4/conf/jk/workers.properties -- and -- Directory /var/tomcat4/webapps/examples See how they are the same first two? /conf and /webapps should be a subdirectory of /tomcat4 (in my case) or /tomcat (in your case), unless you have a symlink (in your case) from /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14 to /usr/local/webserver/tomcat. Does that make sense, or did I just completely confuse everyone? Jerry, when you restart Apache and Tomcat, could you send us copies of the apache error log and the tomcat catalina.out files? Also, if you could confirm the directory structure, that would be a big help. Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 26, 2002 2:00 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer I use the mod_jk binary obtained from John Turner's how-to page, and the httpd.conf and server.xml statements are the same as the statements in the configurations several other people here have provided as examples, I think. I have also tried to follow John Turner's suggested confuguration statements. I've tried just about every combination of configurations that have been suggested. It's possible that by now I have mixed up different people's advice, but I don't know what needs to be changed. I don't know why JK2 is in there, other than the coyote packages that are referenced in sever.xml. But if I don't use those, what do I use? I'm beginning to think mod_webapp.so is looking like my only hope of getting Tomcat and Apache to work together. Jerry Jerry Milt Epstein wrote: On Wed, 25 Dec 2002, Jerry Ford wrote: John: Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way. One things I don't understand, it seems like you have JK2 running on the Tomcat side, but you refer to workers.properties, which is a JK file, JK2 doesn't use it, I don't believe. Could that be related to the problem? As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache: http://localhost opens Apache's index page http://localhost:8080 opens Tomcat's index page, and servlets work http://localhost/examples/servlets opens the servlets index page, but servlets don't work Catalina.out in Tomcat's logs directory says mod_jk is running: Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.pr operties Stopping service Tomcat-Standalone Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE
Re: mod_jk---still trying, getting closer
Denise: Other than path names, the major differences between your set up and mine is that you use SSL, and I don't, and you have a lot more modules loaded than I do (in addition to mod_jk). But I don't see those differences as having anything to do with why yours works and mine doesn't. For one thing, this installation of Apache is on my development workstation, and I just installed it to test the tomcat connection. So, it doesn't need to be a fully functional web server. At least, not yet. Also, I removed the comments from my conf file so I can find things :) I have tried it both ways---with an include statement pointing to mod_jk.conf in tomcat/conf/auto, and with statements inside httpd.conf. Same results. I have also experimented with a variety of permissions on both files and directories. My configuration files are attached. Thanks. Jerry Denise Mangano wrote: Jerry - My config is now working with the files that I had posted. Did you notice any major differences between those and yours? I had also gotten this same Apache error message at one point as well. But it just sort of went away when I put the JkMount statements right into httpd.conf and made a different workers.properties file than the one that was posted on the HOW-TO. Here are the contents of my workers.properties file. With this properties file I use worker1 instead of ajp13 in the JkMount statements: (For example JkMount /examples/* worker1) worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 On a side note, my workers.properties has 644 permissions (-rw-r--r--). Would you post your files and error logs? I am sure someone in here would take a look... I can also look just to see any major differences against mine.. Denise -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 4:31 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Yes, good idea about the symbolic links. I have done now so---sym links for both apache and tomcat. I have also moved all mod_jk configs into httpd.conf. And I'm still getting the same results---catalina.out says Jk is okay, apache works, tomcat works (with servlets) but the apache error_log says error while opening the workers, jk will not work. And sure enough, no servlets through Apache. Jerry Milt Epstein wrote: On Tue, 24 Dec 2002, Jerry Ford wrote: Ooops, sorry, I was using shorthand in showing the directory gtree; actual name of the directory is the full jakarta-tomcat-4.1.12-LE-jdk14; same for apache, it's acutally apache_1.3.27 (whew, guess I need to change those anyway, that's a lot of typing!!! :) I just untarred them and kept the default names. FWIW, you still might want to create a symbolic link tomcat (under webserver) that points to jakarta-tomcat-4.1.12-LE-jdk14. This might not fix your problem here, but it could save you some hassle if/when you upgrade to new versions. PELOQUIN,JEFFREY (HP-Boise,ex1) wrote: Jerry, The confusion as to the name arises from your printour of your directory structure drwxrwxr-x...usr/ drwxrwxr-x..local/ drwxrwxr-x.webserver/ drwxrwxr-xapache/ drwxrwxr-xtomcat/ drwxrwxr-x...conf/ drwxrwxr-x..jk/ -rw-rw-r-x.workers.properties there is no jakarta-tomcat-4.12.12-LE-jdk14 mentioned which implies there is a mismatch of names -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 12:49 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Justin: My bad. I didn't copy and paste, I retyped the JkLogFile reference. In the config, it correctly says mod_jk.log. I don't understand what would be accomplished by changing jakarta-tomcat-4.12.12-LE-jdk14 to simply tomcat. The name of the directory is the full name, as it was created when I untarred Tomcat. If I change the reference in the configs to tomcat and change the name of the directory to tomcat how is that any different? As for auto-conf, you are right. I think I will do as you suggest and move everything into httpd. Jerry Justin L. Spies wrote: Jerry, I've never used the auto/mod_jk stuff, so I can't comment on that. What is weird to me though, is the line that reads: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties That leads me to believe that mod_jk is configured to overwrite the workers.properties file with the mod_jk log. I would have expected to see the lines: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties JKLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/mod_jk.log Changing those as suggested by Jeffrey (I agree with him on these changes
Re: mod_jk---still trying, getting closer
John: Sorry, I had changed ajp13 to worker1 in trying to emulate Denise's working setup, but that didn't do any good so I changed it back and inadvertently put the dot in. But it doesn't matter, it doesn't work either way. As noted in earlier e-mails, I can get the Tomcat example servlets to work, as well as my own j_tools HelloWorld, when I specify port 8080, but not through Apache: http://localhost opens Apache's index page http://localhost:8080 opens Tomcat's index page, and servlets work http://localhost/examples/servlets opens the servlets index page, but servlets don't work Catalina.out in Tomcat's logs directory says mod_jk is running: Dec 25, 2002 8:50:51 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 8:50:57 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 8:50:57 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 8:50:57 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/121 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properties Stopping service Tomcat-Standalone Dec 25, 2002 11:26:13 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 25, 2002 11:26:18 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 25, 2002 11:26:18 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 25, 2002 11:26:19 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/277 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properties But the Apache error log says Apache cannot open the workers file, even though the path specified is correct and permissions to the file are -rw-rw-r-- and to all directories drwxrwxr-x: [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Wed Dec 25 15:14:36 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Wed Dec 25 15:14:36 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) Jerry Turner, John wrote: Whoa, I have NEVER seen a worker called ajp.13 before. I can't imagine that that would work at all, as . is a separator in workers.properties. Is there a reason you are using that instead of ajp13 or something else? Also, what exact URL are you trying to access? What URL is not working? From your httpd.conf, the only possible URL that would work, aside from the examples, the manager app, and the admin app, is: http://localhost/j_tools/servlet/HelloWorld and http://localhost/j_tools/some.jsp Are those what you are trying? John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 25, 2002 6:22 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Denise: Other than path names, the major differences between your set up and mine is that you use SSL, and I don't, and you have a lot more modules loaded than I do (in addition to mod_jk). But I don't see those differences as having anything to do with why yours works and mine doesn't. For one thing, this installation of Apache is on my development workstation, and I just installed it to test the tomcat connection. So, it doesn't need to be a fully functional web server. At least, not yet. Also, I removed the comments from my conf file so I can find things :) I have tried it both ways---with an include statement pointing to mod_jk.conf in tomcat/conf/auto, and with statements inside httpd.conf. Same results. I have also experimented with a variety of permissions on both files and directories. My configuration files are attached. Thanks. Jerry Denise Mangano wrote: Jerry - My config is now working with the files that I had posted. Did you notice any major differences between those and yours? I had also gotten this same Apache error message at one point as well. But it just sort of went away when I put the JkMount statements right into httpd.conf and made a different workers.properties file than the one that was posted on the HOW-TO. Here are the contents of my workers.properties file. With this properties file I use worker1 instead of ajp13 in the JkMount statements: (For example JkMount /examples/* worker1) worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 On a side note, my workers.properties has 644 permissions (-rw-r--r--). Would you post your files and error logs? I am sure someone in here would take a look... I can also look just to see
mod_jk---still trying, getting closer
Thanks to some examples of working configs provided by several people here, I am making progress in getting Apache 1.3.27 and Tomcat 4.1.12 to work together through mod_jk, but it still isn't working yet. Tomcat and Apache run fine independently: http://localhost opens Apache's index.html http://localhost:8080 opens Tomcat's index and servlet examples work fine. http://localhost/examples/servlets opens the servlets index, but servlets themselves don't work (generate an Apache port 80 Internal Server error) I see in the catalina.out logfile that Tomcat is now able to start Jk (this is new for me---one key element was specifying an absolute path to mod_jk.so): Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 24, 2002 9:13:48 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 24, 2002 9:13:48 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 24, 2002 9:13:48 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/179 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.properties But the Apache error_log says Apache can't open the workers.properties file: [Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Tue Dec 24 09:13:59 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Tue Dec 24 09:13:59 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) Worker file is identified as follows, in the auto/mod_jk.conf file: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.properties I know some have recommended that the contents of mod_jk.conf be hardwired into httpd.conf, but auto/mod_jk.conf seems to be working fine in every other respect, so I am inclined to continue using it. Still, I did put the log file directive in httpd.conf just to see of it would make a difference. It did not. The directory tree is set up as follows: drwxrwxr-x...usr/ drwxrwxr-x..local/ drwxrwxr-x.webserver/ drwxrwxr-xapache/ drwxrwxr-xtomcat/ drwxrwxr-x...conf/ drwxrwxr-x..jk/ -rw-rw-r-x.workers.properties Ownership of the apache tree was changed from root:root to jford:jford; so I changed it back to root:root and tried it, and I still get the errors (so I changed it back to jford:jford). Any suggestions? Thanks. Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: mod_jk---still trying, getting closer
Justin: My bad. I didn't copy and paste, I retyped the JkLogFile reference. In the config, it correctly says mod_jk.log. I don't understand what would be accomplished by changing jakarta-tomcat-4.12.12-LE-jdk14 to simply tomcat. The name of the directory is the full name, as it was created when I untarred Tomcat. If I change the reference in the configs to tomcat and change the name of the directory to tomcat how is that any different? As for auto-conf, you are right. I think I will do as you suggest and move everything into httpd. Jerry Justin L. Spies wrote: Jerry, I've never used the auto/mod_jk stuff, so I can't comment on that. What is weird to me though, is the line that reads: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties That leads me to believe that mod_jk is configured to overwrite the workers.properties file with the mod_jk log. I would have expected to see the lines: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties JKLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/mod_jk.log Changing those as suggested by Jeffrey (I agree with him on these changes), they would like this: JkWorkersFile /usr/local/webserver/apache/tomcat/conf/jk/workers.properties JKLogFile /usr/local/webserver/apache/tomcat/conf/jk/mod_jk.log If I were in your shoes, I think that I would try to get mod_jk working without the auto configuration. Once I had that working, I would then focus on the autoconfig. I don't know about you, but in my experience, when I try to get everything working in the first run, I usually miss something and have to take a step back and start with the basics. That's just me though. Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 12:42 PM To: tomcat-user Subject: mod_jk---still trying, getting closer Thanks to some examples of working configs provided by several people here, I am making progress in getting Apache 1.3.27 and Tomcat 4.1.12 to work together through mod_jk, but it still isn't working yet. Tomcat and Apache run fine independently: http://localhost opens Apache's index.html http://localhost:8080 opens Tomcat's index and servlet examples work fine. http://localhost/examples/servlets opens the servlets index, but servlets themselves don't work (generate an Apache port 80 Internal Server error) I see in the catalina.out logfile that Tomcat is now able to start Jk (this is new for me---one key element was specifying an absolute path to mod_jk.so): Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 24, 2002 9:13:48 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 24, 2002 9:13:48 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 24, 2002 9:13:48 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/179 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.prop erties But the Apache error_log says Apache can't open the workers.properties file: [Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Tue Dec 24 09:13:59 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Tue Dec 24 09:13:59 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) Worker file is identified as follows, in the auto/mod_jk.conf file: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties I know some have recommended that the contents of mod_jk.conf be hardwired into httpd.conf, but auto/mod_jk.conf seems to be working fine in every other respect, so I am inclined to continue using it. Still, I did put the log file directive in httpd.conf just to see of it would make a difference. It did not. The directory tree is set up as follows: drwxrwxr-x...usr/ drwxrwxr-x..local/ drwxrwxr-x.webserver/ drwxrwxr-xapache/ drwxrwxr-xtomcat/ drwxrwxr-x...conf/ drwxrwxr-x..jk/ -rw-rw-r-x.workers.properties Ownership of the apache tree was changed from root:root to jford:jford; so I changed it back to root:root and tried it, and I still get the errors (so I changed it back to jford:jford). Any suggestions? Thanks. Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e
Re: mod_jk---still trying, getting closer
Ooops, sorry, I was using shorthand in showing the directory gtree; actual name of the directory is the full jakarta-tomcat-4.1.12-LE-jdk14; same for apache, it's acutally apache_1.3.27 (whew, guess I need to change those anyway, that's a lot of typing!!! :) I just untarred them and kept the default names. Jerry PELOQUIN,JEFFREY (HP-Boise,ex1) wrote: Jerry, The confusion as to the name arises from your printour of your directory structure drwxrwxr-x...usr/ drwxrwxr-x..local/ drwxrwxr-x.webserver/ drwxrwxr-xapache/ drwxrwxr-xtomcat/ drwxrwxr-x...conf/ drwxrwxr-x..jk/ -rw-rw-r-x.workers.properties there is no jakarta-tomcat-4.12.12-LE-jdk14 mentioned which implies there is a mismatch of names -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 12:49 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Justin: My bad. I didn't copy and paste, I retyped the JkLogFile reference. In the config, it correctly says mod_jk.log. I don't understand what would be accomplished by changing jakarta-tomcat-4.12.12-LE-jdk14 to simply tomcat. The name of the directory is the full name, as it was created when I untarred Tomcat. If I change the reference in the configs to tomcat and change the name of the directory to tomcat how is that any different? As for auto-conf, you are right. I think I will do as you suggest and move everything into httpd. Jerry Justin L. Spies wrote: Jerry, I've never used the auto/mod_jk stuff, so I can't comment on that. What is weird to me though, is the line that reads: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties That leads me to believe that mod_jk is configured to overwrite the workers.properties file with the mod_jk log. I would have expected to see the lines: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties JKLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/mod_jk.log Changing those as suggested by Jeffrey (I agree with him on these changes), they would like this: JkWorkersFile /usr/local/webserver/apache/tomcat/conf/jk/workers.properties JKLogFile /usr/local/webserver/apache/tomcat/conf/jk/mod_jk.log If I were in your shoes, I think that I would try to get mod_jk working without the auto configuration. Once I had that working, I would then focus on the autoconfig. I don't know about you, but in my experience, when I try to get everything working in the first run, I usually miss something and have to take a step back and start with the basics. That's just me though. Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 12:42 PM To: tomcat-user Subject: mod_jk---still trying, getting closer Thanks to some examples of working configs provided by several people here, I am making progress in getting Apache 1.3.27 and Tomcat 4.1.12 to work together through mod_jk, but it still isn't working yet. Tomcat and Apache run fine independently: http://localhost opens Apache's index.html http://localhost:8080 opens Tomcat's index and servlet examples work fine. http://localhost/examples/servlets opens the servlets index, but servlets themselves don't work (generate an Apache port 80 Internal Server error) I see in the catalina.out logfile that Tomcat is now able to start Jk (this is new for me---one key element was specifying an absolute path to mod_jk.so): Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 24, 2002 9:13:48 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 24, 2002 9:13:48 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 24, 2002 9:13:48 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/179 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.prop erties But the Apache error_log says Apache can't open the workers.properties file: [Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Tue Dec 24 09:13:59 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Tue Dec 24 09:13:59 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Tue Dec 24 09:13:59 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) Worker file is identified as follows, in the auto/mod_jk.conf file: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties I know some have recommended that the contents of mod_jk.conf be hardwired into httpd.conf, but auto/mod_jk.conf seems to be working fine
Re: mod_jk---still trying, getting closer
Yes, good idea about the symbolic links. I have done now so---sym links for both apache and tomcat. I have also moved all mod_jk configs into httpd.conf. And I'm still getting the same results---catalina.out says Jk is okay, apache works, tomcat works (with servlets) but the apache error_log says error while opening the workers, jk will not work. And sure enough, no servlets through Apache. Jerry Milt Epstein wrote: On Tue, 24 Dec 2002, Jerry Ford wrote: Ooops, sorry, I was using shorthand in showing the directory gtree; actual name of the directory is the full jakarta-tomcat-4.1.12-LE-jdk14; same for apache, it's acutally apache_1.3.27 (whew, guess I need to change those anyway, that's a lot of typing!!! :) I just untarred them and kept the default names. FWIW, you still might want to create a symbolic link tomcat (under webserver) that points to jakarta-tomcat-4.1.12-LE-jdk14. This might not fix your problem here, but it could save you some hassle if/when you upgrade to new versions. PELOQUIN,JEFFREY (HP-Boise,ex1) wrote: Jerry, The confusion as to the name arises from your printour of your directory structure drwxrwxr-x...usr/ drwxrwxr-x..local/ drwxrwxr-x.webserver/ drwxrwxr-xapache/ drwxrwxr-xtomcat/ drwxrwxr-x...conf/ drwxrwxr-x..jk/ -rw-rw-r-x.workers.properties there is no jakarta-tomcat-4.12.12-LE-jdk14 mentioned which implies there is a mismatch of names -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 12:49 PM To: Tomcat Users List Subject: Re: mod_jk---still trying, getting closer Justin: My bad. I didn't copy and paste, I retyped the JkLogFile reference. In the config, it correctly says mod_jk.log. I don't understand what would be accomplished by changing jakarta-tomcat-4.12.12-LE-jdk14 to simply tomcat. The name of the directory is the full name, as it was created when I untarred Tomcat. If I change the reference in the configs to tomcat and change the name of the directory to tomcat how is that any different? As for auto-conf, you are right. I think I will do as you suggest and move everything into httpd. Jerry Justin L. Spies wrote: Jerry, I've never used the auto/mod_jk stuff, so I can't comment on that. What is weird to me though, is the line that reads: JkLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties That leads me to believe that mod_jk is configured to overwrite the workers.properties file with the mod_jk log. I would have expected to see the lines: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.pro perties JKLogFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/mod_jk.log Changing those as suggested by Jeffrey (I agree with him on these changes), they would like this: JkWorkersFile /usr/local/webserver/apache/tomcat/conf/jk/workers.properties JKLogFile /usr/local/webserver/apache/tomcat/conf/jk/mod_jk.log If I were in your shoes, I think that I would try to get mod_jk working without the auto configuration. Once I had that working, I would then focus on the autoconfig. I don't know about you, but in my experience, when I try to get everything working in the first run, I usually miss something and have to take a step back and start with the basics. That's just me though. Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 24, 2002 12:42 PM To: tomcat-user Subject: mod_jk---still trying, getting closer Thanks to some examples of working configs provided by several people here, I am making progress in getting Apache 1.3.27 and Tomcat 4.1.12 to work together through mod_jk, but it still isn't working yet. Tomcat and Apache run fine independently: http://localhost opens Apache's index.html http://localhost:8080 opens Tomcat's index and servlet examples work fine. http://localhost/examples/servlets opens the servlets index, but servlets themselves don't work (generate an Apache port 80 Internal Server error) I see in the catalina.out logfile that Tomcat is now able to start Jk (this is new for me---one key element was specifying an absolute path to mod_jk.so): Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 24, 2002 9:13:48 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Dec 24, 2002 9:13:48 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on tcp port 8009 Dec 24, 2002 9:13:48 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/179 config=/usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk2.prop erties But the Apache error_log says Apache can't open the workers.properties file: [Tue Dec 24
Re: mod_jk...again
Justin: My only objective is to get a working copy of mod_jk. I downloaded a binary from John Turner's how-to page (I cannot find binary connectors on the jakarta website---what URL do you have for them?) but I have so far been unable to make it work. I now think it's my configuration, not the binary, so being able to compile isn't ciritcal. Error messages I'm seeing in the Apache log suggest that mod_jk is getting loaded. More important to me is getting it to work, and so far I'm have no success. Jerry Justin L. Spies wrote: Jerry, I've never tried building mod_jk from source as the files always existed on the Jakarta website. Although I don't see it here, are you looking to perform a customized compile? If not, is there another reason to compile from source instead of using the binaries? I've never had any problems getting mod_jk to work--just DBCP and that was because of a stupid typo on my part. Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 8:57 PM To: Tomcat Users List Subject: mod_jk...again When I try to build mod_jk from the source contained in jakarta-tomcat-connectors-4.1.12-src.tar, the process breaks before it gets started. I am following the instructions on John Turner's how-to page, but when I run the configure script, it breaks at ltconfig---I get an error message that says a host type must be specified when the --no-verify flag is used. But running ltconfig --help shows no parameter for specifying host type, and the command is run from the configure script anyway. Can anyone tell me what's going on, and more importantly how do I correct it? Here's the output when I run configure; the path to apxs is correct, and JAVA_HOME points to a valid Java 1.4 JDK: [jford@gizmo native]$ ./configure --with-apxs=../../../apache_1.3.27/bin/apxs --with-java-home=$JAVA_HOME checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets $(MAKE)... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for ranlib... ranlib checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed [jford@gizmo native]$ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: RES: Mod_jk - won't execute jsp or servlets
Denise: Yes, please :) I am still in the sinking boat.---Apache works fine by itself, Tomcat works fine by itself (example servlets all work, as well as my own HelloWorld), but Apache-Tomcat through mod_jk does not work. At the moment, I can't even display the HTML pages in the examples. That seems to come and go depending on what is in the config files, not sure what caused it to break this time. I have printed Drew's example files and will compare them to my own, and I will look at the timeout value---I see in my server.xml there is *no* timeout specified at all. And, yes, I would like very much to see your final config files now that you have a working setup. Thanks. Jerry Denise Mangano wrote: I don't know what else to say But YAY! :-P Milt - it looks like the timeout was what was doing it. Weird thing is - I didn't edit that. Unless I did something by mistake that is the way that it was shipped!! Everything is working great!! I can access all static pages as well as execute all servlets and JSP. I better knock on wood and pray nothing goes wrong to make it stop working ;) Thank you SO MUCH to everyone for all of your help!! I definitely would have been pulling my hair out from the roots if it weren't for this list!! Jerry - where do you stand with your set up? Since we have the same set up would you like me to send you my files now that it is working for me?? Denise Mangano -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 11:55 AM To: Tomcat Users List Subject: RE: Mod_jk - won't execute jsp or servlets On Mon, 23 Dec 2002, Denise Mangano wrote: Tomcat is up and running - I can view and execute examples by using :8080. OK, that means Tomcat standalone is working (as controlled by the Coyote Http Connector onport 8080) If the port that Tomcat is listening on is set by workers.properties, then that would be port 8009. Where Apache is expecting it to listen on I am not sure. Actually, you've got it backwards. workers.properties is part of the Apache config, and indicates where Apache is expecting to find the (Tomcat side of the) Ajp connector. server.xml is part of the Tomcat config, and tells Tomcat where it should listen for Ajp (and other protocols). The email I sent was correct - the uncommented ports are those that were listed. The only difference between the two is the connection Timeout settings... ( I posted the correct server.xml file - the second email contains the correct one). I responded to that email -- and in fact the connection timeout was the only thing that looked odd to me. So that might be what's causing the problem. -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 11:27 AM To: Tomcat Users List Subject: Re: Mod_jk - won't execute jsp or servlets On Mon, 23 Dec 2002, Denise Mangano wrote: Thanks to all your help, I've gotten over some bumps. As it stands I can access any static pages in the Tomcat directory without having to type port 8080 ( i.e. I can access http://localhost/examples/servlets/index.html. However, whenever I try to execute a servlet or JSP it hangs indefinitely. The only errors appear in my mod_jk.log file: [ ... ] [Mon Dec 23 09:52:47 2002] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 110 [Mon Dec 23 09:52:47 2002] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 110 [ ... ] This seems to be the telling message. So is Tomcat started and running? And what port is it listening on? More completely, what port is Apache expecting it to listen on and what port is it set to listen on? The former is set in workers.properties. The latter is set in server.xml, particularly in the Connector tag for the Ajp connector (because it may be listening on different ports for different things, here we only care about Ajp). The default for that is 8009. It's probably best you post both of those files (i.e. workers.properties and server.xml) so we can see for sure what you have there. You say that Tomcat is listening on port 8080, but that is the default port for Tomcat's Http Connector (i.e. Tomcat standalone). So I suspect that is not the relevant info here. Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus
Re: progress, but still no mod_jk
Denese: libexec/mod_jk.so is correct---that's where mod_jk is located. So I added ApacheConfig modJk=/usr/local/apache-1.3.27/libexe/ to httpd.conf, as suggested in the catalina.out error message (thought maybe a full path would help), but Apache won't start---says ApacheConfig is invalid. Jerry Denise Mangano wrote: Jerry - you know that is the exact error message that I was getting at one point. Here two things that I did. I realized that the mod_jk.conf was being generated every time I started Tomcat. So any changes that I made to it were being overwritten every time I used it. The generated mod_jk.conf was pointing to libexec/mod_jk.so (In the first few lines of mod_jk.conf) but that was not where the file was on my box. I kept changing the path to the correct one, but it kept looking at libexec every time I restarted Tomcat. So I poked the net and found that if you modify the mod_jk.conf file you should place a copy in another location, for example I placed one right in the conf directory. Then change the Include statement in your httpd.conf file to point to that new location. (Try that first) I tried that but mod_jk still wasn't working. So it seemed to me that this error was coming from the file ApacheConfig. But the only place this file existed was in the build distribution that I unpacked, and built my mod_jk.so from (actual location was /jakarta-tomcat-connectors-4.1.17-src/jk/java/org/apache/ajp/tomcat4/config/ ). So I edited that file to reflect the proper location (replaced libexec with my actual Path). Then I built mod_jk.so again and replaced the one I had built previously. That seemed to do the trick. Every time Tomcat is started up, the autogenerated file contains the proper location. This might get rid of your error message, but may not get mod_jk to work. As of right now I have resorted to not using the mod_jk.conf at all, and placing the directives directly in the httpd.conf file...you may be luckier... Please let me know of your progress since we are in the same boat :) HTH Denise -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 21, 2002 8:50 PM To: tomcat-user Subject: progress, but still no mod_jk Okay, I removed the nested comments from server.xml and tomcat now starts up. http://localhost works http://localhost:8080 works (including servlets and jsps) ...but now http://localhost/examples/servlets produces a Not Found error (previously, was giving me the servlets index.html, but no longer). In catalina.out, there is what looks like a warning message about mod_jk: Make sure it is installed corectly or set the config location. Is this normal? Does this message always get written to catalina.out on startup? Or does it only show up when there is an error? Here's the entire output in catalina.out after Tomcat starts up: Dec 21, 2002 5:35:12 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 mod_jk location: libexec/mod_jk.so Make sure it is installed corectly or set the config location Using ApacheConfig modJk=PATH_TO_MOD_JK.SO_OR_DLL / Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 21, 2002 5:35:19 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Configuring mod_jk - Again! [getting desperate]
Denise: I have not moved the servlet or jsp example HTML files; they are in the tomcat tree. In addition, I wrote my own HelloWorld servlet and installed it in tomcat/webapps/j_tools---that's where the HTML and the servlet's WEB-INF directory are located. When I run Apache without Tomcat (it was broken because of the nested comments in server.xml), Apache was able to find the servlets in the Tomcat tree and display the HTML files. But since Tomcat was not running, the servlets would not work. However, now that the nested comments are out of server.xml and Tomcat is able to start, the HTML files are no longer being displayed. And I am now getting the mod_jk startup error message in catalina.out. Jerry Denise Mangano wrote: Jerry, I noticed previous to your last email regarding the problem you are having, that even though the JSP's and servlets would not work, you were able to browse the HTML files via http://localhost/examples/servlets ... I was unable to do even that. Do you also place your HTML files in your webapp directory as Paul just stated he does? If so, then how would Apache serve the static pages?? Is that through using Justin's suggestion of placing the following in my httpd.conf file? # Static files in the examples webapp are served by apache JkAutoAlias /var/tomcat4/webapps/dev.jscs-inc.com If you are storing your HTML files outside of Tomcat, then something is right in your setup that is connected the two. And that something could be what I am doing wrong... I'd appreciate it if you can possibly compare setups with me to see if I am missing anything. Thanks! Denise -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 21, 2002 9:05 PM To: Tomcat Users List Subject: Re: Configuring mod_jk - Again! [getting desperate] Denise: You shouldn't have to open up port 8009 to the ouside world; that's for internal communication between Tomcat and Apache. Users outside the firewall still come in through port 80. Jerry Denise Mangano wrote: Hi all :) So this is where I stand. I added all appropriate (I think) JkMount statements, in my httpd.conf file instead of using the mod_jk.conf. My situation: http://localhost works, http://localhost:8080/examples/servlets/index.html works, http://localhost/examples/servlets.index.html does NOT work. When I try to attempt any Tomcat pages without the :8080 it hangs indefinitely. I am getting pretty desperate, so I am seriously considering opting for mod_webapp, but I would prefer to get this working... On Tomcat startup no problems. On Apache startup, it shows mod_jk is configured. After attempting to access some pages I checked the logs and the only errors seems to occur in the mod_jk.log file (I attached a WordPad doc of the errors). I'm starting to wonder if the following might be my problem. Stupid question, but are my static pages supposed to be in my webapps folder in my $CATALINA_HOME directory??? If so, then the last thing Justin mentioned to add into my httpd.conf file would now make sense: # Static files in the examples webapp are served by apache JkAutoAlias /var/tomcat4/webapps/dev.jscs-inc.com I omitted this, because I am serving my static pages from the /var/www/html/ directory (that is my document root in my httpd.conf file), and didn't understand what this directive meant. Could it be that this is my problem? Also, I notice that the worker listens on port 8009. Although my server has a public IP address, it is accessed through a firewall. Therefor I needed to open ports 80, 8080, etc on my firewall in order for the pages to be viewed. Do I need to open port 8009? Thanks in advance! Calling all cars ;) Denise -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 21, 2002 1:53 AM To: [EMAIL PROTECTED] Subject: Re: Configuring mod_jk - Again! The 'LoadModule' directive must occur only once, and at top-level (e.g. outside of any VirtualHost directive). The same goes for JkWorkersFile, and JkLogFile (and related). Denise Mangano [EMAIL PROTECTED] wrote in message 5D83C44941AFD4118B6F0002B302984F4385BB@EXCHANGE_SERVER">news:5D83C44941AFD4118B6F0002B302984F4385BB@EXCHANGE_SERVER... Silly question - does the LoadModule statement stay grouped with the JkMoutn directives, or does that have to be placed with the other LoadModule directives... Thanks... (Thanks for piecing that together - I am going to give that a whirl)... Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Justin L. Spies [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 5:11 PM To: 'Tomcat Users List' Subject: RE: Configuring mod_jk - Again! Denise, Let me see if this helps you... In httpd.conf, try (I've cut up your example from below): LoadModule jk_module modules/mod_jk.so JkWorkersFile /usr/local/tomcat
javax.servlet does not exist?
I am trying to get a working mod_jk.so and have not been able to pull it off. I am trying once more to build it from the files obtained in jakarta-tomcat-connectors-4.1.12.tar but when I run ant in the jk directory, the build fails because javac cannot find javax.servlet.http. JAVA_HOME points to /usr/java/j2sdk1.4.0 and I have successfuly compiled a HelloWorld servlet; so javax is available to my system, and it does appear to get into the classpath by virtue of JAVA_HOME. So why can't ant build mod_jk.so? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: javax.servlet does not exist?
Sorry, one additional fine point---I know javax is available because in addition to my HelloWorld servlet, I also successfully compiled a servlet that uses the JavaMail API. Jerry Jerry Ford wrote: I am trying to get a working mod_jk.so and have not been able to pull it off. I am trying once more to build it from the files obtained in jakarta-tomcat-connectors-4.1.12.tar but when I run ant in the jk directory, the build fails because javac cannot find javax.servlet.http. JAVA_HOME points to /usr/java/j2sdk1.4.0 and I have successfuly compiled a HelloWorld servlet; so javax is available to my system, and it does appear to get into the classpath by virtue of JAVA_HOME. So why can't ant build mod_jk.so? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: javax.servlet does not exist?
Well, ah, oopsI seem to have shuffled things around since building my test servlets, I have added a CLASSPATH pointing to servlets.jar in $CATALINA_HOME/common/lib and all is well. For this step, at least. Ant builds. Jerry Jerry Ford wrote: Sorry, one additional fine point---I know javax is available because in addition to my HelloWorld servlet, I also successfully compiled a servlet that uses the JavaMail API. Jerry Jerry Ford wrote: I am trying to get a working mod_jk.so and have not been able to pull it off. I am trying once more to build it from the files obtained in jakarta-tomcat-connectors-4.1.12.tar but when I run ant in the jk directory, the build fails because javac cannot find javax.servlet.http. JAVA_HOME points to /usr/java/j2sdk1.4.0 and I have successfuly compiled a HelloWorld servlet; so javax is available to my system, and it does appear to get into the classpath by virtue of JAVA_HOME. So why can't ant build mod_jk.so? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
more progress, but still no mod_jk
I am back to being able to open my webapps in Apache without a port 8080 specification: http://localhost opens Apache's intro page http://localhost:8080 opens Tomcat's intro page, and servlets are available and functional http://localhost/examples/servlets (no port number) opens the servlets HTML page located in the Tomcat webapps directory but servlets do not work; I get an Internal Server Error from Apache on port 80. The Apache error log shows the following: [Sun Dec 22 11:41:09 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Sun Dec 22 11:41:09 2002] [error] (2)No such file or directory: Error while opening the workers, jk will not work [Sun Dec 22 11:41:10 2002] [notice] Apache/1.3.27 (Unix) mod_jk/1.2.0 configured -- resuming normal operations [Sun Dec 22 11:41:10 2002] [notice] Accept mutex: sysvsem (Default: sysvsem) These lines are repeated whenever I stop and restart Apache. The path in the Include statement in httpd.conf is: Include /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/auto/mod_jk.conf ...and mod_jk.conf in that location correctly identifies the location of the workers.properties: JkWorkersFile /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/conf/jk/workers.properties mod_jk.conf and workers.properties both have the following permissions: -rw-rw-r-- So what's wrong with this setup? Thanks, Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Configuring mod_jk - Again! [getting desperate]
Denise: Once Apache starts up, it runs as user nobody, not root. Jerry Denise Mangano wrote: Bill, As of right now starting from my tomcat folder down, permissions are 774 (rwx owner and group, r other). The only variant is that my webapps folder (including everything in it) has 775 (rwx owner and group, rx other). What is odd is that the jsp files that I uploaded I can see without using port 8080. And these jsp's have the same permissions as the examples folder and files within it. Also, apache runs as root - so wouldn't it have permissions? Thanks. Denise -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 22, 2002 9:08 PM To: [EMAIL PROTECTED] Subject: Re: Configuring mod_jk - Again! [getting desperate] Apache requires at least rx permissions on all directories upto and including $CATALINA_HOME/webapps/examples/servlets. You have to check the permissions all the way up the tree. Denise Mangano [EMAIL PROTECTED] wrote in message 5D83C44941AFD4118B6F0002B302984F4385C5@EXCHANGE_SERVER">news:5D83C44941AFD4118B6F0002B302984F4385C5@EXCHANGE_SERVER... I am running Linux 7.3. I checked all relevant pages and directories. All pages are at least read by everyone. I can get to my index page no problem which is in the /var/www/html directory. It is when I try to access anything in Tomcat without using the port number that I get this permissions error from Apache. For some reason I can also access a couple of JSP pages I placed in the ROOT directory without using the port number, but nothing else. I checked to see if there were any differences in permissions between those pages, and the example pages, but there aren't. In fact, all permissions in Tomcat are 775 (rwx for owner and group, rx for other). Thanks. Denise -Original Message- From: Kief Morris [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 22, 2002 7:36 AM To: Tomcat Users List Subject: RE: Configuring mod_jk - Again! [getting desperate] Denise Mangano typed the following on 22:41 21/12/2002 -0500 Sorry, should have posted this... When I type in http://localhost/examples/servlets/ I now get a Forbidden message saying that I do not have permission to access /examples/servlets/index.html. This message is coming from my Apache at mydomain.com Port 80. I feel like I may be getting close, but why this? I believe Tomcat is still listening on port 8080 - does that have to be changed? Since I get this error message, I am assuming that I am getting to the files (indicating that mod_jk may possibly be working) but the files cannot be served. Permission issue in httpd.conf file or somewhere in server.xml?? Check permissions on the file system. If you're on Unix, Apache usually runs as nobody, so the index.html file needs to be world-readable. If you're on Windows, make sure the file isn't opened in an editor or something. You shouldn't need to change Tomcat's port number, and it doesn't seem likely it would be an httpd.conf issue (and certainly not server.xml if Apache is giving the error). Kief -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: progress, but still no mod_jk
Bill: I added the listener line exactly as you showed it (actually, the line was already there but without the modJk=... part), and I still get these messages in catalina.out: mod_jk location: /usr/local/webserver/jakarta-tomcat-4.1.12-LE-jdk14/libexec/mod_jk.so Make sure it is installed corectly or set the config location Using ApacheConfig modJk=PATH_TO_MOD_JK.SO_OR_DLL / ...and now Apache won't even show me the HTML files in the tomcat/webapps directories. (I used to get at least that far.) Permissions on all directories s from webapps down are drwxr-xr-x. Jerry Bill Barker wrote: This would be because ApacheConfig goes in Tomcat's 'server.xml' file (except with a different syntax). The log message could be better (it's left over from Tomcat 3.3) :-(. The warning is simply because Tomcat has no way of knowing about your Apache install, so it is simply telling you that it is guessing based on the defaults. To make it go away, simply set: Server Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=libexec/mod_jk.so / ... Jerry Ford [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Denese: libexec/mod_jk.so is correct---that's where mod_jk is located. So I added ApacheConfig modJk=/usr/local/apache-1.3.27/libexe/ to httpd.conf, as suggested in the catalina.out error message (thought maybe a full path would help), but Apache won't start---says ApacheConfig is invalid. Jerry Denise Mangano wrote: Jerry - you know that is the exact error message that I was getting at one point. Here two things that I did. I realized that the mod_jk.conf was being generated every time I started Tomcat. So any changes that I made to it were being overwritten every time I used it. The generated mod_jk.conf was pointing to libexec/mod_jk.so (In the first few lines of mod_jk.conf) but that was not where the file was on my box. I kept changing the path to the correct one, but it kept looking at libexec every time I restarted Tomcat. So I poked the net and found that if you modify the mod_jk.conf file you should place a copy in another location, for example I placed one right in the conf directory. Then change the Include statement in your httpd.conf file to point to that new location. (Try that first) I tried that but mod_jk still wasn't working. So it seemed to me that this error was coming from the file ApacheConfig. But the only place this file existed was in the build distribution that I unpacked, and built my mod_jk.so from (actual location was /jakarta-tomcat-connectors-4.1.17-src/jk/java/org/apache/ajp/tomcat4/config / ). So I edited that file to reflect the proper location (replaced libexec with my actual Path). Then I built mod_jk.so again and replaced the one I had built previously. That seemed to do the trick. Every time Tomcat is started up, the autogenerated file contains the proper location. This might get rid of your error message, but may not get mod_jk to work. As of right now I have resorted to not using the mod_jk.conf at all, and placing the directives directly in the httpd.conf file...you may be luckier... Please let me know of your progress since we are in the same boat :) HTH Denise -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 21, 2002 8:50 PM To: tomcat-user Subject: progress, but still no mod_jk Okay, I removed the nested comments from server.xml and tomcat now starts up. http://localhost works http://localhost:8080 works (including servlets and jsps) ...but now http://localhost/examples/servlets produces a Not Found error (previously, was giving me the servlets index.html, but no longer). In catalina.out, there is what looks like a warning message about mod_jk: Make sure it is installed corectly or set the config location. Is this normal? Does this message always get written to catalina.out on startup? Or does it only show up when there is an error? Here's the entire output in catalina.out after Tomcat starts up: Dec 21, 2002 5:35:12 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 mod_jk location: libexec/mod_jk.so Make sure it is installed corectly or set the config location Using ApacheConfig modJk=PATH_TO_MOD_JK.SO_OR_DLL / Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 21, 2002 5:35:19 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL P
mod_jk...again
When I try to build mod_jk from the source contained in jakarta-tomcat-connectors-4.1.12-src.tar, the process breaks before it gets started. I am following the instructions on John Turner's how-to page, but when I run the configure script, it breaks at ltconfig---I get an error message that says a host type must be specified when the --no-verify flag is used. But running ltconfig --help shows no parameter for specifying host type, and the command is run from the configure script anyway. Can anyone tell me what's going on, and more importantly how do I correct it? Here's the output when I run configure; the path to apxs is correct, and JAVA_HOME points to a valid Java 1.4 JDK: [jford@gizmo native]$ ./configure --with-apxs=../../../apache_1.3.27/bin/apxs --with-java-home=$JAVA_HOME checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets $(MAKE)... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for ranlib... ranlib checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed [jford@gizmo native]$ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Still trying to make mod_jk work, need help
I am not able to build mod_jk from source, because the configure script breaks on ltconfg, as noted in a previous e-mail. So I took a compiled binary from a link on John Turner's how-to page and installed that. His link says its for tomcat 4.0, and I'm using 4.1.12, but John said previously that version numbers shouldn't matter. Without mod_jk in the mix, I have Apache 1.3.27 running, and Tomcat 4.1.12 running, and both work. Apache answers to localhost, Tomcat answers to localhost:8080, and servlets and JSPs work fine. I have also had tyhe two connected with mod_webapp.so and everything works fine. But when I put mod_jk into place and edit my server.xml file as instructed on John's howto page, Tomcat won't start. The Tomcat examples index pages do get displayed by Apache when I go to http://localhost/examples/servlets and ../jsp; I can even get my own HelloWorld html page in the Tomcat webapss directory to display. But the servlets themselves don't work, because Tomcat is not running. When I try to start Tomcat, I get the following error in catalina.out: SEVERE: Parse Fatal Error at line 52 column -1: Next character must be terminating comment . org.xml.sax.SAXParseException: Next character must be terminating comment . at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182) at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176) at org.apache.crimson.parser.Parser2.nextChar(Parser2.java:3098) at org.apache.crimson.parser.Parser2.maybeComment(Parser2.java:910) at org.apache.crimson.parser.Parser2.content(Parser2.java:1788) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500) at org.apache.crimson.parser.Parser2.parse(Parser2.java:305) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.Catalina.start(Catalina.java:449) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) I'm pretty sure there is no syntax error in my server.xml file; and I have not touched the global web.xml. But here's my server.xml file, in case anyone cares to look. Server port=8005 shutdown=SHUTDOWN debug=0 !-- the following line added per www.johnturner.com/howto for mod_jk; jf/21dec2002 -- Listener className=org.apache.ajp.tomcat4.config.ApacheConfig/ !-- Define the Tomcat Stand-Alone Service -- Service name=Tomcat-Standalone !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0/ !-- Define the top level container in our container hierarchy -- Engine name=Standalone defaultHost=localhost debug=0 Valve className=org.apache.catalina.valves.RequestDumperValve/ !-- Global logger unless overridden at lower levels -- Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ !-- Because this Realm is here, an instance will be shared globally -- Realm className=org.apache.catalina.realm.MemoryRealm / !-- Define the default virtual host -- Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=localhost_access_log. suffix=.txt pattern=common/ Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=localhost_log. suffix=.txt timestamp=true/ !-- following line added per www.johnturner.com/howto for mod_jk; jf/21dec2002 -- Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append=true forwardAll=false/ !-- Tomcat Root Context -- Context path= docBase=ROOT debug=0/ /Host /Engine /Service !-- !-- Define an Apache-Connector Service -- Service name=Tomcat-Apache Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ !-- Replace localhost with what your Apache ServerName is set to -- Engine className=org.apache.catalina.connector.warp.WarpEngine name=Apache debug=0 appBase=webapps !-- Global logger unless overridden at lower levels -- Logger
progress, but still no mod_jk
Okay, I removed the nested comments from server.xml and tomcat now starts up. http://localhost works http://localhost:8080 works (including servlets and jsps) ...but now http://localhost/examples/servlets produces a Not Found error (previously, was giving me the servlets index.html, but no longer). In catalina.out, there is what looks like a warning message about mod_jk: Make sure it is installed corectly or set the config location. Is this normal? Does this message always get written to catalina.out on startup? Or does it only show up when there is an error? Here's the entire output in catalina.out after Tomcat starts up: Dec 21, 2002 5:35:12 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 mod_jk location: libexec/mod_jk.so Make sure it is installed corectly or set the config location Using ApacheConfig modJk=PATH_TO_MOD_JK.SO_OR_DLL / Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 Dec 21, 2002 5:35:19 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Configuring mod_jk - Again! [getting desperate]
Denise: You shouldn't have to open up port 8009 to the ouside world; that's for internal communication between Tomcat and Apache. Users outside the firewall still come in through port 80. Jerry Denise Mangano wrote: Hi all :) So this is where I stand. I added all appropriate (I think) JkMount statements, in my httpd.conf file instead of using the mod_jk.conf. My situation: http://localhost works, http://localhost:8080/examples/servlets/index.html works, http://localhost/examples/servlets.index.html does NOT work. When I try to attempt any Tomcat pages without the :8080 it hangs indefinitely. I am getting pretty desperate, so I am seriously considering opting for mod_webapp, but I would prefer to get this working... On Tomcat startup no problems. On Apache startup, it shows mod_jk is configured. After attempting to access some pages I checked the logs and the only errors seems to occur in the mod_jk.log file (I attached a WordPad doc of the errors). I'm starting to wonder if the following might be my problem. Stupid question, but are my static pages supposed to be in my webapps folder in my $CATALINA_HOME directory??? If so, then the last thing Justin mentioned to add into my httpd.conf file would now make sense: # Static files in the examples webapp are served by apache JkAutoAlias /var/tomcat4/webapps/dev.jscs-inc.com I omitted this, because I am serving my static pages from the /var/www/html/ directory (that is my document root in my httpd.conf file), and didn't understand what this directive meant. Could it be that this is my problem? Also, I notice that the worker listens on port 8009. Although my server has a public IP address, it is accessed through a firewall. Therefor I needed to open ports 80, 8080, etc on my firewall in order for the pages to be viewed. Do I need to open port 8009? Thanks in advance! Calling all cars ;) Denise -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 21, 2002 1:53 AM To: [EMAIL PROTECTED] Subject: Re: Configuring mod_jk - Again! The 'LoadModule' directive must occur only once, and at top-level (e.g. outside of any VirtualHost directive). The same goes for JkWorkersFile, and JkLogFile (and related). Denise Mangano [EMAIL PROTECTED] wrote in message 5D83C44941AFD4118B6F0002B302984F4385BB@EXCHANGE_SERVER">news:5D83C44941AFD4118B6F0002B302984F4385BB@EXCHANGE_SERVER... Silly question - does the LoadModule statement stay grouped with the JkMoutn directives, or does that have to be placed with the other LoadModule directives... Thanks... (Thanks for piecing that together - I am going to give that a whirl)... Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Justin L. Spies [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 5:11 PM To: 'Tomcat Users List' Subject: RE: Configuring mod_jk - Again! Denise, Let me see if this helps you... In httpd.conf, try (I've cut up your example from below): LoadModule jk_module modules/mod_jk.so JkWorkersFile /usr/local/tomcat/conf/jk/workers.properties JkLogFile /usr/local/tomcat/logs/mod_jk.log JkLogLevel info JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %r %s %T # Send servlet for context /examples to worker named worker1 JkMount /servlet/* ajp13 JkMount /examples/jsp/*.jsp ajp13 JkMount /examples/servlet/* ajp13 # Send JSPs for context /examples to worker named worker1 JkMount /*.jsp ajp13 JkMount /admin/* ajp13 JkMount /manager/* ajp13 # Static files in the examples webapp are served by apache JkAutoAlias /var/tomcat4/webapps/dev.jscs-inc.com # This will fix the missing images for you... Alias /examples /var/tomcat4/webapps/dev.mydomain.com/examples Alias /tomcat-docs /var/tomcat4/webapps/dev.mydomain.com/tomcat-docs # The following line prohibits users from directly access WEB-INF Location /examples/WEB-INF/ AllowOverride None deny from all /Location Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 5:03 PM To: 'Tomcat Users List' Subject: RE: Configuring mod_jk - Again! Ok, now I added the JkMount /examples/* worker1 and nothing works. Everything hangs indefinitely. I had all this placed at the end of my httpd.conf file so it would apply to all virtual hosts. I'm completely at a loss, and quite frustrated actually : ( At this point I do not care if the examples work, I just want to get my app that was working before back up... What on earth could possibly be going wrong? Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 3:56 PM To: Tomcat Users List Subject: RE: Configuring
Re: Configuring mod_jk - Again!
Denise: I'm probably going to offend somebody with my suggestion, but... As much trouble as you are having making mod_jk work (and I was having the same trouble until I got interupted and had to put Tomcat aside momentarily), you might consider shifting gears temporarily. Try mod_webapp.so. It's in the connectors tarball (jakarta-tomcat-connectors-4.1.12-src) although I had better luck building it from CVS---instructions are in the tarball. After the trouble I was having with mod_jk, I was amazed at how easily webapp built, and how easy it was to configure and use. I know John said it is deprecated and mod_jk is the wave of the future, and I believe him (actually, I think jk2 is the ultimate intended wave, but that's another project :) And I am going to get mod_jk to work eventually, with, I hope, John's help. But in the interim, mod_webapp, deprecated or not, does work. If you are hard pressed to meet a deadline, you might take a look at it, get it running, get your app set up and fine-tuned, and then work on mod_jk at a more leisurely pace. Jerry Denise Mangano wrote: Silly question - does the LoadModule statement stay grouped with the JkMoutn directives, or does that have to be placed with the other LoadModule directives... Thanks... (Thanks for piecing that together - I am going to give that a whirl)... Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Justin L. Spies [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 5:11 PM To: 'Tomcat Users List' Subject: RE: Configuring mod_jk - Again! Denise, Let me see if this helps you... In httpd.conf, try (I've cut up your example from below): LoadModule jk_module modules/mod_jk.so JkWorkersFile /usr/local/tomcat/conf/jk/workers.properties JkLogFile /usr/local/tomcat/logs/mod_jk.log JkLogLevel info JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %r %s %T # Send servlet for context /examples to worker named worker1 JkMount /servlet/* ajp13 JkMount /examples/jsp/*.jsp ajp13 JkMount /examples/servlet/* ajp13 # Send JSPs for context /examples to worker named worker1 JkMount /*.jsp ajp13 JkMount /admin/* ajp13 JkMount /manager/* ajp13 # Static files in the examples webapp are served by apache JkAutoAlias /var/tomcat4/webapps/dev.jscs-inc.com # This will fix the missing images for you... Alias /examples /var/tomcat4/webapps/dev.mydomain.com/examples Alias /tomcat-docs /var/tomcat4/webapps/dev.mydomain.com/tomcat-docs # The following line prohibits users from directly access WEB-INF Location /examples/WEB-INF/ AllowOverride None deny from all /Location Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 5:03 PM To: 'Tomcat Users List' Subject: RE: Configuring mod_jk - Again! Ok, now I added the JkMount /examples/* worker1 and nothing works. Everything hangs indefinitely. I had all this placed at the end of my httpd.conf file so it would apply to all virtual hosts. I'm completely at a loss, and quite frustrated actually : ( At this point I do not care if the examples work, I just want to get my app that was working before back up... What on earth could possibly be going wrong? Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 3:56 PM To: Tomcat Users List Subject: RE: Configuring mod_jk - Again! On Fri, 20 Dec 2002, Denise Mangano wrote: Well I tried it. And I added additional JkMount statements: LoadModule jk_module modules/mod_jk.so JkWorkersFile /usr/local/tomcat/conf/jk/workers.properties JkLogFile /usr/local/tomcat/logs/mod_jk.log JkLogLevel info JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %r %s %T JkMount /*.jsp worker1 JkMount /tomcat-docs/*.jsp worker1 JkMount /admin/j_security_check worker1 JkMount /admin/*.do worker1 JkMount /admin/*.jsp worker1 JkMount /webdav/*.jsp worker1 JkMount /examples/jsp/security/protected/j_security_check worker1 JkMount /examples/snoop worker1 JkMount /examples/servlet/* worker1 JkMount /examples/CompressionTest worker1 JkMount /examples/*.jsp worker1 JkMount /examples/servletToJsp worker1 JkMount /examples/SendMailServlet worker1 JkMount /manager/html/* worker1 JkMount /manager/* worker1 JkMount /manager/*.jsp worker1 For workers.properties I first tried: worker.list=worker1 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 Now when I go to http://localhost/index.jsp it displays the tomcat home page, but the images are missing (looks like the path is not right)... You don't really give enough information to tell what's going on with this, but sometimes there are
another mod_jk attempt failing
When I try to build mod_jk from the source contained in jakarta-tomcat-connectors-4.1.12-src.tar, the process breaks before it gets started. I am following the instructions on John Turner's how-to page, but when I run the configure script, it breaks at ltconfig---I get an error message that says a host type must be specified when the --no-verify flag is used. But running ltconfig --help shows no parameter for specifying host type, and the command is run from the configure script anyway. Can anyone tell me what's going on, and more importantly how do I correct it? Here's the output when I run configure; the path to apxs is correct, and JAVA_HOME points to a valid Java 1.4 JDK: [jford@gizmo native]$ ./configure --with-apxs=../../../apache_1.3.27/bin/apxs --with-java-home=$JAVA_HOME checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets $(MAKE)... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for ranlib... ranlib checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed [jford@gizmo native]$ Thanks. Jerry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat Documentation WAS: jsps and servlets don't work
Rasputin wrote: * Joseph Shraibman [EMAIL PROTECTED] [1233 03:33]: Jerry Ford wrote: With all due respect and recognition to the enormous efforts you personally appear to have put into making Tomcat accessible, the documentation is neither comprehensive nor adequate, for either Tomcat or whatever is the connector du jour. There are pockets of good documentation, such as your how-tos and seemingly tireless presence on this mail list, surrounded by lots of chaffe---incomplete, inaccurate, out-of-date, even non-existent files inside of tarballs or littered around the jakarta.apache.org website. Definitely. But at the end of the day this is an Open Source project. If people don't want to write documentation, they won't, and there's not a lot you can do to persuade them. I'm not playing the 'use the source Luke' card, I'm just telling you how it is. In my experience of Open Source projects, all ranting does is getting you killfiled. That is the last thing I want. :) I still need help and hope to get answers to my questions when I plunge back in and try to get a working mod_jk. And really, I do understand how open source works, and how nobody is obligated to document to my standards. And I also hear John when he says put up or shut up. Since I can't put up until I know more and can make it work on my own damn machine, I'll shut up now (until I start posting the Qs). Jerry The real fix for this is to put the website docs into CVS and let people send patches. Then people who like writing documentation can write docs, and the coders can get on with coding. Maybe it's already in CVS. I couldn't find any docum... oh :D Craig (or anyone), do we have an address to recieve doc patches? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[off-topic] Re: jsps and servlets don't work
/*** * * Caution: LONG Rant Warning :) * **/ Turner, John wrote: I don't think they are poorly documented at all. Just the HOWTOs written by myself and others on this list alone provide comprehensive documentation. John: // begin rant: With all due respect and recognition to the enormous efforts you personally appear to have put into making Tomcat accessible, the documentation is neither comprehensive nor adequate, for either Tomcat or whatever is the connector du jour. There are pockets of good documentation, such as your how-tos and seemingly tireless presence on this mail list, surrounded by lots of chaffe---incomplete, inaccurate, out-of-date, even non-existent files inside of tarballs or littered around the jakarta.apache.org website. I don't mean to rag on you, or the Apache group. I know it's all free software and, though it may not sound like it, I am an appreciative fan, now that I have stumbled onto this list and located your how-to page. But I've spent a lot of time fruitlessly searching the jakarta.apache.org website for answers to my questions and I have found the doc set taken as a whole to be contradictory, poorly organized, and in some cases downright misleading. If you have any pull with the development team, IMHO, you ought to ask them give the website a thorough going over, removing old, out of date stuff (if mod_webapp and mod_jk are deprecated, why are they included in the connectors tarball with nothing in the READMEs to suggest they are out of date?) and updating whats left so that the entire doc set accurately reflects the current state of the software. // end rant :) Jerry My point was that Tomcat is free, and it is developed in the open source model. That means the quickest way to get your suggestions implemented is to do them yourself. The source for the ApacheConfig class is in the Tomcat source bundle, where it should be. The package name is the same name as used in server.xml. Please keep in mind that the ApacheConfig class is a convenience feature, and is not a core feature of Tomcat. The fact that it is there at all is gravy, not a requirement, and more a feature of connector development than Tomcat development. John -Original Message- From: Joseph Shraibman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 3:02 PM To: Tomcat Users List Subject: Re: jsps and servlets don't work How can I patch if I can't even figure out how to set it up? Tomat and mod_jk are very poorly documented. I'm not even sure where the source to the autogenerator is. Turner, John wrote: Maybe so. Seems pretty straightforward to me. I'm sure the dev team would welcome a patch. Since the dev team is focusing on JK2, and ApacheConfig only works for JK, I'm not sure they will give it much attention. Worth a shot, though. John -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: How do you get a C:\ prompt in Windows XP?
enter cd c:\ Ronin Quigley wrote: Thanks for your tips. When I type C:\ I get the following message 'C:\' is not recognised as an internal or external command, operable program or batch file. Any other suggestions? Rocket - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, December 19, 2002 12:13 AM Subject: RE: Help needed to run Tomcat 4.1.12 Agreedavoid spaces in pathnames if you can. As an aside, there is no reason to switch directories to start Tomcat. You can do so by typing something like c:\tomcat\bin\startup.bat from any command prompt in Windows. John -Original Message- From: Paul Yunusov [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:04 PM To: Tomcat Users List Subject: Re: Help needed to run Tomcat 4.1.12 On Wednesday 18 December 2002 06:27 pm, Ronin Quigley wrote: I am running Windows XP and have done the following: a.. Installed Jave SDK and set the path variable to stemRoot%\System32\Wbem;C:Java\bin; b.. Downloaded release version 4.1.12 of Tomcat c.. Set the variable JAVA HOME=C:\JAVA d.. Set the variable CATALINA_HOME= C:\TOMCAT\JAKARTA-TOMCAT 4.1.12 e.. Tested the above by doing the ECHO test and they were fine. The command prompt in Windows XP automatically defaults to C:\Documents and Settings\Go For It Web Design, how do I get a C:\ prompt? And once I get a C:\ prompt can I start it by the following? C:\ cd tomcat\jakarta-tomcat 4.1.12\bin startup.bat Any help would be much appreciated. Rocket To change the working directory to C: type C:\ and press enter in the command prompt (if my memory doesn't betray me - my Windows days are long gone). Your steps to start tomcat seem be correct but paths and names in the description of environment variables are a mess (JAVA_HOME should have the _, SystemRoot instead of stemRoot, C: must be followed by a \ in paths, there is a - instead of a space between jakarta-tomcat and 4.1.12 in the standard distribution, at least on Linux). I attribute this chaos to fast typing but I'd double check if I were you. My Windows experience taught me to avoid spaces in paths also. HTH, Paul -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Connecting Tomcat 4.1.12 with Apache 1.3
John: I took your advice from yesterday, replaced mod_webapp.so with mod_jk.so and now jsps and servlets don't work. They worked fine under mod_webapp, including my own HelloWorld app in addition to the Tomcat examples. Now they don't work, although I am able to get to the HTML pages using, for example, http://localhost/examples/servlets. But the servlets and jsp examples themselves all generate an Apache port 80 internal server error. I followed the instructions on your howto page, (except that the configure script fails---I have been able to build apache, tomcat, ant, and mod_webapp on my system, but mod_jk fails, so I just grabbed your posted binary.) I added the listener statements to server.xml. mod_jk.conf shows Location entries for each of the webapps, and there is a JkMount entry for the servlets (including my HelloWorld entry). mod_jk.log is empty. What more do I need to do? Thanks, Jerry Turner, John wrote: Mod_webapp is deprecated, and has some fairly serious limitations. JK/JK2 is the better choice if you are concerned with future growth. If you're having problems, perhaps my HOWTOs will help: http://www.johnturner.com/howto John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:15 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/jak arta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Connecting Tomcat 4.1.12 with Apache 1.3
I also will assume that you have the 'Include' statement in the httpd.conf for mod_jk.properties (as well as the LoadModule/AddModule directives for mod_jk.so). Ah, oops, you may have hit it...I put in the include statement, but I forgot to load the module. Thanks. Jerry Ben Ricker wrote: On Fri, 2002-12-13 at 12:16, Jerry Ford wrote: John: I added the listener statements to server.xml. mod_jk.conf shows Location entries for each of the webapps, and there is a JkMount entry for the servlets (including my HelloWorld entry). mod_jk.log is empty. Do you see that mod_jk is being loaded by Apache when you start it or in Apache's error_log? I see the following when I start Apache: Apache/1.3.26 (Unix) mod_jk/1.2.0 configured -- resuming normal operations I also will assume that you have the 'Include' statement in the httpd.conf for mod_jk.properties (as well as the LoadModule/AddModule directives for mod_jk.so). You might also want to bump the 'JkLogLevel' in your mod_jk.properties to get the debug level to get some feedback on what is going on. Hth, Ben Ricker What more do I need to do? Thanks, Jerry Turner, John wrote: Mod_webapp is deprecated, and has some fairly serious limitations. JK/JK2 is the better choice if you are concerned with future growth. If you're having problems, perhaps my HOWTOs will help: http://www.johnturner.com/howto John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:15 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/jak arta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Connecting Tomcat 4.1.12 with Apache 1.3
Denise: I have Red Hat 7.1. I didn't have a problem unzipping it; but when I tried to compile, it failed the first time, then compiled, but when I run the configure script, it fails consistently. Now that I'm responding to you, I went back to John's how-to page to check my facts and I think see where I went wrong...I may have grabbed a Solaris file, which would explain why it wouldn't build on Linux. It's the only 4.1.12 tomcat version in his connector matrix, so I took it not seeing it was for the wrong system. When it failed to install, I went back and got the binary instead. I see he has a 4.1.10 version for Linux; maybe I'll try that. Or maybe not, if I can get the binary to work. I don't really feel a need to build it, just want to get it working. :) Jerry Denise Mangano wrote: Jerry, I know you have same version of Apache and Tomcat I do. By any chance are you running RedHat Linux 7.2 / 7.3? I ran into same problem with encountering error during configure, and just downloaded the binary. That is the binary that I downloaded, but when I try to gunzip it tells me the file is not in gzip format. Did you have a similar problem? Denise -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 1:17 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 John: I took your advice from yesterday, replaced mod_webapp.so with mod_jk.so and now jsps and servlets don't work. They worked fine under mod_webapp, including my own HelloWorld app in addition to the Tomcat examples. Now they don't work, although I am able to get to the HTML pages using, for example, http://localhost/examples/servlets. But the servlets and jsp examples themselves all generate an Apache port 80 internal server error. I followed the instructions on your howto page, (except that the configure script fails---I have been able to build apache, tomcat, ant, and mod_webapp on my system, but mod_jk fails, so I just grabbed your posted binary.) I added the listener statements to server.xml. mod_jk.conf shows Location entries for each of the webapps, and there is a JkMount entry for the servlets (including my HelloWorld entry). mod_jk.log is empty. What more do I need to do? Thanks, Jerry Turner, John wrote: Mod_webapp is deprecated, and has some fairly serious limitations. JK/JK2 is the better choice if you are concerned with future growth. If you're having problems, perhaps my HOWTOs will help: http://www.johnturner.com/howto John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:15 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/sr c/jak arta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc
Re: Connecting Tomcat 4.1.12 with Apache 1.3
No, wait, that's not true...I did get the right one (or as close as I could come, the connector cell in the matrix says Tomcate 4.0x). I got confused because I'm not at the Linux box right now, I checked his website from my Win2000 machine and the Solaris link was the one that showed the last visit. I must have clicked it from this computer, even though I didn't download it---not only for Solaris, but also wrong Apache. Jerry Jerry Ford wrote: Denise: I have Red Hat 7.1. I didn't have a problem unzipping it; but when I tried to compile, it failed the first time, then compiled, but when I run the configure script, it fails consistently. Now that I'm responding to you, I went back to John's how-to page to check my facts and I think see where I went wrong...I may have grabbed a Solaris file, which would explain why it wouldn't build on Linux. It's the only 4.1.12 tomcat version in his connector matrix, so I took it not seeing it was for the wrong system. When it failed to install, I went back and got the binary instead. I see he has a 4.1.10 version for Linux; maybe I'll try that. Or maybe not, if I can get the binary to work. I don't really feel a need to build it, just want to get it working. :) Jerry Denise Mangano wrote: Jerry, I know you have same version of Apache and Tomcat I do. By any chance are you running RedHat Linux 7.2 / 7.3? I ran into same problem with encountering error during configure, and just downloaded the binary. That is the binary that I downloaded, but when I try to gunzip it tells me the file is not in gzip format. Did you have a similar problem? Denise -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 1:17 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 John: I took your advice from yesterday, replaced mod_webapp.so with mod_jk.so and now jsps and servlets don't work. They worked fine under mod_webapp, including my own HelloWorld app in addition to the Tomcat examples. Now they don't work, although I am able to get to the HTML pages using, for example, http://localhost/examples/servlets. But the servlets and jsp examples themselves all generate an Apache port 80 internal server error. I followed the instructions on your howto page, (except that the configure script fails---I have been able to build apache, tomcat, ant, and mod_webapp on my system, but mod_jk fails, so I just grabbed your posted binary.) I added the listener statements to server.xml. mod_jk.conf shows Location entries for each of the webapps, and there is a JkMount entry for the servlets (including my HelloWorld entry). mod_jk.log is empty. What more do I need to do? Thanks, Jerry Turner, John wrote: Mod_webapp is deprecated, and has some fairly serious limitations. JK/JK2 is the better choice if you are concerned with future growth. If you're having problems, perhaps my HOWTOs will help: http://www.johnturner.com/howto John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:15 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/sr c/jak arta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form
Re: Connecting Tomcat 4.1.12 with Apache 1.3
Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/jakarta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Connecting Tomcat 4.1.12 with Apache 1.3
BTW, the configuration lines that go in httpd.conf for webapp are entirely different than what is required for mod_jk. They serve the same function, but they are entirely different connectors. It will take some reading to make the transition. Jerry Jerry Ford wrote: Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/jakarta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Connecting Tomcat 4.1.12 with Apache 1.3
John: Thanks, I'll try it. But, your website matrix of connectors/OSs/server versions just misses my setup on each detail---I'm running Apache 1.3.27 and Tomcat 4.1.12 on Red Hat Linux 7.1; your matrix shows Apache 1.3.26, Tomcat 4.1.10, RHLinux 7.2. How critical are version numbers? Jerry Turner, John wrote: Mod_webapp is deprecated, and has some fairly serious limitations. JK/JK2 is the better choice if you are concerned with future growth. If you're having problems, perhaps my HOWTOs will help: http://www.johnturner.com/howto John -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:15 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/src/jak arta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.419 / Virus Database: 235 - Release Date: 11/13/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Connecting Tomcat 4.1.12 with Apache 1.3
Denise: You do not need SSL unless you want SSL. Tomcat works just fine without it, both as a standalone and as an Apache extension. But I don't know what the answer is if your Apache server is already configured for SSL. You're operating outside of my comfort zone. :) I don't use SSL. You need Tomcat (whether through Apache or standalone) in order to access the JSP. Just going to the JSP through http:// without a Java engine (a.k.a. Tomcat) won't work. Jerry Denise Mangano wrote: Just an after thought here... Even though I can access the JSP from my web site in Apache, I just tried to access it through the https:// protocol. It just hung and did not load. Do I have to configure something in Tomcat to allow for SSL connection to the JSP's? I am looking at Jakarta's site and it is saying that when using Tomcat as a standalone server, SSL has to be configured. But when running Tomcat primarily as a Servlet/JSP container behind another web server, such as Apache the SSL is configured on the web server, which it is (I already have a certificate). What am I missing? The only time I will need to access Tomcat from my web site is over a secure connection. Sorry for the trivial questions, as I said I'm new to this. Thanks in advance, Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Denise Mangano [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 4:29 PM To: 'Tomcat Users List' Subject: RE: Connecting Tomcat 4.1.12 with Apache 1.3 Thank you so much for getting back to me about that. I have just been trying to read up on the mod_jk, and was hoping there was another option. I do have one more question though related to running JSP with Tomcat. If I make my entire form JSP, and run from within Tomcat, and after it communicates with the payment server, an updated JSP page will be displayed (depending on the data received from the bank). Would I still have to make the connection between Apache and Tomcat? It would basically be a link from my website to the form, which will be JSP. I put up a dummy page and had a link to one of the example JSP that came with Tomcat. The link worked Ok, and the servlet ran fine. Thanks again! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -Original Message- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 11, 2002 3:39 PM To: Tomcat Users List Subject: Re: Connecting Tomcat 4.1.12 with Apache 1.3 BTW, the configuration lines that go in httpd.conf for webapp are entirely different than what is required for mod_jk. They serve the same function, but they are entirely different connectors. It will take some reading to make the transition. Jerry Jerry Ford wrote: Denise: I have just got my Apache 1.3.27/Tomcat 4.1.12 connection to work. Answers to your questions are yes, and yes. You need a connector between them, and mod_jk.so is one such connector. However, I had a devil of a time locating any connector on the apache.org website, and I never was able to make mod_jk work (I tried using the version that did work with my Tomcat 3.2 installation, but it did not work with 4.1 and I was not able to locate mod_jk---any version---on the apache website in order to rebuild). I ended up using mod_webapp.so, which is another connector. It's located in the jakarta-tomcat-connectors-4.1.12-src.tar.gz, which you can download from http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/sr c/ (the same directory as tomcat itself). When you unpack it, look for README.txt in the webapp directory. It will tell you how to build the connector from CVS. Follow the directions in the readme. They're clear, straightforward, and the build process was smooth and routine, for me at least. Jerry http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/s rc/jakarta-tomcat-connectors-4.1.12-src.tar.gz Denise Mangano wrote: Hi all, I am fairly new to using Apache / Tomcat. I currently have my website set up in Apache, running in the /var/html directory. I have installed Tomcat because I have a form page (HTML) that I want to run a servlet with to process a credit card payment with an outside payment processor. I have seen some instances that people have stated I have to do some special configuration in order to use both Apache and Tomcat together. Is this so? If so, then are there any good resources for this? Perhaps using JSP for the form will be better because I want a custom page to display depending on what error message will come back from the payment engine. If that is the case then wouldn't I need the connection between Apache and Tomcat? (the images I will need for the JSP page is stored in apache web directory as well). Is this the mod_jk plug in? (I am running RedHat Linux 7.3) Thanks in advance! Denise Mangano Help Desk Analyst Complus Data Innovations, Inc. -- To unsubscribe, e-mail