Re: Tomcat 7. MX4J
On Thu, May 24, 2012 at 1:19 PM, Peter Roßbach p...@objektpark.de wrote:
HI Vadzim,
as you like a hot HTTP-JMX access use
http://www.jolokia.org/
chili...
Peter
Am 23.05.2012 um 00:06 schrieb Vadzim Mikhalenak:
On Wed, May 23, 2012 at 12:31 AM, Konstantin Kolinko
knst.koli...@gmail.com
wrote:
2012/5/22 Vadzim Mikhalenak vadzim.mikhale...@gmail.com:
Hello Christopher,
*
*
Thank you for the reply! Yes, link
http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html is for version
5.5
but we are migrating from version 6 (sorry for the confusion) but the
configuration above was valid for version 6
It works (or at least tries to start, to my surprise) in Tomcat 6 with
this particular AJP/1.3 connector implementation, but it is not
documented and not supported. Other connectors do not support those
attributes and this one was removed from Tomcat 7.
Tomcat 6 and 7 use JMX support provided by JRE and if you need http
access to it, the common way is to use JMXProxy servlet that is part
of the manager webapp.
It is all is documented
http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html
http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html#Using_the_JMX_Proxy_Servlet
or see the same docs for Tomcat 7.
Connector port=${AJP.PORT}
handler.list=mx
mx.enabled=true
mx.httpHost=${JMX.HOST}
mx.httpPort=${JMX.PORT}
protocol=AJP/1.3 /
*
*
and gave us opportunity to manage JMX beans using http://
${JMX.HOST}:${JMX.PORT} (please see
http://logback.qos.ch/manual/images/chapters/jmxConfigurator/mx4j_jetty.gif
)
In version 7 I couldn't see any possibility to do it.
I've noticed that in Connector class of version 6
if (AJP/1.3.equals(protocol)) {
setProtocolHandlerClassName
(org.apache.jk.server.JkCoyoteHandler);
org.apache.jk.server.JkCoyoteHandler used JkMain which used JkMX where
HttpAdapter from mx4j-tool.jar was used.
but in version 7
else if (AJP/1.3.equals(protocol)) {
setProtocolHandlerClassName
(org.apache.coyote.ajp.AjpAprProtocol);
So do we have possibility to manage JMX beans in version 7 as we could
in
version 6? (please see
http://logback.qos.ch/manual/images/chapters/jmxConfigurator/mx4j_jetty.gif
)
Please
1. Post your response below the text that you are replying to (aka do
not top-post)
2. Do not cross-post questions between users@ and dev@ lists.
This one belongs to users@.
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Hi,
Thanks for the reply.
I know about JMX Proxy Servlet but it was more preferable to use MX4J
page
and I thought there is simple way to configure it (as it was configured
in
6 version).
I'll be looking for solution to get mx4j page working.
Thanks again for your help!
Sorry for the trouble.
Best regards,
Vadim.
Hello Peter,
Thanks for the link. May be I'll try it soon :)
Best regards,
Vadim.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
After going to Tomcat 6 I get log4j problems. Why?
Hi, I have upgraded from Tomcat 5.5 to Tomcat 6.0.35 I am getting java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory I didn't have this problem before. Note that I have commons-logging already in my web apps WEB-INF\lib And this exception is from a class (custom class) running from a jar in %TOMCAT_HOME%\lib If I drop commons-logging in %TOMCAT_HOME%\lib the exception does not happen BUT now I get exceptions in log4j from inside my web app. I tried also deleting the commons-logging from %TOMCAT_HOME%\webapps\myApp\WEB-INF\lib but no success. Any idea what is the problem here?
Re: mod_jk not working !!
That's strange. It's working fine for many other people, on thousands of websites. Maybe it is your configuration that is not working ? is not working !! is about the best subject that can be imagined, if your intention was to not get any response at all. The only missing parts are capitals and the word URGENT. And if you believe that anyone is going to walk through the hundreds of lines of your configuration files, trying to figure out what you did wrong, then you have a surprise coming. You really need to read this : http://www.catb.org/~esr/faqs/smart-questions.html When you have read it, post another message to the list, with a better subject and the /relevant/ parts of your configuration, and maybe someone will feel like helping. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On Fri, May 25, 2012 at 6:45 AM, Mladen Turk mt...@apache.org wrote: On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? The question is, is this a recommendation or a restriction that should be enforced? Maybe a warning about this, apparently common, [mis-]configuration should be issued at module configuration time? Cheers Martin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/25/2012 11:28 AM, Martin Knoblauch wrote: On Fri, May 25, 2012 at 6:45 AM, Mladen Turkmt...@apache.org wrote: On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? The question is, is this a recommendation or a restriction that should be enforced? Maybe a warning about this, apparently common, [mis-]configuration should be issued at module configuration time? Hmm, I still didn't get the response if it works in case member workers are not in the worker.list. But you are right. Before 1.2.36 we just created another worker slot in shared memory. Now it's allocated 'by name' so it can create problems if the same name is declared both as standalone ajp13 worker and load balancer member. I'm sure that once we had 'must not be in worker.list', but someone changed that to 'should' inside http://tomcat.apache.org/connectors-doc/reference/workers.html (see balance_workers directive) Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: After going to Tomcat 6 I get log4j problems. Why?
2012/5/25 Hermes Flying flyingher...@yahoo.com: Hi, I have upgraded from Tomcat 5.5 to Tomcat 6.0.35 I am getting java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory I didn't have this problem before. Note that I have commons-logging already in my web apps WEB-INF\lib And this exception is from a class (custom class) running from a jar in %TOMCAT_HOME%\lib If I drop commons-logging in %TOMCAT_HOME%\lib the exception does not happen BUT now I get exceptions in log4j from inside my web app. I tried also deleting the commons-logging from %TOMCAT_HOME%\webapps\myApp\WEB-INF\lib but no success. Any idea what is the problem here? Your description is too generic to say. You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. See 1) Class Loading page in documentation. Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. I'd suspect that one of them is the culprit. 2) Logging page in documentation. Compare it with your configuration. It might be that you config matches some of the steps for enabling log4j described there, but not all of them. Note that using log4j in Tomcat is not the default configuration. 3) Apache Commons Logging documentation http://commons.apache.org/logging/guide.html Especially how commons-logging switches between java.util.logging and log4j (preferring the latter if it is available). Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: After going to Tomcat 6 I get log4j problems. Why?
On 25/05/2012 10:03, Hermes Flying wrote: Hi, I have upgraded from Tomcat 5.5 to Tomcat 6.0.35 I am getting java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory I didn't have this problem before. Note that I have commons-logging already in my web apps WEB-INF\lib And this exception is from a class (custom class) running from a jar in %TOMCAT_HOME%\lib If I drop commons-logging in %TOMCAT_HOME%\lib the exception does not happen BUT now I get exceptions in log4j from inside my web app. I tried also deleting the commons-logging from %TOMCAT_HOME%\webapps\myApp\WEB-INF\lib but no success. Any idea what is the problem here? Please start a new thread, rather than hijacking an existing thread, by editing a subject/body. p -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: jk 1.2.36 throwing 503/sendfull/cping errors
On Fri, May 25, 2012 at 1:29 PM, Mladen Turk mt...@apache.org wrote: On 05/25/2012 11:28 AM, Martin Knoblauch wrote: On Fri, May 25, 2012 at 6:45 AM, Mladen Turkmt...@apache.org wrote: On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? The question is, is this a recommendation or a restriction that should be enforced? Maybe a warning about this, apparently common, [mis-]configuration should be issued at module configuration time? Hmm, I still didn't get the response if it works in case member workers are not in the worker.list. I'm not the OP, although I believe he wrote so. But you are right. Before 1.2.36 we just created another worker slot in shared memory. Now it's allocated 'by name' so it can create problems if the same name is declared both as standalone ajp13 worker and load balancer member. This would explain the changed behaviour. As I said, if this is a non-no with 1.2.36+, there should be a watning in the logs, or an outright refusal to load. I'm sure that once we had 'must not be in worker.list', but someone changed that to 'should' inside http://tomcat.apache.org/connectors-doc/reference/workers.html (see balance_workers directive) Probably needs to be changed back, or a strong warning added. Cheers Martin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
On 05/24/2012 09:40 PM, Anthony J. Biacco wrote: I'm still puzzled as to why this behavior just changed between .35 and .36 OK, but if you follow the recommended configuration by making sure that workers which are members of lb are not listed inside worker.list, does it works? If I take the worker out of the worker list, then the loadbalancer works. But then accessing the worker by itself it doesn't. It seems to be based on the worker.list ordering Here's the behavior: worker.list=jkstatus,app-03,loadbalancer loadbalancer: does NOT work (503) app-03: works worker.list=jkstatus,loadbalancer,app-03 loadbalancer: works app-03: does NOT work (503) worker.list=jkstatus,loadbalancer loadbalancer: works app-03: does NOT work (500) -Tony - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
I'm sure that once we had 'must not be in worker.list', but someone changed that to 'should' inside http://tomcat.apache.org/connectors-doc/reference/workers.html (see balance_workers directive) Probably needs to be changed back, or a strong warning added. And that's ok, if I need to change my config, then that's no problem. It does make it more complicated for me, but I don't care enough to gripe about it. :) I was just going by how I read the docs, so didn't know if it was a desired change or a bug. -Tony - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk not working !!
From: Aman Arora aman.arora...@gmail.com To: users@tomcat.apache.org Sent: Thursday, May 24, 2012 10:25 PM Subject: mod_jk not working !! m trying to do a setup of tomcat clustering in which one tomcat is on port 8080 and other one is on 8081. i have downloaded the tomcat-connector in the modules folder of my apache.i built it using build-unix.sh by downloading the script from net as it was nt already there in the downloaded tomcat-connector. it buit mod_jk.so which i have placed inside modules folder as /usr/local/apache2/modules/mod_jk.so then i created workers.properties file and gave the description of workers there .and included it in httpd.cong file . still when i type http://localhost/jsp-pages which are in my webapps / it is not passing requast to tomcat which is holding the js pages. you may hav a look at the conf files to get a better fel of the problem ! the link is http://www.coderanch.com/t/581294/Tomcat/Tomcat-Clustering#2648034 OK, I've taken a brief look at your configuration files (httpd.conf, mod_jk.conf, server.xml, workers.properties). I've also taken a brief look at the Safari Books link you gave. As Andre said (sorry about the lack of accent, Andre), people are going to be a bit reluctant to wade through all of that material and provide pointers. Also as Andre has said, clustering Tomcat on the same machine works fine for many people. I routinely use a 3 or 4 node cluster as a test platform. I'll try to give a few general directions. As is my usual practice, this is going to be long. You have been warned. General thoughts In your Code Ranch postings, you state that you are new to Linux. Getting clustering to work on Linux involves Apache HTTPD configuration, Tomcat configuration, and Linux configuration. If this is your first time doing all of this, it's probably best to get a simple mod_jk connection working first. At each stage of the setup, I recommend testing and coming back to the mailing list with simple questions and the relevant portion(s) of the configuration file(s). Also, be prepared to do at least as much work as those people trying to help. Remember, this is a volunteer list, and we contribute in our spare time. Also, as another aside . . . there is a lot of misleading, incomplete, and just flat wrong information concerning Tomcat floating around on the 'net. The authoritative source for information is always: http://tomcat.apache.org/ The mailing list for questions is this mailing list. We try to give accurate information, and some people here have been working with Tomcat for a very long time. You might get accurate information elsewhere, but from what I've seen this is not very likely. Linux in General You'll find that Linux is a different beast than Windows (even Windows 7). In particular file permissions, file ownerships, and SELinux present quite a different security model than the typical Windows installation. It's best to be aware of this from the start. Purpose === What is the purpose of this setup? If you're running a pseudo-production development platform, then what you're setting up may be reasonable. If you're setting up a development platform with NetBeans or Eclipse, then you will run into a lot of file access problems with your setup. If you're setting up a development system, I recommend just creating a directory in your home directory to hold a single Tomcat, unpack Tomcat 7.0.27 in that directory, edit $CATALINA_HOME/conf/tomcat-users.xml per the instructions, and then use that installation. http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access Once it's running and you can access the manager application, then associate the installation with your IDE. Now you can develop, debug, test, and deploy without running into permission issues. If you're setting up a pseudo-production environment, then it's probably a good idea to set up a service account, install (and control) all Tomcats from that account, and connect those Tomcats to Apache HTTPD (or not). Note that since this is a separate account, this is a bit less convenient for development. Apache HTTPD I noticed that you have a lot of /usr/local based directories in your Apache HTTPD configuration. This is quite unusual for Linux, since most (all?) Linux distributions package Apache HTTPD. Rather than building your own Apache HTTPD, I recommend that you get and install the distribution package for Apache HTTPD. This will place files in line with the rest of your system, and it will also have a serviceable default configuration. On Fedora, the Apache HTTPD packages include: apr apr-util apr-devel apr-util-devel httpd httpd-devel httpd-tools The -devel packages are very important, since you will be building mod_jk from source. Java I from your messages that you have Oracle's Java installed. Make sure
Re: mod_jk not working !!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aman, On 5/25/12 1:25 AM, Aman Arora wrote: I'm trying to do a setup of tomcat clustering in which one tomcat is on port 8080 and other one is on 8081. Sounds reasonable. i have downloaded the tomcat-connector in the modules folder of my apache.i built it using build-unix.sh by downloading the script from net as it was nt already there in the downloaded tomcat-connector. What is build-unix.sh and why did you have to download it from [the] net? Other than apxs (which implies you have the httpd dev tools available), you don't need anything else to build mod_jk for your environment. Read the README.txt file in the root of the tarball and follow the directions. it buit mod_jk.so That's good. Since I don't know what build-unix.sh does, I'm happy it didn't delete your kernel. which i have placed inside modules folder as /usr/local/apache2/modules/mod_jk.so then i created workers.properties file and gave the description of workers there What's in there (see below)? .and included it in httpd.cong file . How? still when i type http://localhost/jsp-pages which are in my webapps / it is not passing requast to tomcat which is holding the js pages. What do you get in the response instead? you may hav a look at the conf files to get a better fel of the problem ! the link is http://www.coderanch.com/t/581294/Tomcat/Tomcat-Clustering#2648034 So I have to follow one link to get to 4 other links? For those less-willing to put up with this kind of crap, here's the important part of httpd.conf: Include /usr/local/apache2/conf/mod_jk.conf (*Not inside a VirtualHost definition*) Here's the mod_jk.conf: LoadModule jk_module /usr/local/apache2/modules/mod_jk.so JkWorkersFile /usr/local/apache2/conf/workers.properties JkLogFile /usr/local/apache2/logs/mod_jk.log JkLogLevel info #JkMount /sample/* loadbalancer #JkMount /* loadbalancer JkMount /examples/*.jsp default And finally, here's the workers.properties: workers.tomcat_home=/usr/local/tomcat/apache-tomcat-7.0.27/ workers.java_home=/usr/java/jdk1.7.0_04/ ps=/ worker.list=tomcatnode1, tomcatnode2, loadbalancer worker.tomcatnode1.port=8009 worker.tomcatnode1.host=localhost worker.tomcatnode1.type=ajp13 worker.tomcatnode1.lbfactor=1 worker.tomcatnode2.port=8010 worker.tomcatnode2.host=localhost worker.tomcatnode2.type=ajp13 worker.tomcatnode2.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=tomcatnode1, tomcatnode2 worker.loadbalancer.sticky_session=1 So, I can see a bunch of problems. Let's start at the top. 1. You put your JkMount directives in your mod_jk.conf file, which is included in your the top-level httpd.conf file. Your JkMounts will not be copied into your VirtualHosts and so you essentially have no mappings at all. 2. You are mapping /examples/*.jsp and trying to access /jsp-pages, so that's not going to work. 3. You are mapping /examples/*.jsp to the default worker, which has not been defined. 4. You have an old mod_jk config that contains these irrelevant settings: workers.tomcat_home, workers.java_home, ps 5. You have defined your 2 node workers to be on ports 8009 and 8010 but you said that you have your Tomcats running on 8080 and 8081. Perhaps you have AJP/1.3 connectors defined for 8009 and 8010 but I'm not going to enter /yet another/ CAPTCHA just to see your configuration files which I'm sure are completely full of comments and other crap I don't feel like reading. I suspect that #1, #2, and #3 are your real problems. Fix those and try again. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tQIACgkQ9CaO5/Lv0PAqXQCeLCHjYQAtRJH8FQ78+x9e0xf4 v1gAoJLdYNCS/HErJbQr2bm47AUYSczC =y+SX -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk not working !!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 5/25/12 12:26 PM, Mark Eggers wrote: . . . just my three cents (since this is long) More like twelve bucks: you should send this guy a bill for the message you just put together for him. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tT4ACgkQ9CaO5/Lv0PDYhQCcDgYU8IJzIwqd0toPoJPk+UMK 5lEAoJbcKTc3l4wl9UWBLyOVd9qhaczv =Ly2T -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony, On 5/25/12 12:07 PM, Anthony J. Biacco wrote: If I take the worker out of the worker list, then the loadbalancer works. But then accessing the worker by itself it doesn't. It seems to be based on the worker.list ordering Here's the behavior: worker.list=jkstatus,app-03,loadbalancer loadbalancer: does NOT work (503) app-03: works worker.list=jkstatus,loadbalancer,app-03 loadbalancer: works app-03: does NOT work (503) worker.list=jkstatus,loadbalancer loadbalancer: works app-03: does NOT work (500) What if you remove the jkstatus worker? What if you put jkstatus at the end of the list? I know we're grasping at straws, but you are not the only one who has this problem: 0.0.0.0 is showing up in a few places and we need to track it down. Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tfQACgkQ9CaO5/Lv0PDFJQCfSkC5uWQG4iqJ84XOpNp3KV7I U5oAniHDeVa5mFQ4tv3s9Wnj8qcOFrmp =lAcB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: mod_jk not working !!
From: Mark Eggers [mailto:its_toas...@yahoo.com] Subject: Re: mod_jk not working !! I'll try to give a few general directions. much useful content snipped Again, start simply. 1. Stock Apache HTTPD installation (and verify) 2. Stock Apache Tomcat installation (and verify) 3. mod_jk installation (and verify) 4. Second Apache Tomcat installation (and verify both) 5. Cluster I'd suggest that your entire e-mail should be put in the Wiki. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: jk 1.2.36 throwing 503/sendfull/cping errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony, On 5/25/12 12:07 PM, Anthony J. Biacco wrote: worker.list=jkstatus,app-03,loadbalancer loadbalancer: does NOT work (503) app-03: works worker.list=jkstatus,loadbalancer,app-03 loadbalancer: works app-03: does NOT work (503) worker.list=jkstatus,loadbalancer loadbalancer: works app-03: does NOT work (500) I can confirm that load-balancing works properly in my environment[1] with this workers.properties: worker.list=jk-status worker.jk-status.type=status # Template worker worker.template.type=ajp13 worker.template.host=localhost worker.template.connection_pool_timeout=60 worker.template.socket_timeout=300 worker.template.max_packet_size=65536 worker.list=crazy-lb worker.crazy-lb.type=lb worker.crazy-lb.balance_workers=worker23,worker03 worker.list=worker01 worker.worker01.reference=worker.template worker.worker01.port=8015 [more workers defined in exactly the same way] All worked as well as I expected (see below). - -chris [1] Environment: Debian Linux kernel 2.6.32 x86_64 Apache httpd 2.2.16-6 mod_jk 1.2.36 (just built it myself against httpd 2.2.16-6) Oracle Java 1.6.0_26-b03 (though not terribly relevant) Tomcat 7.0.27 and Tomcat 6.0.35 (I balanced two different TC versions and two different webapps... the results were not pretty but proved that mod_jk was working properly) -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/udIACgkQ9CaO5/Lv0PAH1gCfd6Dqc3IoLUQzQTN0zFnINpko K+YAoMBkcEwxJP5tKhYG87I9XdFoChML =/OIp -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk not working !!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 5/25/12 12:41 PM, Caldarale, Charles R wrote: From: Mark Eggers [mailto:its_toas...@yahoo.com] Subject: Re: mod_jk not working !! I'll try to give a few general directions. much useful content snipped Again, start simply. 1. Stock Apache HTTPD installation (and verify) 2. Stock Apache Tomcat installation (and verify) 3. mod_jk installation (and verify) 4. Second Apache Tomcat installation (and verify both) 5. Cluster I'd suggest that your entire e-mail should be put in the Wiki. +1, though maybe in smaller pieces linked by a top-level page. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/ufQACgkQ9CaO5/Lv0PBvzQCeM/ugajKLsv3od//91wc3WcKP /X4AoJztvRXa1d6lMYdHSbPiiT5WDPIF =nBVy -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
What if you remove the jkstatus worker? worker.list=app-03,loadbalancer app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03 app-03: does NOT work (503) loadbalancer: works What if you put jkstatus at the end of the list? worker.list=app-03,loadbalancer,jkstatus app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03,jkstatus app-03: does NOT work (503) loadbalancer: works -Tony Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tfQACgkQ9CaO5/Lv0PDFJQCfSkC5uWQG4iqJ84XOpNp3K V7I U5oAniHDeVa5mFQ4tv3s9Wnj8qcOFrmp =lAcB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: jk 1.2.36 throwing 503/sendfull/cping errors
GOOD loadbalancer (loadbalancer,app-03) [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_worker_for_name::jk_worker.c (115): found a worker loadbalancer [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_name_for_type::jk_worker.c (292): Found worker type 'lb' [Fri May 25 12:01:20 2012] [25030:1105992000] [debug] service::jk_lb_worker.c (1248): service worker=app-03 route=app-03 [Fri May 25 12:01:20 2012] [25030:1105992000] [info] service::jk_lb_worker.c (1254): FD: IP is 127.0.0.1 BAD loadbalancer (app-03,loadbalancer) [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_worker_for_name::jk_worker.c (115): found a worker loadbalancer [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] wc_get_name_for_type::jk_worker.c (292): Found worker type 'lb' [Fri May 25 11:52:52 2012] [24754:1138370880] [debug] service::jk_lb_worker.c (1248): service worker=app-03 route=app-03 [Fri May 25 11:52:52 2012] [24754:1138370880] [info] service::jk_lb_worker.c (1254): FD: IP is 0.0.0.0 I'm getting the IP using inet_ntoa on the worker_inet_addr In both GOOD and BAD scenarios, jk_resolve has the right IP for the app-03 every time. So it's somewhere in between or right in jk_lb_worker.c -Tony --- Manager, IT Operations Format Dynamics, Inc. P: 303-228-7327 F: 303-228-7305 abia...@formatdynamics.com http://www.formatdynamics.com -Original Message- From: Anthony J. Biacco [mailto:abia...@formatdynamics.com] Sent: Friday, May 25, 2012 11:40 AM To: Tomcat Users List Subject: RE: jk 1.2.36 throwing 503/sendfull/cping errors What if you remove the jkstatus worker? worker.list=app-03,loadbalancer app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03 app-03: does NOT work (503) loadbalancer: works What if you put jkstatus at the end of the list? worker.list=app-03,loadbalancer,jkstatus app-03: works loadbalancer: does NOT work (503) worker.list=loadbalancer,app-03,jkstatus app-03: does NOT work (503) loadbalancer: works -Tony Thanks, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/tfQACgkQ9CaO5/Lv0PDFJQCfSkC5uWQG4iqJ84XOpNp3K V7I U5oAniHDeVa5mFQ4tv3s9Wnj8qcOFrmp =lAcB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk not working !!
From: Christopher Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Sent: Friday, May 25, 2012 9:57 AM Subject: Re: mod_jk not working !! -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 5/25/12 12:41 PM, Caldarale, Charles R wrote: From: Mark Eggers [mailto:its_toas...@yahoo.com] Subject: Re: mod_jk not working !! I'll try to give a few general directions. much useful content snipped Again, start simply. 1. Stock Apache HTTPD installation (and verify) 2. Stock Apache Tomcat installation (and verify) 3. mod_jk installation (and verify) 4. Second Apache Tomcat installation (and verify both) 5. Cluster I'd suggest that your entire e-mail should be put in the Wiki. +1, though maybe in smaller pieces linked by a top-level page. - -chris If this goes up on the Wiki, then smaller pages organized by task would be good. It would probably help if the Wiki pages had a lot of detail, and cross-reference the appropriate documentation on the Tomcat web site as well. I've been meaning to write this up for some time, so maybe I'll get started on it this weekend. Since this is going to take a bit of time, is there a place on the Tomcat Wiki that I can write but not have it published (may be a developer list question). If not, then I'll write locally and then do a cut / paste. However, it would be nice to have feedback during the writing process. /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mod_jk not working !!
On 25 May 2012, at 19:21, Mark Eggers its_toas...@yahoo.com wrote: From: Christopher Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Sent: Friday, May 25, 2012 9:57 AM Subject: Re: mod_jk not working !! -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chuck, On 5/25/12 12:41 PM, Caldarale, Charles R wrote: From: Mark Eggers [mailto:its_toas...@yahoo.com] Subject: Re: mod_jk not working !! I'll try to give a few general directions. much useful content snipped Again, start simply. 1. Stock Apache HTTPD installation (and verify) 2. Stock Apache Tomcat installation (and verify) 3. mod_jk installation (and verify) 4. Second Apache Tomcat installation (and verify both) 5. Cluster I'd suggest that your entire e-mail should be put in the Wiki. +1, though maybe in smaller pieces linked by a top-level page. - -chris If this goes up on the Wiki, then smaller pages organized by task would be good. It would probably help if the Wiki pages had a lot of detail, and cross-reference the appropriate documentation on the Tomcat web site as well. I've been meaning to write this up for some time, so maybe I'll get started on it this weekend. Since this is going to take a bit of time, is there a place on the Tomcat Wiki that I can write but not have it published (may be a developer list question). If not, then I'll write locally and then do a cut / paste. However, it would be nice to have feedback during the writing process. It's coherent. Just put it up, worry about the tweaking later. p /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
CATALINA_BASE and CATALINA_HOME deployment
I'm trying to convert my app to use the preferred catalina base and home deployment. I understand that this allows for easier migration between tomcat versions, etc. As a point of reference, I'm reading about how to do this in Tomcat: The Definitive Guide. Also, I'm dealing with 5.5.35, if that matters. I have one question. I understand that the separation of the core tomcat stuff from my instance stuff is good. But the book says to copy the entire conf folder over to my instance folder ( CATALINA_BASE/myapp/conf ). Isn't this copying a bunch of tomcat version specific stuff that I'll have to sift through when it's time to migrate? Will I be able to just upgrade CATALINA_HOME and not upgrade all of that copied conf stuff as well? Thanks, Chad
Re: CATALINA_BASE and CATALINA_HOME deployment
chad.da...@emc.com wrote: I'm trying to convert my app to use the preferred catalina base and home deployment. I understand that this allows for easier migration between tomcat versions, etc. Maybe that is a slight misconception. I think that the separation between catalina_base and catalina_home is /mainly/ directed at allowing someone to run multiple tomcat instances on the same host, with different configurations, but sharing the same (tomcat) code. As a point of reference, I'm reading about how to do this in Tomcat: The Definitive Guide. That may be ok, but why not use the online tomcat documentation ? Last time I looked - and with the exception of the part about logging ;-) - it was quite comprehensible. Also, I'm dealing with 5.5.35, if that matters. Well yes. Why choose an old version that will soon become obsolete (or at least unsupported) ? The current version is 7.0, and the version before that was 6.0. If you are going to make this effort, do it with the latest released version. It will last longer. I have one question. I understand that the separation of the core tomcat stuff from my instance stuff is good. But the book says to copy the entire conf folder over to my instance folder ( CATALINA_BASE/myapp/conf ). That's a strange-sounding location. Maybe you are confused about the term instance ? It means an instance of tomcat, not of your application. The correct folder is catalina_base/conf. The default location for applications running under that separate tomcat instance would be catalina_base/webapps/, with your apps below that one (like catalina_base/webapps/myapp). Isn't this copying a bunch of tomcat version specific stuff that I'll have to sift through when it's time to migrate? Will I be able to just upgrade CATALINA_HOME and not upgrade all of that copied conf stuff as well? Definitely not. The files in the conf folder are quite likely to change between versions (old tags being retired, new tags being added, attributes changing in tags, etc..). The recommended practice when you ugrade to another version is to install a vanilla new version in a new directory, with the vanilla conf files of that new version. Then check that it is working. And then, bring over your modifications to the old vanilla version, into these new conf files, one by one and carefully, consulting the docs at every step to see what's changed. Then when it all works with the new version, remove the old one. Under the catalina_home/catalina_base directory (by default they are the same), there have been (and will be) changes between versions, such as some sub-directories disappearing or being renamed, other ones added, and some stuff that used to be in one place being moved to another. If you try to keep the same directory structure and the same conf files between versions, you are looking for trouble. Note: I am talking about upgrading between major versions, like from tomcat 5.5.x to tomcat 6.0.x, or from 6.0.x to 7.0.x. If you are talking about upgrading from 7.0.x to 7.0.y, then things are a bit different. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: CATALINA_BASE and CATALINA_HOME deployment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chad, On 5/25/12 3:31 PM, chad.da...@emc.com wrote: I'm trying to convert my app to use the preferred catalina base and home deployment. I dunno about /preferred/, but it certainly is flexible. I understand that this allows for easier migration between tomcat versions, etc. Absolutely! As a point of reference, I'm reading about how to do this in Tomcat: The Definitive Guide. Also, I'm dealing with 5.5.35, if that matters. CATALINA_BASE and CATALINA_HOME have worked (roughly) the same way since at least as far back as Tomcat 4.1. I have one question. I understand that the separation of the core tomcat stuff from my instance stuff is good. But the book says to copy the entire conf folder over to my instance folder ( CATALINA_BASE/myapp/conf ). Isn't this copying a bunch of tomcat version specific stuff that I'll have to sift through when it's time to migrate? Yes and no. First, you *must* have a separate conf/server.xml file otherwise all your instances will conflict with their port numbers, etc. Same thing with conf/tomcat-users.xml -- that would be a security issue to share that configuration. Technically, you can leave catalina.policy, catalina.properties, context.xml, and logging.properties in CATALINA_HOME/conf and Tomcat will pick them up. You'll have to check, but you may be able to leave web.xml out of CATALINA_BASE/conf and Tomcat will pick-up the one from CATALINA_HOME/conf. Will I be able to just upgrade CATALINA_HOME and not upgrade all of that copied conf stuff as well? When upgrading between major versions of Tomcat (say, 5.5 - 7.0 which you should do at your earliest possible convenience), you *will* have to ditch your server.xml. You will also have to replace your conf/web.xml file with the one that comes with the version of Tomcat that you are using. I think everything else left over (assuming you have left out catalina.policy, etc. as I described above) then you should be good to go after a new server.xml has been installed. When I upgrade from one version to the next, I usually just do a diff of my server.xml and the one that is in CATALINA_HOME/conf of the version I'm /leaving/. Then, I get a fresh copy of server.xml from the *new* version of Tomcat, stick it in CATALINA_BASE/conf/ and apply basically the same changes to it. That way, I don't break things like logging, standard Listener configuration, etc. Hope that helps, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/670ACgkQ9CaO5/Lv0PD/GgCeLsr3wzQr0UOTUWphWCATwLFY gPgAoI2GZIcAqUR88oVPfJfM9ZvCV33E =x70f -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
After going to Tomcat 6 I get log4j problems. Why? (RE:)
Creating a new Thread as Pid recommended: Concerning the questions posed by Konstantin Kolinko: You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. I am not sure I follow: you mean the version? I have log4j in the WEB-INF\xml, and commons-logging and commons-logging-api as well No problem up to Tomcat 5.5. Does this answer your question? Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. The custom jar provides an SSLImplementation to be hooked in the connectors. When it tries to log I get exception. No problem in Tomcat 5.5. This exception goes away if I move commons-logging in %TOMCAT_HOME%\lib BUT then I have exceptions in my web application (even if I delete the commons-logging from WEB-INF\lib) Has something changed in the logging in Tomcat 6? How can I resolve this problems? Thank you! I'd suspect that one of them is the culprit. 2012/5/25 Hermes Flying flyingher...@yahoo.com: Hi, I have upgraded from Tomcat 5.5 to Tomcat 6.0.35 I am getting java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory I didn't have this problem before. Note that I have commons-logging already in my web apps WEB-INF\lib And this exception is from a class (custom class) running from a jar in %TOMCAT_HOME%\lib If I drop commons-logging in %TOMCAT_HOME%\lib the exception does not happen BUT now I get exceptions in log4j from inside my web app. I tried also deleting the commons-logging from %TOMCAT_HOME%\webapps\myApp\WEB-INF\lib but no success. Any idea what is the problem here? Your description is too generic to say. You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. See 1) Class Loading page in documentation. Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. I'd suspect that one of them is the culprit. 2) Logging page in documentation. Compare it with your configuration. It might be that you config matches some of the steps for enabling log4j described there, but not all of them. Note that using log4j in Tomcat is not the default configuration. 3) Apache Commons Logging documentation http://commons.apache.org/logging/guide.html Especially how commons-logging switches between java.util.logging and log4j (preferring the latter if it is available). Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: After going to Tomcat 6 I get log4j problems. Why? (RE:)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hermes, A: Because it's hard to read. Q: Why shouldn't I top-post? - -chris On 5/25/12 4:40 PM, Hermes Flying wrote: Creating a new Thread as Pid recommended: Concerning the questions posed by Konstantin Kolinko: You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. I am not sure I follow: you mean the version? I have log4j in the WEB-INF\xml, and commons-logging and commons-logging-api as well No problem up to Tomcat 5.5. Does this answer your question? Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. The custom jar provides an SSLImplementation to be hooked in the connectors. When it tries to log I get exception. No problem in Tomcat 5.5. This exception goes away if I move commons-logging in %TOMCAT_HOME%\lib BUT then I have exceptions in my web application (even if I delete the commons-logging from WEB-INF\lib) Has something changed in the logging in Tomcat 6? How can I resolve this problems? Thank you! I'd suspect that one of them is the culprit. 2012/5/25 Hermes Flying flyingher...@yahoo.com: Hi, I have upgraded from Tomcat 5.5 to Tomcat 6.0.35 I am getting java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory I didn't have this problem before. Note that I have commons-logging already in my web apps WEB-INF\lib And this exception is from a class (custom class) running from a jar in %TOMCAT_HOME%\lib If I drop commons-logging in %TOMCAT_HOME%\lib the exception does not happen BUT now I get exceptions in log4j from inside my web app. I tried also deleting the commons-logging from %TOMCAT_HOME%\webapps\myApp\WEB-INF\lib but no success. Any idea what is the problem here? Your description is too generic to say. You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. See 1) Class Loading page in documentation. Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. I'd suspect that one of them is the culprit. 2) Logging page in documentation. Compare it with your configuration. It might be that you config matches some of the steps for enabling log4j described there, but not all of them. Note that using log4j in Tomcat is not the default configuration. 3) Apache Commons Logging documentation http://commons.apache.org/logging/guide.html Especially how commons-logging switches between java.util.logging and log4j (preferring the latter if it is available). Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+/73cACgkQ9CaO5/Lv0PBuFQCeM91SilAiWfhgXVeaHA5BDv1w P2QAoI9rggqqhrkgmoJLwM7XobIlDpCi =dbX/ -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: After going to Tomcat 6 I get log4j problems. Why? (RE:)
On 25/05/2012 21:40, Hermes Flying wrote: Creating a new Thread as Pid recommended: Concerning the questions posed by Konstantin Kolinko: You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. I am not sure I follow: you mean the version? I have log4j in the WEB-INF\xml, and commons-logging and commons-logging-api as well No problem up to Tomcat 5.5. Does this answer your question? Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. The custom jar provides an SSLImplementation to be hooked in the connectors. When it tries to log I get exception. No problem in Tomcat 5.5. This exception goes away if I move commons-logging in %TOMCAT_HOME%\lib BUT then I have exceptions in my web application (even if I delete the commons-logging from WEB-INF\lib) Has something changed in the logging in Tomcat 6? How can I resolve this problems? Thank you! I'd suspect that one of them is the culprit. 2012/5/25 Hermes Flying flyingher...@yahoo.com: Hi, I have upgraded from Tomcat 5.5 to Tomcat 6.0.35 I am getting java.lang.NoClassDefFoundError: org.apache.commons.logging.LogFactory I didn't have this problem before. Tomcat 5.5 != Tomcat 6.0 http://tomcat.apache.org/migration.html p Note that I have commons-logging already in my web apps WEB-INF\lib And this exception is from a class (custom class) running from a jar in %TOMCAT_HOME%\lib If I drop commons-logging in %TOMCAT_HOME%\lib the exception does not happen BUT now I get exceptions in log4j from inside my web app. I tried also deleting the commons-logging from %TOMCAT_HOME%\webapps\myApp\WEB-INF\lib but no success. Any idea what is the problem here? Your description is too generic to say. You do not say what jars are exactly where and what actual configuration (server.xml and logging) you have. See 1) Class Loading page in documentation. Placing custom jars into %TOMCAT_HOME%\lib is usually a bad idea. I'd suspect that one of them is the culprit. 2) Logging page in documentation. Compare it with your configuration. It might be that you config matches some of the steps for enabling log4j described there, but not all of them. Note that using log4j in Tomcat is not the default configuration. 3) Apache Commons Logging documentation http://commons.apache.org/logging/guide.html Especially how commons-logging switches between java.util.logging and log4j (preferring the latter if it is available). Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] signature.asc Description: OpenPGP digital signature
