<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user">
    <title>gmane.comp.jakarta.tomcat.user</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221963"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221962"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221961"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221960"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221959"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221958"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221957"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221956"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221955"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221954"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221953"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221952"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221951"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221950"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221949"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221948"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221947"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221946"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221945"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221943"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221963">
    <title>Re: After going to Tomcat 6 I get log4j problems. Why? (RE:)</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221963</link>
    <description>&lt;pre&gt;
Tomcat 5.5 != Tomcat 6.0

 http://tomcat.apache.org/migration.html


p



&lt;/pre&gt;</description>
    <dc:creator>Pid</dc:creator>
    <dc:date>2012-05-25T21:35:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221962">
    <title>Re: After going to Tomcat 6 I get log4j problems. Why? (RE:)</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221962</link>
    <description>&lt;pre&gt;-----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:
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;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-----
&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T20:45:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221961">
    <title>After going to Tomcat 6 I get log4j problems. Why? (RE:)</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221961</link>
    <description>&lt;pre&gt;Creating a new Thread as Pid recommended:
Concerning the questions posed by Konstantin Kolinko:
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?


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 &amp;lt;flyinghermes&amp;lt; at &amp;gt;yahoo.com&amp;gt;:

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 &lt;/pre&gt;</description>
    <dc:creator>Hermes Flying</dc:creator>
    <dc:date>2012-05-25T20:40:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221960">
    <title>Re: CATALINA_BASE and CATALINA_HOME deployment</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221960</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chad,

On 5/25/12 3:31 PM, Chad.Davis&amp;lt; at &amp;gt;emc.com wrote:

I dunno about /preferred/, but it certainly is flexible.


Absolutely!


CATALINA_BASE and CATALINA_HOME have worked (roughly) the same way
since at least as far back as Tomcat 4.1.


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.


When upgrading between major versions of Tomcat (say, 5.5 -&amp;gt; 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 y&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T20:29:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221959">
    <title>Re: CATALINA_BASE and CATALINA_HOME deployment</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221959</link>
    <description>&lt;pre&gt;
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.


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&lt;/pre&gt;</description>
    <dc:creator>André Warnier</dc:creator>
    <dc:date>2012-05-25T20:25:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221958">
    <title>CATALINA_BASE and CATALINA_HOME deployment</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221958</link>
    <description>&lt;pre&gt;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
&lt;/pre&gt;</description>
    <dc:creator>Chad.Davis&lt; at &gt;emc.com</dc:creator>
    <dc:date>2012-05-25T19:31:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221957">
    <title>Re: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221957</link>
    <description>&lt;pre&gt;

It's coherent. Just put it up, worry about the tweaking later.


p



&lt;/pre&gt;</description>
    <dc:creator>Pid *</dc:creator>
    <dc:date>2012-05-25T19:19:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221956">
    <title>Re: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221956</link>
    <description>&lt;pre&gt;

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/
&lt;/pre&gt;</description>
    <dc:creator>Mark Eggers</dc:creator>
    <dc:date>2012-05-25T18:21:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221955">
    <title>RE: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221955</link>
    <description>&lt;pre&gt;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.&lt;/pre&gt;</description>
    <dc:creator>Anthony J. Biacco</dc:creator>
    <dc:date>2012-05-25T18:11:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221954">
    <title>RE: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221954</link>
    <description>&lt;pre&gt;
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


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





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe&amp;lt; at &amp;gt;tomcat.apache.org
For additional commands, e-mail: users-help&amp;lt; at &amp;gt;tomcat.apache.org
&lt;/pre&gt;</description>
    <dc:creator>Anthony J. Biacco</dc:creator>
    <dc:date>2012-05-25T17:39:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221953">
    <title>Re: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221953</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 5/25/12 12:41 PM, Caldarale, Charles R wrote:

+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-----
&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T16:57:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221952">
    <title>Re: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221952</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tony,

On 5/25/12 12:07 PM, Anthony J. Biacco wrote:

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 di&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T16:56:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221951">
    <title>RE: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221951</link>
    <description>&lt;pre&gt;


&amp;lt;much useful content snipped&amp;gt;



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.
&lt;/pre&gt;</description>
    <dc:creator>Caldarale, Charles R</dc:creator>
    <dc:date>2012-05-25T16:41:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221950">
    <title>Re: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221950</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tony,

On 5/25/12 12:07 PM, Anthony J. Biacco wrote:

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-----
&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T16:40:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221949">
    <title>Re: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221949</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark,

On 5/25/12 12:26 PM, Mark Eggers wrote:

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-----
&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T16:37:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221948">
    <title>Re: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221948</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aman,

On 5/25/12 1:25 AM, Aman Arora wrote:

Sounds reasonable.


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.


That's good. Since I don't know what build-unix.sh does, I'm happy it
didn't delete your kernel.


What's in there (see below)?


How?


What do you get in the response instead?


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.&lt;/pre&gt;</description>
    <dc:creator>Christopher Schultz</dc:creator>
    <dc:date>2012-05-25T16:36:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221947">
    <title>Re: mod_jk not working !!</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221947</link>
    <description>&lt;pre&gt;
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&lt;/pre&gt;</description>
    <dc:creator>Mark Eggers</dc:creator>
    <dc:date>2012-05-25T16:26:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221946">
    <title>RE: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221946</link>
    <description>&lt;pre&gt;
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
&lt;/pre&gt;</description>
    <dc:creator>Anthony J. Biacco</dc:creator>
    <dc:date>2012-05-25T16:12:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221945">
    <title>RE: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221945</link>
    <description>&lt;pre&gt;and

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
&lt;/pre&gt;</description>
    <dc:creator>Anthony J. Biacco</dc:creator>
    <dc:date>2012-05-25T16:07:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221943">
    <title>Re: jk 1.2.36 throwing 503/sendfull/cping errors</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221943</link>
    <description>&lt;pre&gt;
 I'm not the OP, although I believe he wrote so.


 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.


 Probably needs to be changed back, or a strong warning added.

Cheers
Martin
&lt;/pre&gt;</description>
    <dc:creator>Martin Knoblauch</dc:creator>
    <dc:date>2012-05-25T13:31:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221942">
    <title>Re: After going to Tomcat 6 I get log4j problems. Why?</title>
    <link>http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/221942</link>
    <description>&lt;pre&gt;
Please start a new thread, rather than hijacking an existing thread, by
editing a subject/body.


p



&lt;/pre&gt;</description>
    <dc:creator>Pid</dc:creator>
    <dc:date>2012-05-25T12:30:34</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.jakarta.tomcat.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.jakarta.tomcat.user</link>
  </textinput>
</rdf:RDF>

