Guenter Knauf wrote:
Hi Mladen,
But that is exactly what we should *not* do.
Tomcat comes with it's native, so if you upgrade the
Tomcat, upgrade its native as well (if changed)
Like said, all that can be easy done by simply
extending requirements for building Tomcat release.
One will need
jean-frederic clere wrote:
Mark Thomas wrote:
jean-frederic clere wrote:
I think that is all working around the fact that tcnative is not
mandatory module for Tomcat and it is somehow independent from tomcat.
tcnative builds contain cryptosoftware (openssl) and that means they
may not be
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
Mark Thomas wrote:
jean-frederic clere wrote:
I think that is all working around the fact that tcnative is not
mandatory module for Tomcat and it is somehow independent from tomcat.
tcnative builds contain
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
Mark Thomas wrote:
jean-frederic clere wrote:
I think that is all working around the fact that tcnative is not
mandatory module for Tomcat and it is somehow independent
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
Hi,
I think that the tcnative releases should be independent from tomcat.
There are several reasons:
- The native code is in /tomcat/connectors/trunk/jni/native and it
checked out via links in tc trunk/6.0.x/5.5.x
jean-frederic clere wrote:
Hi,
I think that the tcnative releases should be independent from tomcat.
There are several reasons:
- The native code is in /tomcat/connectors/trunk/jni/native and it
checked out via links in tc trunk/6.0.x/5.5.x.
- The logic to have tcnative independent is already
Yoav Shapira wrote:
I'd vote the same given the new choice. I'm also willing to help with
putting docs up, etc.
Can we guys discuss this more before putting any vote?
Vote means we cannot make any consensus, so we need
to make a 'by majority rule' decision.
The whole discussion started less
Remy Maucherat wrote:
The native component can be used by many Tomcat releases, and has been
tagged and released independently. Of course, it is often done in sync
with Tomcat to introduce new APIs, but overall it's quite similar to
mod_jk releases.
But it's not even close to the mod_jk
Remy Maucherat wrote:
(for example, existing Tomcat
users will be able to take 1.1.12 and use it with older Tomcat releases
to fix a bug), so it would need a release vote and separate tagging.
Sure, the same can be done with commons-logging.jar from
any future version I suppose ;)
Anyhow,
Stacy Johnson (stacjohn) wrote:
I am working on a soon to be released product that is currently in a
bind as it requires a fix that has been implemented in tcnative-1.dll
(ver 1.1.12). Does anyone one know when this version will be released?
http://tomcat.heanet.ie/native/1.1.12/
Regards,
Stusynski, Dan wrote:
However, an IIS 7.0 compatible configuration script without the need to
enable optional modules and reboot the server would seem ideal.
I'll attend the Microsoft server 2008 compatibility lab
organized by Microsoft for ASF at the end of the February.
Guys that wrote
William A. Rowe, Jr. wrote:
Rainer Jung wrote:
- cleanup and prepare for each of the targets underneath or release.
Either way, since in the source tgz target there is already an exclude
list, I would prefer to update that exclude list and use the same one
whereever possible, so something
Haroon Rafique wrote:
Basically Mladen is saying that in case only the protocol is different
(and the vhost is the same as the parent) mod_jk should treat the
JkMounts as the same as if they were in the parent.
Right, this is one particular use case where we actually
have only the
According to the release process, the 6.0.16 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[x] Stable
Regards,
Mladen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
According to the release process, the 5.5.26 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable
Regards,
Mladen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jean-frederic clere wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Wed Apr 16 05:37:22 2008
New Revision: 648682
URL: http://svn.apache.org/viewvc?rev=648682view=rev
Log:
Add watchdog thread to Apache 2. It creates additional thread in child
process if set for unatended maintenance of
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Wed Apr 16 05:37:22 2008
New Revision: 648682
URL: http://svn.apache.org/viewvc?rev=648682view=rev
Log:
Add watchdog thread to Apache 2. It creates additional thread
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
Mladen Turk wrote:
jean-frederic clere wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Wed Apr 16 05:37:22 2008
New Revision: 648682
URL: http://svn.apache.org/viewvc?rev=648682view=rev
Log:
Add watchdog thread
Henri Gomez wrote:
Well Suse RPM provided an Apache 2.2.3 but with ap_mmm from 2.2.5.
It's pretty common on Linux Enterprise distributions to use a know
core (ie 2.2.3) and apply security patches from later (ie: 2.2.5).
IMHO that's incorrect.
You cannot change mmn unless you support what mmn
jean-frederic clere wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Thu May 29 11:08:20 2008
New Revision: 661428
URL: http://svn.apache.org/viewvc?rev=661428view=rev
Log:
Move the ttl as well when the socket is removed. Patch provided by
Alex Barclay
Cool but could you put the
jean-frederic clere wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Mon May 26 05:42:11 2008
New Revision: 660175
URL: http://svn.apache.org/viewvc?rev=660175view=rev
Log:
Fix 45071 by updating ttl for signaled but not removed sockets
Modified:
Mark Thomas wrote:
I've just attached a couple of patches to
https://issues.apache.org/bugzilla/show_bug.cgi?id=43327
One of the patches is a patch to native and since all I know just about
know enough C to be dangerous, I would be grateful if someone who
actually knows what they are doing
Hi,
Since all crypto software issues has been resolved
with US government we can ship openssl native binaries
directly instead using Irelands official mirror site.
Now, this also presumes that installer can directly
contain those .dll's instead downloading them at install
time. It's probably
Since all crypto software issues has been resolved
with US government we can ship openssl native binaries
directly instead using Irelands official mirror site.
I've put the binaries to
archive.apache.org/dist/tomcat/tomcat-connectors/native/
and (1.1.14 only) to
Henri Gomez wrote:
I've put the binaries to
archive.apache.org/dist/tomcat/tomcat-connectors/native/
and (1.1.14 only) to
www.apache.org/dist/tomcat/tomcat-connectors/native/
Not sure why but archive is not yet populated
(probably its some mirroring issue)
The heanet.ie site is still on and
Remy Maucherat wrote:
According to the release process, the 6.0.17 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[x] Stable
Regards
--
^(TM)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Remy Maucherat wrote:
The candidates binaries are available here:
http://people.apache.org/~remm/tomcat-6/v6.0.18/
According to the release process, the 6.0.18 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable
Regards
--
^(TM)
Hi,
Seems this year Tomcat has 10 year anniversary since
being part of ASF. I plan to create some artwork and
edit the heritage.html page, probably add few more.
It would be nice to list all the initial committers
on that page and get some more info on the history
from the early days.
If
Mark Thomas wrote:
Asf has a great server framework, mina, but it's not used by Tc.
I'm not sure building Tomcat on top of another framework is a good idea. If you
have a PoC that shows otherwise that would be very interesting.
Mina is also ASF and why not speak with the MINA team ?
May be
Henri Gomez wrote:
That's my wishes for Tomcat, not just code, bits and specs compliance,
but recreate a new wider commiters/contributors community.
It takes outreach to make that happen. Mark isn't offbase, keep posting
your wishes here, but if you want to make it happen, engage these other
Henri Gomez wrote:
I doubt you will get veto if this starts as module project
that can be used as drop-in component without changing the
overall API.
Under Tomcat umbrella we have now :
- a Servlet container
- an Apache/IIS connector (jk)
- a native connector
First guess, but I may be
Costin Manolache wrote:
+1 on removing from trunk.
IMHO AJP as a protocol is a dead end - it is not worth extending,
Agreed. It has to many limitations to satisfy the
modern webserver/backend connector.
and certainly not
worth creating a new protocol. We need to pick one of
Costin Manolache wrote:
and certainly not
worth creating a new protocol. We need to pick one of
thrift/protobuf/hessian for
marshaling, and start doing some mux-ing in the protocol.
All those framework you mention are just helpers for
*building* the custom protocol. They actually mandate
Costin Manolache wrote:
So in essence you have a new protocol but the sole
difference is how you describe it.
The API can be something like:
- legacyRequest(RequestMessage) - whatever we have in the current AJP
protocol
- getServerLoad() and whatever new we wanted to add
Instead of defining
David Jencks wrote:
I don't really know what you guys are talking about
LOL. Not sure we do as well :)
but it might be you
are looking for a cross-platform multiplexing asynchronous message
exchange system. If so you might look into activemq's openwire
transport. IIUC they have a message
Costin Manolache wrote:
On Sat, Apr 4, 2009 at 9:03 AM, David Jencks david_jen...@yahoo.com wrote:
My understanding of 'what we talk about' is what to do with mod_jk -
deprecate/remove old code, add few features
to better match current tomcat ( and current requirements - larger clusters,
etc
Remy Maucherat wrote:
Why is poller performance bad in Windows? Is that a consequence of the
I've been told it uses select, which works only on 64 sockets at a time.
So if you have a large poller, then the poll call performance degrades.
Mladen is really the only one who can answer Windows
Mark Thomas wrote:
On behalf of the Tomcat committers I am pleased to announce that Konstantin
Kolinko has been voted in as a new Tomcat committer.
Please join me in welcoming him.
Welcome Konstantin.
Cheers
--
^(TM)
-
To
William A. Rowe, Jr. wrote:
mt...@apache.org wrote:
+runas /env /savecred /user:%SERVICE_USER% %COMSPEC% /K \%SELF%\ %SERVICE_CMD%
%SERVICE_NAME%
review your cmd.exe syntax. cmd /k is wrong here, that's to persist
a shell. You meant /c I suspect.
Well /c does give no info to the user.
Hi,
As you could see from the SVN log I've updated procrun
binaries to 2.0.5 version (Tagged as COMMONS_DAEMON_2_0_5 in commons)
It contains a fix that might help XP/SP1 and later using Java6
on systems that do not have msvcrt71.dll in the PATH
(Something Sun refuses to fix) by using the
Konstantin Kolinko wrote:
Your removal of 64-bit GUI files broke the build scripts there.
Sorry ;)
Thought it will be easy to fix.
Is suppose the copy task should just use the *.exe
instead referencing the files directly (more reusable)
Nevertheless, how about creating separate .zips
William A. Rowe, Jr. wrote:
Mladen Turk wrote:
Nevertheless, how about creating separate .zips that
would contain tomcat(X)w.exe tomcat(X).exe service.bat
and tcnative-1.dll
eg.
apache-tomcat-6.0.21-win32-native.zip
apache-tomcat-6.0.21-win64-native.zip
apache-tomcat-6.0.21-win64-ia64
+1
Mark Thomas wrote:
Once 4.1.x is archived, there will be no release branches sharing code.
We could also pull out mod_jk and tcnative along the lines of
/repos/asf/tomcat
/mod_jk
/tcnative
Finally! :)
Regards
--
^(TM)
Konstantin Kolinko wrote:
so -win32-x86-native, -win32-x64 and -win32-ia64 would make perfect
sense.
Fine with me.
32 in -win32-x64 looks odd.
Right win64-x64 would make more sense.
In the /bin folder there is now a /bin/procrun subfolder,
that contains
/bin/procrun/amd64/ and
William A. Rowe, Jr. wrote:
Right win64-x64 would make more sense.
Irrelevant.
win32-x64 means nothing to an ordinary user.
There is no win64, but there could be.
What are u talking about?
http://technet.microsoft.com/en-us/library/bb496995.aspx
MS clearly distinguishes Win32 and
Mark Thomas wrote:
IMO the release is broken.
If the windows installer issue is an isolated one it, the release is no
worse than any that have gone out of the door previously. That said, the
issues are all fixed so I'll roll a 4.1.41 release.
Why not just re-tagging?
It's no like it was
As you might see from the SVN log I added few more dist files.
The newly created files are:
apache-tomcat-7.0.0-dev-win32-x86-native.zip
apache-tomcat-7.0.0-dev-win64-ia64-native.zip
apache-tomcat-7.0.0-dev-win64-x86_64-native.zip
I have also removed the .exe, .dll and service.bat from the
interested developers.
The first message on dev@ list was posted by Brian Behlendorf
on Tue, 15 Jun 1999 07:53:14 GMT and it looked like this:
This is just a test of the ezmlm system... let's see if it works. =)
So, wish us happy anniversary :)
Regards
--
Mladen Turk
Apache Tomcat PMC Chair
Mark Thomas wrote:
Mladen Turk wrote:
The standard .zip distro should contain only the bare tomcat.
Everything else like docs, deployer etc are already in separate packages.
The point is to have the same functionality as with .exe installer
but from individual peaces, just like you select which
Mark Thomas wrote:
Mladen Turk wrote:
(I'm not even convinced we absolutely need CR-LF line endings).
The reason is that some platforms have limited default tar implementation
like Solaris (especially for long file names and paths).
I see where you are coming from but I think the line ending
Guenter Knauf wrote:
Personally I would prefer something like the MSYS or Cygwin installer:
one executable (I think this could / should even be written in Java)
One thing I hate with Cygwin is it's installer, and with Mingw I really
have no clue what to download from the hundred or so things
Mark Thomas wrote:
The (updated) candidates source tarball and derived binaries are
available here:
http://tomcat.apache.org/dev/dist/apache-tomcat-4.1.40/
According to the release process, the release based on the 4.0.40 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable
[x] Stable
Tested
Hi
instead
jdt.loc=http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.3.1-200709211145/eclipse-JDT-3.3.1.zip
this should now be:
jdt.loc=http://archive.eclipse.org/eclipse/downloads/drops/R-3.3.1-200709211145/download.php?dropFile=eclipse-JDT-3.3.1.zip
It took me
Konstantin Kolinko wrote:
+ StrCmp $0 %PROCESSOR_ARCHITEW6432% 0 +5
I think it should be
StrCmp $0 %PROCESSOR_ARCHITEW6432% +5 0
Thanks for spotting that. Updated the patch as well.
Regards
--
^(TM)
-
To unsubscribe,
Konstantin Kolinko wrote:
2009/6/23 Mladen Turk mt...@apache.org:
Konstantin Kolinko wrote:
+ StrCmp $0 %PROCESSOR_ARCHITEW6432% 0 +5
I think it should be
StrCmp $0 %PROCESSOR_ARCHITEW6432% +5 0
Thanks for spotting that. Updated the patch as well.
OK.
Minor issues:
apache-tomcat-6.0
Konstantin Kolinko wrote:
My zip archiver shows them. Or, using jar -t:
C:\Program Files\Java\jdk1.6.0_14\bin\jar -tf
apache-tomcat-6.0-snapshot-windows-x86.zip | find exe
jar -tf apache-tomcat-6.0-snapshot-windows-x86.zip | greo -e '\.exe$' -e
'\.dll$'
Filip Hanik - Dev Lists wrote:
what do you guys wanna do? Get through STATUS as it is today, then issue
a release?
I'm preparing the new packages patch for 5.5.x as well.
It would be nice to have cleaned packages and installer
supporting 32 and 64 bit JVM and OSs.
Regards
--
^(TM)
Mark Thomas wrote:
It is unclear to me whether the archive is CTR or RTC since it does
contain some old release branches. I would like to propose making the
whole archive CTR. On the rare occassions where someone wishes to make a
change to code in the archive, this will make it easier.
kkoli...@apache.org wrote:
Author: kkolinko
* When throwing Non-serializable exception, mark which argument was
@@ -163,6 +163,13 @@
6.0.x version of the patch:
http://people.apache.org/~mturk/tomcat/setAttribute.iae.patch
+1: mturk
+ -1: kkolinko: (
+ good in general, but
+
Filip Hanik - Dev Lists wrote:
Unless anyone objects, we can clear out the status for 5.5 and do a tag
on Monday.
+1
I was hoping to backport the windows packaging, but it's
not that straightforward, so can wait for a next release.
Regards
--
^(TM)
William A. Rowe, Jr. wrote:
You have three groups, general users, Tomcat users, and Tomcat Admins.
I understand the second two, and have no clue what you mean by general :)
It should mean 'Anyone', not just users/admins already familiar
(to some extend) to Tomcat.
Regards
--
^(TM)
On 17/07/09 15:27, Konstantin Kolinko wrote:
2009/7/17 Rainer Jungrainer.j...@kippdata.de:
In this case, name to be seen by users, I have some strong feelings for
ia64 instead of i64. I thought that's the standard used for the Itanium
architecture. Is there any official or pseudo-official of
On 21/07/09 03:11, kkoli...@apache.org wrote:
Author: kkolinko
Date: Tue Jul 21 01:11:31 2009
New Revision: 796103
URL: http://svn.apache.org/viewvc?rev=796103view=rev
Log:
Bundle native dlls with exe installer, instead of downloading some old
(1.1.4) native version from Heanet, and install DLL
On 29/07/09 17:25, Rainer Jung wrote:
Of course first you need to get access to V6R1...
I had V6 once, but it was Peugeot Coupe. Nasty beast :)
Anyhow, perhaps Henri can upload some binaries
inside the dist if relevant.
Cheers
--
^TM
On 27/07/09 22:20, Filip Hanik - Dev Lists wrote:
The candidates binaries are available here:
http://people.apache.org/~fhanik/tomcat/tomcat-5.5/v5.5.28/
According to the release process, the 5.5.28 tag is:
[ ] Broken
[ ] Alpha
[ ] Beta
[X] Stable
Regards
--
^TM
Hi,
JK connector uses the request.secret attribute for setting the
AJP secret property. However APR connector and Ajp connector
use the requiredSecret instead. This of course (first problem is
that it's nowhere documented) makes problems cause it requires to
have separate directives depending on
On 07/08/09 13:41, Mark Thomas wrote:
Just a reminder that once 5.5.28 is released, I am planning to re-org
svn. If you have checkouts of 5.5.x, jk, native, isapi, nsapi this will
affect you.
I am currently planning the following changes:
When done, could you post the changes or even better
On 07/08/09 17:34, Mark Thomas wrote:
Mladen Turk wrote:
On 07/08/09 13:41, Mark Thomas wrote:
Just a reminder that once 5.5.28 is released, I am planning to re-org
svn. If you have checkouts of 5.5.x, jk, native, isapi, nsapi this will
affect you.
I am currently planning the following
Forwarding the original message...
Sign up for ApacheCon US by 14 August and save up to $500!
This year's ApacheCon US promises to deliver our most extensive program to date, and largest anticipated gathering of the global Apache community to celebrate the ASF's milestone 10th Anniversary. The
On 12/08/09 15:18, Konstantin Kolinko wrote:
2009/8/4 Mladen Turkmt...@apache.org:
Hi,
JK connector uses the request.secret attribute for setting the
AJP secret property. However APR connector and Ajp connector
use the requiredSecret instead. This of course (first problem is
that it's nowhere
On 13/08/09 19:43, Konstantin Kolinko wrote:
Other option is to use required.secret instead requiredSecret
Much easier because requiredSecret isn't document, so one
can only find it browsing the source code.
However dunno how to make it using current property set/get methods
I have just
On 16/09/09 13:23, Rainer Jung wrote:
Is tcnative 1.1.x CTR or RTC?
CTR, with standard branch exceptional clause:
No new features, no API changes.
There are a couple of simple fixes sitting in there and waiting for a
vote, but if we are still RTC, I would like to apply them before 1.1.17.
On 16/09/09 16:18, Mark Thomas wrote:
rj...@apache.org wrote:
Author: rjung
Date: Wed Sep 16 13:24:54 2009
New Revision: 815768
URL: http://svn.apache.org/viewvc?rev=815768view=rev
Log:
Sync java parts of tcnative with C part.
Do we need the java part here any more? 5.5.x, 6.0.x and trunk
On 16/09/09 18:53, Rainer Jung wrote:
If we want to get every Java related file for jni from Tomcat, we would
need to add the test and examples files back.
build.xml and build.properties.default might make more sense in native
itself.
Comments?
Sure, we should bring back java/examples and
Hi,
Anyone volunteering for 1.1.17 RM?
We have one nasty bug with OpenSSL/Windows that
users are constantly complaining about, and since
the patch is already in the SVN and confirmed to
solve the issue I see no problem we push for a
new release.
If no one has the spare time, I'll tag and
On 20/10/09 21:55, jean-frederic clere wrote:
Hi,
Apache Tomcat Native 1.1.17 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
Regards
--
^TM
On 06/27/2011 08:03 PM, Mladen Turk wrote:
I have a time slot available so I volunteer as a 1.2.32 RM.
Think we are good for a new release.
Prepared and made couple of dry runs. So far so good.
and all platforms build cleanly.
We'll have a simplified dist layout starting from this
release
Hi,
At
http://people.apache.org/~mturk/tomcat-connectors/jk/
you can find the connectors tagged as RC1.
Check the new dist layout and artifacts.
Few notes about dist
1. No more sources/ dir
2. Binaries are produced for windows only
3. Binaries are enclosed inside .zip files
I plan to call for
The proposed Apache Tomcat Connecotrs 1.2.32 release is now available for
voting.
It can be obtained from:
http://people.apache.org/~mturk/tomcat-connectors/jk/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/jk/tags/JK_1_2_32
Generated documentation can be seen at:
On 07/04/2011 08:43 AM, Henri Gomez wrote:
Works for me (OS/X 10.6.8)
BTW: I could provide binaries if needed
I wish we break the practice of shipping the
posix platform binaries.
This was never consistent in the past between
releases, and it looks more like a junk yard.
(basically, if it
On 07/04/2011 08:43 AM, Henri Gomez wrote:
Works for me (OS/X 10.6.8)
I suppose that '[x] Stable'
right?
Cheers
--
^TM
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
With my implicit +1 we have 4 binding votes
(Henri, Jim, Tim and I)
As such Tomcat Connectors 1.2.32 has been voted as stable.
I'll copy the files to the dist, and make ANN later today
when majority of mirrors pick the dist.
Thanks to all who helped testing!
Regards
--
^TM
The proposed 7.0.18 release is:
[ ] Broken - do not release
[ ] Alpha - go ahead and release as 7.0.18 Alpha
[ ] Beta - go ahead and release as 7.0.18 Beta
[X] Stable - go ahead and release as 7.0.18 Stable
Tested on linux and windows.
Love the new installer features!
Regards
--
^TM
The Apache Tomcat Project is proud to announce the release
of version 1.2.32 of Apache Tomcat Connectors.
This release includes both bug fixes and new features compared
to version 1.2.31. Full details of these changes and new features,
are available in the Apache Tomcat Connectors changelog:
On 07/09/2011 04:14 AM, Christopher Schultz wrote:
All,
I've been working in AprLifecycleListener to add FIPS support. I need to
make an additional native method call in initializeSSL and I'm wondering
why all of the native methods are called using reflection instead of
direct method calls.
On 07/13/2011 11:35 AM, Henri Gomez wrote:
I just seen my tomcat-native 1.1.20 is not working anymore on OS/X (10.6.8).
I tried to rebuild and install under latest OS/X 10.6.8 but Tomcat 6
still didn't detect it.
Have you tried starting tomcat with 'java -d32/-d64'
Might be the wrong ABI
On 07/25/2011 07:31 PM, Christopher Schultz wrote:
Jean-Frederic,
Nope, it also includes the native part of FIPS mode. I forgot to update
the changelog when I did that commit. Now updated.
Note that the new FIPS code isn't called by anything on the Java side at
this point. I'm still working
On 07/27/2011 11:20 AM, jean-frederic clere wrote:
Win32/Win64 binaries will be available at:
http://tomcat.apache.org/dev/dist/tomcat-connectors/native/1.1.21/binaries/
Think we should stop shipping anything that is not voted for.
You should have call for a vote after the binaries are
On 07/26/2011 07:30 PM, Mark Thomas wrote:
1. Should tomcat/tc7.0.x/trunk be RTC or CTR?
CTR
2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to
see earlier and more frequent alpha/beta releases than we had for Tomcat
Sure. This time we might have 8 ready as 3.1 spec
On 07/27/2011 06:53 PM, Mark Thomas wrote:
On 27/07/2011 16:48, Mladen Turk wrote:
After we release first 8 stable or starting from now?
I was thinking announce EOL for 5.5.x now, with the actual EOL date /
last release ~August 2012.
OK, but IMHO we should add +12 months
On 07/29/2011 08:32 AM, jean-frederic clere wrote:
I mention that because buildconf require APR source directory whereas
I used to build it (on OSX/ or Linux) against provided APR, i.e. like
this :
CFLAGS='-arch i386 -arch x86_64' APXSLDFLAGS='-arch i386 -arch x86_64'
./configure
On 08/09/2011 11:33 AM, Mark Thomas wrote:
The proposed 7.0.20 release is:
[X] Stable - go ahead and release as 7.0.20 Stable
Tested on Linux and Windows.
Regards
--
^TM
-
To unsubscribe, e-mail:
On 08/18/2011 03:54 AM, t...@apache.org wrote:
Author: timw
Date: Thu Aug 18 01:54:31 2011
New Revision: 1158991
URL: http://svn.apache.org/viewvc?rev=1158991view=rev
Log:
Use the DLL handle to make the shared memory file name used by the ISAPI
Redirector unique for each DLL - the redirector
On 09/27/2011 11:36 PM, Mark Thomas wrote:
The proposed 7.0.21 release is:
[ ] Broken - do not release
[ ] Beta - go ahead and release as 7.0.22 Beta
[x] Stable - go ahead and release as 7.0.22 Stable
Do an usual set of tests on win32/win64 and linux
Regards
--
^TM
Jess Holle wrote:
I want to use mod_proxy_balancer to load balance over a set of ports
that potentially have Tomcats running on them.
Unfortunately there will generally be a good number of ports where no
Tomcat is running. Every 'retry' seconds I have a request that takes
about an extra
Jess Holle wrote:
I'm quite willing to help, but you're clearly much more familiar with
both mod_jk and APR/MPM than I am, so I suspect I'd just get in the way
except at the testing level.
Well, I plan to create mpm watchdog hook system first.
I'll also create a small callback in
Jess Holle wrote:
Mladen Turk wrote:
Is there a means of achieving background-only (or nearly so) testing of
dead workers with mod_jk? That's what I'm looking for in both jk and
mod_proxy_ajp connectors. I guess I was hoping/assuming it was there in
mod_jk from reading the docs
Jess Holle wrote:
P.S. I'd also like to quiet attempts to recover workers from errors to a
lower (and by default unlogged) logging level. The transition of a
worker into an error state should certainly be logged, but logging every
time we find it to still be in an error state seems to be
[EMAIL PROTECTED] wrote:
Fix wrong default in doc.
Modified:
tomcat/trunk/webapps/docs/config/http.xml
Modified: tomcat/trunk/webapps/docs/config/http.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/http.xml?rev=689758r1=689757r2=689758view=diff
Jim Jagielski wrote:
As Mladen said, there is some very prelim discussions regarding
key aspects of these issue on the httpd-dev list. But it is hardly
unique to mod_proxy (mod_dbd could also use a nice robust watchdog
hook implementation).
Correct. The bottom line is like you said to move
201 - 300 of 1171 matches
Mail list logo