@ -278,6 +278,11 @@
+Rainer Jung (rjung at apache.org)
+
+
+
+
Jan Luehe (luehe at apache.org)
Modified: tomcat/site/trunk/xdocs/whoweare.xml
URL:
http://svn.apache.org/viewcvs/tomcat/site/trunk/xdocs/whoweare.xml?rev=405811&r1=405810
-- Resent, because of mail setup problems during original commit --
Author: rjung
Date: Wed May 10 01:12:29 2006
New Revision: 405672
URL: http://svn.apache.org/viewcvs?rev=405672&view=rev
Log:
Remove unnecessary includes.
Small first commit to also test eol style etc.
Modified:
tomcat/conne
-- Resent, because of mail setup problems during original commit --
Author: rjung
Date: Wed May 10 01:41:48 2006
New Revision: 405677
URL: http://svn.apache.org/viewcvs?rev=405677&view=rev
Log:
Replace hard coded size of magic header by macro.
Compute size of shm using sizeof.
Modified:
tomc
Hi,
it's true, that jkstatus doesn't persist changes. There is no
functionality there to write a workers.properties (it's somewhere near
the end of the TODO).
Concerning disabled: Yes, disabled at the moment is an attribute
belonging to a worker and when using stickyness for any jvmRoute you
-grained, so you can specify the worker within the balancer - eg:
worker.adminloadbalancer.BLUFF.disabled=1
Presumably something like that is happening within jkstatus?
cheers,
David
x54680
|-+-------->
| | Raine
r, but will work for us.
I'll see, what I can do ...
Thanks. What kind of timeframe are we looking at?
cheers,
David
|-----+---->
| | Rainer Jung |
| | <[EMAIL PROTECTED]|
| | >|
|
It's a feature:
- disabled and stop attributes only work, when a worker is a balanced
worker of an lb
- if an lb has only one balanced worker, then disabled is not being
respected, because then every request would result in an error. Only if
you set the only worker to stop, it will get no re
Mladen Turk wants to add some small changes. After that we will do some
testing again and then release. Any input from your side about
intermediate test results on trunk will be highly appreciated.
Most important changes until now:
- fixed bug, that disabled workers never will leave error stat
+1
Rainer
Mark Thomas wrote:
That's 2 +1's and a +0. Any committer care to chip in with another +1
so I can go ahead with the beta release?
Cheers,
Mark
Peter Rossbach wrote:
[x ] +1 I am in favour of a 4.1.32-beta release
Great job :-)
peter
---
As there is no developer documentation: what are you trying to achieve?
mod_jk.c is the file that contains the apache specific code. To
understand it you will need to have some knowledge of the apache module API.
All web server plugins use shared code contained in the directory "common".
Rain
Hi Mladen,
Costins README.txt inside the sandbox already suggested:
===
Sandbox components should be developed in a sub-directory of the /tomcat/sandbox
directory. Developers may choose whether to add source directly under the
component's directory or to create the standard subversion /trunk/, /
I should have been more explicit: +1 for cleaning it up according to the
README :)
Mladen Turk schrieb:
Rainer Jung wrote:
Hi Mladen,
Costins README.txt inside the sandbox already suggested:
I know, I read the README, but the content inside does
not follow the README. That's the
[EMAIL PROTECTED] schrieb:
Author: mturk
Date: Sat Jun 24 03:44:34 2006
New Revision: 416897
URL: http://svn.apache.org/viewvc?rev=416897&view=rev
Log:
Instead calling time(NULL), use it as a function
parameter.
Modified: tomcat/connectors/trunk/jk/native/common/jk_lb_worker.c
@@ -283,32 +2
Hi Mladen,
In jk/native/common/jk_ajp_common.c: Are you able to convince me, that
this condition is correct:
2210 if (n > aw->ep_mincache_sz) {
2211 if (JK_IS_DEBUG_LEVEL(l)) {
2212 jk_log(l, JK_LOG_DEBUG,
2213
Thanks, I committed most of it (and some more). The only thing I left
unchanged is not escaping the Ampersand as a seperator between query
arguments.
Johan Bergström schrieb:
Hello dev-list.
I'm quite new to both tomcat and mod_jk.. really liking it so far!
Thought I could contribute back wit
[EMAIL PROTECTED] schrieb:
+if ((cnt - n) < aw->ep_mincache_sz) {
"<=" (lower or equals) instead of "<"?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I would like to start releasing mod_jk 1.2.16 this week.
Since our last release was done from CVS and there are several updates
to the tool chain (autoconf/automake/m4/libtool), there is some risk of
breaking the release (additionally to mod_jk code bugs).
For that reason I would propose t
I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the download.
Does anyone know about external references we might break?
Rainer
---
That's part of what I'll be doing.
Jean-frederic Clere schrieb:
Rainer Jung wrote:
I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the dow
repo.
Costin
On 6/28/06, Rainer Jung <[EMAIL PROTECTED]> wrote:
I think it's time to rename jakarta-tomcat-connectors to
tomcat-connectors. I'll try to handle the remaining jakarta-tomcat
artefacts inside the connectors module and concerning the download.
Does anyone know abou
Rainer Jung schrieb:
After releasing I would also love to change repos structure to make
deprecated code much more visible. More precisely: I would first like to
build consensus on what parts are deprecated.
Sorry: I meant "to make the deprecation much more vi
For tomcat6+ - I think the
> main issue is figuring where to put the native code so the duplicated
> java source trees don't confuse people. Given how much unused native
> we have, it may be good to just move mod_jk and whatever else is still
> used to tomcat6/ repo.
>
> Co
Maybe this
http://www.apache.org/dev/svn-eol-style.txt
will help?
Filip Hanik - Dev Lists schrieb:
gee, this is the second time this happened to me.
my IDE is set to preserve line endings, do I need to setup some
subversion property?
Filip
Jean-frederic Clere wrote:
Hi,
Try to prevent C
Hi,
version 1.2.16 of the Apache Tomcat mod_jk web server connector has been
tagged. This version contains numerous bug fixes and some new
improvements over our last release 1.2.15. Please test and share your
experience.
If no critical bugs will be found, we will have a formal release vote
starti
Hi,
version 1.2.16 of the Apache Tomcat mod_jk web server connector has been
tagged. This version contains numerous bug fixes and some new
improvements over our last release 1.2.15. Please test and share your
experience.
If no critical bugs will be found, we will have a formal release vote
starti
Hi,
as a reminder: I will summarize test feedback for mod_jk 1.2.16 late
friday, and provided positive test results the Apache Tomcat project
will proceed to vote on the final release. Until now only about 10
downloads happened, so we need more users to participate!
To ensure a quality release fo
I updated the README for 5.0.30 and 5.0.28 with a deprecation warning in
the style of 5.5. I also made the notice on the download page a little
more visible. It will take a couple of hours, before people.a.o
replicates it to the productive web server.
Thank's for the hint!
Rainer
Mladen Turk sch
Hi,
the tests for mod_jk 1.2.16 had a couple of results, unfortunately with
one bad regression bug:
1) The status worker (aka jkmanager) had a bug, which resulted in double
locking and hanging when a user tried to change the important attributed
"disabled" or "stopped" (and also for the new one "
Hi,
thanks to everyone who tested 1.2.16. Unfortunately we had one
regression bug in the status worker (hanging update request because of
double locking). For full results please see:
http://marc.theaimsgroup.com/?l=tomcat-dev&m=115234851210076&w=2
Today version 1.2.17 of the Apache Tomcat mod_j
klen_t *optlen);
>
>
> rclen should be socklen_t instead of unsigned int...
>
> With this iSeries build without problems...
>
>> 2006/7/12, Rainer Jung <[EMAIL PROTECTED]>:
>> Hi,
>>
>> thanks to everyone who tested 1.2.16. Unfortunately we had one
le more conciliant :)
>
> BTW, I think next major version of mod_jk (1.3 / 3.x ?) should use APR
> to be simpler and better integrated in Apache 2.x
>
>
> 2006/7/13, Rainer Jung <[EMAIL PROTECTED]>:
>> Hi Henri,
>>
>> thanks for reporting this. This has a
It's called once a minute (at least if a request comes in) to be able to
clean up things not directly related to the actual request, like closing
idle connections.
[EMAIL PROTECTED] schrieb:
> Hi,
>
> I'm currently working in mod_jk in order to add a particular mechanism, in
> this
> work I have
I think Mladen and I both want people to move to mod_proxy_*. Mladen
already offered help and httpd-dev for porting mod_jk improvements to
mod_proxy_* and I definitely want to join him in that. But first I need
to manage the pending mod_jk release, something we are right now doing.
I don't know mo
Hi Remy and Filip,
overwhelmed is much more correct than uncomfortable. I think looking at
how much work Filip has put into it since it's beginnings, it was good
to not immediately change the default implementation for TC 5.5 when
Filip started.
As Filip thinks it's ready for TC 6, I will happily
Hi Mladen,
would you mind putting it on
http://tomcat.apache.org/dev/dist/
first?
Many thanks for the Win-Builds!
Regards,
Rainer
Mladen Turk wrote:
Henri Gomez wrote:
What the status of mod_jk 1.2.17 ?
It would be usefull to get some binaries to help users check against
their platform,
Be careful:
I understand Henri problem report as getsockopt complaining about the
*last* argument. So it has been introduced between 1.2.15 and 1.2.16:
r386629 | pero | 2006-03-17 13:36:04 +0100 (Fri, 17 Mar 2006) | 1 lin
Mladen Turk wrote:
Anyhow, I suppose it should be neither int nor unsigned int,
but rather size_t, at least that's the retval from sizeof, right?
Of course its used by getsockopt that OTOH requires socklen_t.
Since it's only use is putting it into getsockopt(), I would suggest the
use of sockl
Then let Peter try it on Mac OS X, if he only gets a warning or a real
error.
Henri Gomez wrote:
Ok, build against the latest from SVN (thanks Mladen), and build
without any problem on iSeries.
A strong 1.2.18 candidate
2006/7/18, Mladen Turk <[EMAIL PROTECTED]>:
Henri Gomez wrote:
> Well o
at 10:44 AM, Henri Gomez wrote:
Good, so we're ready for a 1.2.18 release ?
2006/7/18, Jim Jagielski <[EMAIL PROTECTED]>:
On Jul 18, 2006, at 8:46 AM, Mladen Turk wrote:
> Rainer Jung wrote:
>> Then let Peter try it on Mac OS X, if he only gets a warning or a
>> real e
I'll care about that, since it looks like I'll do 1.2.18 now.
But I will only update documentation on tomcat.apache.org/dev. I'm
really thinking about rolling back the premature publication of newer
doc on tomcat.apache.org. I think, doc there should not be more recent,
than the last release. O
In
http://www.apache.org/dev/version-control.html
the ASF suggests:
Committers will need to properly configure their svn client. One
particular issue is OS-specific line-endings for text files. When you
add a new text file, especially when applying patches from Bugzilla,
first ensure that th
No, I think it's not:
1) This is not a regression, it was always implemented like that.
2) The recover feature is used in the load balancer and the first way of
avoiding errors is meant to be retries, the second way is failover. Only
then comes recovery.
3) A worker that goes into error stat
Mladen Turk wrote:
Rainer Jung wrote:
6) We could make the interval configurable, but there is a real danger
of users thinking, that a low recovery interval, like 10 seconds would
make things better, whereas it is very likely, that it would make
there whole system kind of oscillate
ween states. At least in most cases.
Mladen Turk wrote:
Rainer Jung wrote:
Mladen Turk wrote:
Anyhow, why would 60 second be optimal value?
It could as well be 90, 100, 180, etc...
Increasing is something totally different. I just want to avoid people
ending with a system that changes error/o
David Rees wrote:
While the change you made allows you to configure the worker to a
recover_time lower than 60 seconds, it doesn't let you change it to a
value lower than 60 using the status worker.
Still investigating, but it looks like there are a number of other
places it should be changed.
David Rees wrote:
Thanks that should work around my issue quite nicely. I'll check out
SVN and give a whirl (unless a new tag is to be rolled again shortly?)
Try 1.2.18.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Hi,
thanks to everyone who tested 1.2.17. We had one bug related to special
types used in the networking code. Furthermore there was one request for
enhancement we included in the next version 1.2.18.
Today this version 1.2.18 of the Apache Tomcat mod_jk web server
connector has been tagged.
To find out, why this is so: did you get the same VStudio complains for
1.2.16 or 17? I tought you built those?
I would suggest to just repack the zip, since there is no change in
repository and no official release yet.
Mladen Turk wrote:
Rainer Jung wrote:
Hi,
http://tomcat.apache.org/dev
- ./native/iis/installer/License.rtf
- ./native/iis/installer/isapi-redirector-win32-msi.ism
So we would need to maintain a list, which files need to be excluded in
the "-l". I think it ill be easier to rely on svn and keep the eol
information there.
Mladen Turk wrote:
Rainer Ju
h.
Rainer
Mladen Turk wrote:
Rainer Jung wrote:
To find out, why this is so: did you get the same VStudio complains
for 1.2.16 or 17? I tought you built those?
I would suggest to just repack the zip, since there is no change in
repository and no official release yet.
OK.
I have used your zi
The name associated with each worker must match the one used for the
jvmRoute attribute specified on the Engine element of the corresponding
node's server.xml.
It's not explicitely passed via AJP. You need to keep the names in
workers.properties/server.xml in sync by yourself.
Rainer
[EMAIL
Hi Mladen,
I wouldn't have known before, but
http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html
says:
Subversion's locking feature is currently limited to files only - it's
not yet possible to reserve access to a whole directory tree.
So I guess that's why you were able to get
I found it easy to delete via filtering for "svn lock" and "svn unlock".
It's different for the archives, but for them this traffic peak will not
be serious. The worst thing was, that mails got delayed by several hours.
I would prefer to keep svn commits on the dev list.
Yoav Shapira wrote:
Hello to all Tomcat project members,
after 2 unsuccessful release attempts for mod_jk it looks like 1.2.18
doesn't get any bug reports. All known bugs related to 1.2.16 and 1.2.17
have been fixed in 1.2.18. About 20 users downloaded 1.2.16 and 1.2.17
each, and 11 downloads happened for 1.2.18
release.
Thanks
On Mon, 2006-07-24 at 13:07 +0200, Peter Rossbach wrote:
Stable,
really cool community driven release. :-)
Peter
Am 24.07.2006 um 12:13 schrieb Mladen Turk:
Rainer Jung wrote:
Apache Tomcat Connectors 1.2.18 is:
[X] Stable - no major issues, no regressions
[ ] Beta - at
elease.
Thank's for your participation in the vote!
Rainer
Rainer Jung schrieb:
> Hello to all Tomcat project members,
>
> after 2 unsuccessful release attempts for mod_jk it looks like 1.2.18
> doesn't get any bug reports. All known bugs related to 1.2.16 and 1.2.17
&
Hi David,
David Rees schrieb:
> On 7/25/06, David Rees <[EMAIL PROTECTED]> wrote:
>> On 7/24/06, David Rees <[EMAIL PROTECTED]> wrote:
>> I spoke too soon. I've been testing 1.2.18 further, and recover time
>> while appearing to change, I can not get mod_jk to actually recover
>> any faster than 6
> Apache Tomcat Connectors 1.2.18 is:
> [X] Stable - no major issues, no regressions
> [ ] Beta - at least one significant issue -- tell us what it is
> [ ] Alpha - multiple significant issues -- tell us what they are
Rainer
-
T
The results of the vote are:
Stable: 6 votes (Mladen, Henri, Peter, Yoav, Jean-Frederic, Rainer)
Beta, Alpha: None.
I'm now going to move everything to the download area, updating docs,
updating cgi, mailing announcement ...
-
T
The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.18 of the Apache Tomcat mod_jk web server connector.
mod_jk is a connector which allows a web server such as Apache HTTPD
to act as a front end to the Tomcat web application server.
This version contains severa
mod_jk already uses shared memory, but since it should work for apache
1.3 and 2.0/2.2 it does not use apr. If your extensions are only meant
for 2.0/2.2, then have a look at apr:
http://apr.apache.org/docs/apr/modules.html
I'm not sure, that I understand your use case. Isn't Enhydra able to
incl
Klaus Wagner wrote:
...
4. the tricky part: have a) a watchdog that clears invalid sessions in
idle time or b) clear sessions before looking for them (causes some
performance issues)
If you really, really want to do this, for the watchdog you can enhance
the existing maintain methods. There i
Klaus Wagner wrote:
On Mon, 2006-08-14 at 16:24 +0200, Rainer Jung wrote:
Klaus Wagner wrote:
...
If you really, really want to do this, for the watchdog you can enhance
the existing maintain methods. There is already a mechanism that calls
the maintain methods during a request only if the
related with apache 2
> module programming)
>
> Thanks a lot !!!
>
>
> On 8/14/06, Rainer Jung <[EMAIL PROTECTED]> wrote:
>>
>> Klaus Wagner wrote:
>> > On Mon, 2006-08-14 at 16:24 +0200, Rainer Jung wrote:
>> >
>> >>Klaus Wa
I checked the whole thread, but I found no technical description of the
problem observed. So apart from discussing the uses and stability of any
do-not-reuse implementation, I would be interested in understanding the
real problem, which started the discussion.
- What is known about the TCP behavio
So I think the Tomcat problem with recent code is a non-issue. If anyone
has different experience please correct me.
Regards,
Rainer
Rainer Jung schrieb:
> I checked the whole thread, but I found no technical description of the
> problem observed. So apart from discussing the uses and st
Jim Jagielski schrieb:
> In a nutshell, there are many cases where Apache httpd and
> Tomcat are separated by a firewall, and, as such, there
> isn't a one-to-one direct connection. The firewall
> will close a connection but one side doesn't
> know about it.
I would call this a broken firewall, ri
laris it's not a problem, and the TC code and the Java API doc suggest
it's no problem on any platform.
Regards
Rainer
Filip Hanik - Dev Lists schrieb:
> Rainer Jung wrote:
>> Jim Jagielski schrieb:
>>
>>> In a nutshell, there are many cases where Apache httpd and
Klaus Wagner schrieb:
> Here my impressions of the situation from an serveradmin perspective.
>
> On Wed, 2006-08-23 at 17:08 +0200, Rainer Jung wrote:
>> I still don't have a consistent idea what happened around the firewall:
>>
>> - silently dropping is not expe
Hi Mladen,
Mladen Turk schrieb:
> Rainer Jung wrote:
>> I still don't have a consistent idea what happened around the firewall:
>>
>
> It is a very simple:
I don't think so, because no one was able to give the details. From a
"simple" perspective every
Mladen Turk schrieb:
>> The patch the Jim provided, gives us the functionality of turning off
>> the keep alive from the "clients" (httpd in this case) perspective.
>
> I do not agree, although its a hack and easy fix for
> the problem itself.
I would prefer the more useful 3 param connections/po
Hi all,
I plan to commit four more changes during the weekend. 2 of them are
already coded and running, the other 2 ones I still need to implement.
Most of the commits I did this week were only preparations for these
functionally bigger ones.
Already done but not committed:
- Passing back child
OK, so
- what's the show stopper: the rewrite windows things?
If yes, I would suggest to release this one patch without *any* of the
changes I did last week, because I hope, that this release would need no
changes.
Rainer
Mladen Turk schrieb:
> Rainer Jung wrote:
>>
>>
Hi all,
I applied some bigger changes to mod_jk. The result is available from
trunk, but also from
http://people.apache.org/~rjung/mod_jk-1.2.19-437488/
Under this URL you can also find the updated docs.
Since we need to decide, if we release Mladens Windows fixes from a
branch (not includi
This configure worked for previous version ;'(
2006/8/28, Henri Gomez <[EMAIL PROTECTED]>:
I'll make a build on our Linux PPC box and make some tests.
Stay tuned
BTW, a windows binary will be usefull also
2006/8/28, Rainer Jung < [EMAIL PROTECTED]>:
> Hi all,
>
&
Mladen Turk wrote:
Rainer,
can you make some tomcat-connectors-1.2.19-dev.tar.gz?
Regards,
Mladen.
Hi Mladen,
isn't that what's under
http://people.apache.org/~rjung/mod_jk-1.2.19-437488/
The numver is the subversion revision. The contents are 1.2.19-dev with
everything like in the release
Mladen Turk wrote:
You can put tarball inside your http://people.apache.org/~rjung/
It's much easier to handle tarball then doing svn co for each platform.
Somehow I don't get the problem: the tarball was already on
people.apache.org when I sent the original message. It's in the
directory I
If no one stops me, I'll do so at in 30 minutes :)
Henri Gomez schrieb:
> 2006/8/29, Mladen Turk <[EMAIL PROTECTED]>:
>>
>> Henri Gomez wrote:
>> >
>> > BTW, a windows binary will be usefull also
>> >
>>
>> http://people.apache.org/~mturk/jk1219/
>>
>> Done some bug fixes to be able to compile,
>>
Hi all,
Mladen and I applied some minor but partly important fixes. The result
is available from trunk, but also as a tarball from
http://people.apache.org/~rjung/mod_jk-1.2.19-438031/
Under this URL you can also find the docs (no changes form previous
quality check).
Feel free to send any obse
Hi Filip,
I can't give the correct recommendations, but explain the flag:
The flag tells the loader not to load the default thread library, but
instead another - usually older - one. Linux had incompatible changes in
it's thread implementation and since the distros bundle so much
software, they h
+1 (thanks for the nice comments on the recent connectors work) and +1
to Mladens Comments on the connector stuff.
Maybe you might like to add myself to the "diversifying release managers
part concerning tomcat-connectors.
Regards,
Rainer
Yoav Shapira schrieb:
> Hey,
> We need to submit a quart
I checked it, and tomcat-connectors-1.2.18-src.zip seems to have CRLF
line ends.
Alpha Huang schrieb:
> It has been a long time that mod_jk.dsp has unix line endings (LF) instead of
> win32's CRLF.
>
> I have to fix it every time when I use msdev to build it.
>
> Although many text editors could
at for 6.x, and Rainer Jung for the connectors.
Releases:
- mod_jk 1.2.17 and 1.2.18 were released. 1.2.18 is currently the
stable release (it was put out on July 20th). mod_jk 1.2.19 is in the
works, expected to release in the first half of September.
- Tomcat 4.1.34 was released in the first we
Yes, I'm willing and I've got time to cut a release during the weekend.
I'll put a HEAD tarball on people.apache.org during the next hour and
announce that on tomcat-dev, so that interesting parties have another
chance of giving it a quick try (since wwe've got again a lot of changes
since the
before we cut the release.
The release is being planned for tagging during saturday.
Regards,
Rainer
Rainer Jung wrote:
Yes, I'm willing and I've got time to cut a release during the weekend.
I'll put a HEAD tarball on people.apache.org during the next hour and
announce that on
hrieb Rainer Jung:
In preparation of release 1.2.19 of tomcat-connnectors (including
mod_jk) I made the actual HEAD of the code available for download and
testing under
http://people.apache.org/~rjung/mod_jk-1.2.19-442987/
This is not an official release, but another opportunity to give the
c
worker show state REC (cool)
I thing first report is a bootstrap problem, but I can find it :-)
regards
Peter
Am 13.09.2006 um 16:07 schrieb Rainer Jung:
In preparation of release 1.2.19 of tomcat-connnectors (including
mod_jk) I made the actual HEAD of the code available for download and
This is not a known feature.
Anything in the mod_jk log?
You mean "first hit" after restart, or after a time of inactivity?
Platform? Server version?
The new svn HEAD code gives the ability to log useful state info of the
LB in the access logs, so you can more easily find out, how often and
wh
Please open a Bugzilla for an enhancement request.
Thanks for pointing it out.
David Rees wrote:
On 9/14/06, Mladen Turk <[EMAIL PROTECTED]> wrote:
> So what do you do when you have multiple virtualhosts mapped to
> different workers?
Please don't split hair :)
In that case use the JkMount/J
Hi,
I'm going to tag tomcat-connectors 1.2.19 in around an hour. In case
anyone has a pending important commit, please let me know soon.
Regards,
Rainer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mai
Hi,
version 1.2.19 of the Apache Tomcat mod_jk web server connector has been
tagged. This version contains numerous bug fixes and some new
improvements over our last release 1.2.18. Please test and share your
experience. Your feedback helped us a lot during the previous release,
so we hope there w
Hi,
there is some information, that the JNI worker in mod_jk does not really
work (since a long time). So it looks like it is not being maintained
any more.
I would like to clarify things for future mod_jk releases:
- is there any information, that the JNI worker is still usable (for
which mod_j
Hi William,
which mod_jk version is this based on?
Where can I have a look at the code?
Regards,
Rainer
William L. Thomson Jr. wrote:
Your timing is perfect, not. I just added code to the mod_jk ebuild on
Gentoo to build and install the JNI stuff, yesterday. :( Although no one
requested it,
Getting a positive feedback from you ("it works!") will help :)
We plan starting the vote on thursday, so if we do not run in a blocker
the release should be official at the end of the week.
Regards,
Rainer
Peter Huber schrieb:
> Thanks for the quick response. Is there any release date fixed fo
If you are going to build it yourself, it will work with versions much
older than 2.0.54. I checked the change list for API changes of apache
and found nothing that's related to what mod_jk uses at least back until
2.0.41. I think 2.0.54 is pretty save.
But: If you are simply downloading provi
Hi,
I shortly want to remind everyone, that our release vote for mod_jk
1.2.19 will start tomorrow.
So all users still have some time to give us positive or negative
feedback on the release candidate. Until now, no issues have been found.
You can find 1.2.19 under:
http://tomcat.apache.org
Hello to all Tomcat project members,
mod_jk 1.2.19 has been available for testing for nearly 4 days now.
For those interested, these are the download numbers for the first three
days:
10 source/jk-1.2.19/tomcat-connectors-1.2.19-src.tar.gz
1 source/jk-1.2.19/tomcat-connectors-1.2.19-src.
Apache Tomcat Connectors 1.2.19 is:
[X] Stable - no major issues, no regressions
[ ] Beta - at least one significant issue -- tell us what it is
[ ] Alpha - multiple significant issues -- tell us what they are
Rainer
-
To unsub
The results of the vote are:
Stable: 4+1 votes (Mladen, Henri, Peter, Rainer and Jim mailed a +1
before the vote started)
Beta, Alpha: None.
I'm now going to move everything to the download area, updating docs,
updating cgi, mailing announcement ...
---
The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.19 of the Apache Tomcat mod_jk web server connector.
mod_jk is a connector which allows a web server such as Apache HTTPD
to act as a front end to the Tomcat web application server.
This version contains sever
301 - 400 of 2101 matches
Mail list logo
