RE: Manager access problems
There's multiple connectors configured in tomcat/conf/server.xml. I have to do JkMount for each webapp I want mapped into Apache in httpd.conf, but I can still access the regular tomcat page on port 8080, just like when tomcat is running as a standalone http server. I never shut off the standalone http server running on port 8080, and I would like to be able to access the manager application using port 8080 (directly through the tomcat standalone http server, not using apache and mod_jk, so I don't have manager and admin JkMounted into apache. Even before I installed and configured mod_jk, I was running tomcat in standalone mode and I couldn't access manager from a remote host, but I can access it from the localhost. I anticipated finding one of those Valve.../Valve entries in manager.xml that only allows you to access it from certain hosts, but there was no such entry, so I'm stumped as to why it's possible to access it using mod_jk, but I get that access denied error when using tomcat's standalone http server. Am I making any sense? Greg No, it's not needed. Anyways, why do you think you would be able to access the webapp on http://IP-ADDRESS:8080/manager/html/? 8080 is the port tomcat listens to. It has nothing to do with what you define in httpd.conf. 80 is the port apache listens to. It talks with tomcat through port 8009 you defined in workers.properties. By default, 80 is the default port that apache uses. If virtual host and jk2 are working for you, you should be able to access your webapp without defining any port. There are a lot of good posts on port 8080 and 80. You may want to do a search on the archieve. Cheers:) -Yan -Original Message- From: Greg Adams [mailto:[EMAIL PROTECTED] Sent: May 10, 2004 14:49 To: Tomcat Users List Subject: RE: Manager access problems yes. Would it be helpful to post the entire httpd.conf? It's pretty long... Your apache listens on port 80, no? -Yan -Original Message- From: Greg Adams [mailto:[EMAIL PROTECTED] Sent: May 10, 2004 10:23 To: [EMAIL PROTECTED] Subject: Manager access problems I've installed tomcat 5.0.19 on solaris 2.8. I've also installed jk-1.2.5 to connect tomcat to apache 1.3.27. I'm having no problems with jk, my problem is when trying to access the manager application. If I access it on the localhost using port 8080, http://localhost:8080/manager/html/, I have no problem, but when I try to access it on port 8080 from another host, http://IP-ADDRESS:8080/manager/html/, I get a HTTP Status 403 - Access to the requested resource has been denied error message. If I access it through the jk connector from another host, http://IPADDRESS/manager/html/, I get no error message... From looking at the FAQ's and the Manager how-to, I've looked at the following: TOMCAT_ROOT/conf/Catalina/localhost/manager.xml: !-- Context configuration file for the Tomcat Manager Web App $Id: manager.xml,v 1.1.1.1 2002/07/18 16:48:14 remm Exp $ -- Context path=/manager docBase=../server/webapps/manager debug=0 privileged=true !-- Link to the user database we will get roles from -- ResourceLink name=users global=UserDatabase type=org.apache.catalina.UserDatabase/ /Context relevant section from httpd.conf LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c # Configure mod_jk # JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel info # Tomcat Virtual Host # VirtualHost 199.42.192.190:80 DocumentRoot /usr/local/apache/htdocs ServerName yoda.ddm.apm.bpm.eds.com JkMount /servlets-examples/* ajp13 JkMount /manager/* ajp13 /VirtualHost workers.properties worker.list= ajp13 worker.ajp13.host=yoda.ddm.apm.bpm.eds.com worker.ajp13.port=8009 worker.ajp13.type=ajp13 server.xml - I'm using the default server.xml bundled with tomcat 5.0.19 Thanks for any ideas... Greg - 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: Manager access problems
Nope, I already read that part of the manager how-to. As I said, I'm able to access the manager webapp using jk, and even using the standalone http server on port 8080, which would be impossible if I hadn't added a user in the manager role. I ran into a problem accessing the manager admin apps. I didn't realize you had to add users in the Jakarta-tomcat-5.0.19/conf/tomcat-users.xml file. -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 2:22 PM To: 'Tomcat Users List' Subject: RE: Manager access problems No, it's not needed. Anyways, why do you think you would be able to access the webapp on http://IP-ADDRESS:8080/manager/html/? 8080 is the port tomcat listens to. It has nothing to do with what you define in httpd.conf. 80 is the port apache listens to. It talks with tomcat through port 8009 you defined in workers.properties. By default, 80 is the default port that apache uses. If virtual host and jk2 are working for you, you should be able to access your webapp without defining any port. There are a lot of good posts on port 8080 and 80. You may want to do a search on the archieve. Cheers:) -Yan -Original Message- From: Greg Adams [mailto:[EMAIL PROTECTED] Sent: May 10, 2004 14:49 To: Tomcat Users List Subject: RE: Manager access problems yes. Would it be helpful to post the entire httpd.conf? It's pretty long... Your apache listens on port 80, no? -Yan -Original Message- From: Greg Adams [mailto:[EMAIL PROTECTED] Sent: May 10, 2004 10:23 To: [EMAIL PROTECTED] Subject: Manager access problems I've installed tomcat 5.0.19 on solaris 2.8. I've also installed jk-1.2.5 to connect tomcat to apache 1.3.27. I'm having no problems with jk, my problem is when trying to access the manager application. If I access it on the localhost using port 8080, http://localhost:8080/manager/html/, I have no problem, but when I try to access it on port 8080 from another host, http://IP-ADDRESS:8080/manager/html/, I get a HTTP Status 403 - Access to the requested resource has been denied error message. If I access it through the jk connector from another host, http://IPADDRESS/manager/html/, I get no error message... From looking at the FAQ's and the Manager how-to, I've looked at the following: TOMCAT_ROOT/conf/Catalina/localhost/manager.xml: !-- Context configuration file for the Tomcat Manager Web App $Id: manager.xml,v 1.1.1.1 2002/07/18 16:48:14 remm Exp $ -- Context path=/manager docBase=../server/webapps/manager debug=0 privileged=true !-- Link to the user database we will get roles from -- ResourceLink name=users global=UserDatabase type=org.apache.catalina.UserDatabase/ /Context relevant section from httpd.conf LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c # Configure mod_jk # JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel info # Tomcat Virtual Host # VirtualHost 199.42.192.190:80 DocumentRoot /usr/local/apache/htdocs ServerName yoda.ddm.apm.bpm.eds.com JkMount /servlets-examples/* ajp13 JkMount /manager/* ajp13 /VirtualHost workers.properties worker.list= ajp13 worker.ajp13.host=yoda.ddm.apm.bpm.eds.com worker.ajp13.port=8009 worker.ajp13.type=ajp13 server.xml - I'm using the default server.xml bundled with tomcat 5.0.19 Thanks for any ideas... Greg - 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] - 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]
Manager access problems
I've installed tomcat 5.0.19 on solaris 2.8. I've also installed jk-1.2.5 to connect tomcat to apache 1.3.27. I'm having no problems with jk, my problem is when trying to access the manager application. If I access it on the localhost using port 8080, http://localhost:8080/manager/html/, I have no problem, but when I try to access it on port 8080 from another host, http://IP-ADDRESS:8080/manager/html/, I get a HTTP Status 403 - Access to the requested resource has been denied error message. If I access it through the jk connector from another host, http://IPADDRESS/manager/html/, I get no error message... From looking at the FAQ's and the Manager how-to, I've looked at the following: TOMCAT_ROOT/conf/Catalina/localhost/manager.xml: !-- Context configuration file for the Tomcat Manager Web App $Id: manager.xml,v 1.1.1.1 2002/07/18 16:48:14 remm Exp $ -- Context path=/manager docBase=../server/webapps/manager debug=0 privileged=true !-- Link to the user database we will get roles from -- ResourceLink name=users global=UserDatabase type=org.apache.catalina.UserDatabase/ /Context relevant section from httpd.conf LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c # Configure mod_jk # JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel info # Tomcat Virtual Host # VirtualHost 199.42.192.190:80 DocumentRoot /usr/local/apache/htdocs ServerName yoda.ddm.apm.bpm.eds.com JkMount /servlets-examples/* ajp13 JkMount /manager/* ajp13 /VirtualHost workers.properties worker.list= ajp13 worker.ajp13.host=yoda.ddm.apm.bpm.eds.com worker.ajp13.port=8009 worker.ajp13.type=ajp13 server.xml - I'm using the default server.xml bundled with tomcat 5.0.19 Thanks for any ideas... Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Manager access problems
yes. Would it be helpful to post the entire httpd.conf? It's pretty long... Your apache listens on port 80, no? -Yan -Original Message- From: Greg Adams [mailto:[EMAIL PROTECTED] Sent: May 10, 2004 10:23 To: [EMAIL PROTECTED] Subject: Manager access problems I've installed tomcat 5.0.19 on solaris 2.8. I've also installed jk-1.2.5 to connect tomcat to apache 1.3.27. I'm having no problems with jk, my problem is when trying to access the manager application. If I access it on the localhost using port 8080, http://localhost:8080/manager/html/, I have no problem, but when I try to access it on port 8080 from another host, http://IP-ADDRESS:8080/manager/html/, I get a HTTP Status 403 - Access to the requested resource has been denied error message. If I access it through the jk connector from another host, http://IPADDRESS/manager/html/, I get no error message... From looking at the FAQ's and the Manager how-to, I've looked at the following: TOMCAT_ROOT/conf/Catalina/localhost/manager.xml: !-- Context configuration file for the Tomcat Manager Web App $Id: manager.xml,v 1.1.1.1 2002/07/18 16:48:14 remm Exp $ -- Context path=/manager docBase=../server/webapps/manager debug=0 privileged=true !-- Link to the user database we will get roles from -- ResourceLink name=users global=UserDatabase type=org.apache.catalina.UserDatabase/ /Context relevant section from httpd.conf LoadModule jk_module libexec/mod_jk.so AddModule mod_jk.c # Configure mod_jk # JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel info # Tomcat Virtual Host # VirtualHost 199.42.192.190:80 DocumentRoot /usr/local/apache/htdocs ServerName yoda.ddm.apm.bpm.eds.com JkMount /servlets-examples/* ajp13 JkMount /manager/* ajp13 /VirtualHost workers.properties worker.list= ajp13 worker.ajp13.host=yoda.ddm.apm.bpm.eds.com worker.ajp13.port=8009 worker.ajp13.type=ajp13 server.xml - I'm using the default server.xml bundled with tomcat 5.0.19 Thanks for any ideas... Greg - 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: JK2 configure thinks apache 2.0.48 is apache 1.3 on solaris 9
Nope, at least not in my install..
maul(grega):/usr/apache2 % find /usr/apache2 -name apxs
/usr/apache2/bin/apxs
maul(grega):/usr/apache2 %
Greg Adams wrote:
8. ./configure --with-apxs2=/usr/apache2/bin/apxs
Shouldn't this be /usr/apache2/sbin/apxs?
When I install Apache 2.0.49 in a custom dir of my choice, apxs goes
into
${PREFIX}/sbin/ directory.
Nix.
-
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: the pain of choice
Sad but true. Why DON'T the ant build files work? Did someone get lazy? Is JK2 part of a source tree that we're only getting a portion of when we download the source tarball? Great, let's use JK2 My experience: rant-mode tar -xvzf jakarta-tomcat-connectors-jk2-src-current.tar.gz cd jakarta-tomcat-connectors-jk2-2.0.4-src/ less README.txt - gibberish, doesn't help me much less RELEASE-NOTES.txt -- Tomcat Connectors Version @VERSION@ Release Notes This version matches the version included with tomcat-5.0.2, and supports tomcat 3.3, 4.0, 4.1, 5.0. Bugs and issues will be tracked with tomcat5 - this file will list only issues related with older versions. -- 5.0.2??? my confidence is growing. ls doc/* doc/install_tomcat33.html doc/install_tomcat40.html doc/install_tomcat41.html Hmmm, I want to install it for tomcat 5.0.19. Ok, I'll read the most current (install_tomcat41.html). Try it, it's quite amusing... Not helpful. ant Buildfile: build.xml build: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/build.xml:45: Basedir /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/util does not exist Total time: 1 second -- Ok, it can't find it's own files Great cd jk See if this works. ant -- Buildfile: build.xml detect: [echo] jakarta-tomcat-connectors prepare: BUILD FAILED file:/data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/jk/build.xml:142: Warning: Could not find file /data/michiel/jakarta-tomcat-connectors-jk2-2.0.4-src/coyote/build/lib/tomcat-coyote.jar to copy. Total time: 1 second -- lets read the README.txt blablabla Tomcat 4.1. No mention of Tomcat 5.x This feels like abandoned alpha software all the way, there is NO WAY I'm putting this on a production machine. /rant-mode Summary: if you package and distribute software like this, how on earth do you expect your users to build, let alone use it? Cheers, Michiel P.S. Compare this to the Tomcat release on UNIX: tar xvzf jakarta-tomcat-xxx.tgz cd jakarta-tomcat-xxx bin/startup.sh it works Angus Mezick wrote: Jk vs jk2. JK is dead STOP USING IT. JK2 all the way!! (sorry, jk2 is the prefered way to link apache2 to tomcat[45]) I would suggest using tomcat 4 for now if you are going immediately into a production environment where you have to abide by a server level agreement. Otherwise use tomcat 5. Tomcat 5 is listed as stable but seems a bit shakey right now with the bugs that keep popping up. There is no reason that I know of not to use Apache2. You will be using worker2.properties. Since I know nothing about JK I can't comment on the rest. -Original Message- From: C. Kukulies [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 5:33 PM To: [EMAIL PROTECTED] Subject: the pain of choice Can someone give me an advice which way to go WRT to using a tomcat/apache combo on a Unix (not Linux) system? There are so many options, jk, jk2, tomcat 3-4-5, apache 1.3, apache2. worker.properties worker2.properties, jk2.properties in tomcat/conf, mod_jk.conf in etc/apache, mod_jk, mod_jk2. Then I see constructs in brackets [] in worker.properties and without these. What is workers.host=jsp-hostname? Is it an IP host? Or is it some placeholder which must be in workers.list? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de - 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] -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.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: JK2 configure thinks apache 2.0.48 is apache 1.3 on solaris 9
I think I got it working now. I wasn't running configure as root... a
possibility I gathered from Chong's tomcat 5 for linux step-by-step:
http://cymulacrum.net/writings/tomcat5/book1.html
which is the best howto I've found yet... Bravo to Chong!
Greg
Nope, at least not in my install..
maul(grega):/usr/apache2 % find /usr/apache2 -name apxs
/usr/apache2/bin/apxs
maul(grega):/usr/apache2 %
Greg Adams wrote:
8. ./configure --with-apxs2=/usr/apache2/bin/apxs
Shouldn't this be /usr/apache2/sbin/apxs?
When I install Apache 2.0.49 in a custom dir of my choice, apxs goes
into
${PREFIX}/sbin/ directory.
Nix.
-
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]
JK2 configure thinks apache 2.0.48 is apache 1.3 on solaris 9
I'm having problems getting configure to run when trying to build the jk2 connector for apache 2.0.48 on solaris 9. The tomcat I'm running is 5.0.19. Here's a general list of what I've done... 1. Built apache 2.0.48 from source ./configure --prefix=/usr/apache2 --enable-so --enable-layout=Apache --enable-module=most --enable-mods-shared=most --enable-ssl make su -c make install 2. installed jdk 1.4.2_04 using instructions from http://java.sun.com - no problems there 3. installed jakarta-tomcat-5.0.19 which runs when using jsvc per the tomcat instructions. 4. downloaded jakarta-tomcat-connectors-jk2-src-current.tar.gz 5. gtar xzvf jakarta-tomcat-connectors-jk2-src-current.tar.gz 6. cd jakarta-tomcat-connectors-jk2-2.0.4-src/jk/native2 7. sh buildconf.sh - I get some errors about libtoolize and aclocal.m4 macro deprecation, but I read somewhere to ignore that. 8. ./configure --with-apxs2=/usr/apache2/bin/apxs Tail of output from configure: *** checking for cp... /bin/cp *** checking for mkdir... /bin/mkdir *** no apxs given *** need to check for Perl first, apxs depends on it... *** checking for perl... /bin/perl *** building connector for apache-2.0 *** checking checking for apache13.. not provided *** checking checking for apache20.. not provided *** checking checking for iis.. not provided *** checking checking for iPlanet.. not provided *** checking for tomcat33 location... not provided *** checking for tomcat40 location... not provided *** checking for tomcat41 location... not provided *** configure: error: Apache 1.3 requires apr to built from source, use --with-apr and --with-apr-util Why does configure say there was no apxs given? I gave it apxs2, didn't I? Why's it saying Apache 1.3 requires apr to build from source? I've got apache 2.0.48 installed, it must be incorrectly detecting it as 1.3 somehow. I've seen a few other posts like this but none had solutions. Is there some way to force it to recognize that I've got Apache 2 here?? Thanks very much in advance for any help you might give... Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
