Re: [Vote] Announce EOL for ajp12 and ajp14 workers in mod_jk

Christopher Schultz <[email protected]>
Newsgroups gmane.comp.jakarta.tomcat.devel
Message-ID <[email protected]>
Rainer,

On 6/15/26 5:01 AM, Rainer Jung wrote:
> Picking up the date suggested by Mark I propose to announce the EOL date 
> 2027-06-30 for the worker types ajp12 and ajp14 in Tomcat connectors aka 
> mod_jk aka ISAPI redirector.
> 
> Reason for ajp12: The sources say it is deprecated at least for a decade 
> now, the docs say it's obsolete. I never saw it in use or remember any 
> question raised about it.
> 
> Reason for ajp14: it was always experimental. I never saw it in use or 
> remember any question raised about it.
> 
> Some source code files or types and functions could be dropped as well 
> at the EOL date, because they are only used by ajp12 or ajp14 (eg. 
> jk_sockbuf annd jk_sb_* for ajp12, jk_md5 for ajp14).
> 
> Setting EOL date for ajp12:
> 
>   [ ] Yes, I agree with EOL 2027-06-30
>   [ ] No, I don't agree with any EOL
>   [ ] I strongly prefer EOL date .......... instead

+1 for EOL 2027-06-30, though I would have agreed with an immediate EOL 
as the whole industry moved to ajp13 years ago along with mod_jk, 
mod_proxy_ajp, etc.

> Setting EOL date for ajp14:
> 
>   [ ] Yes, I agree with EOL 2027-06-30
>   [ ] No, I don't agree with any EOL
>   [ ] I strongly prefer EOL date .......... instead

+1 for EOL 2027-06-30, though I would have agreed with an immediate EOL 
as ajp14 was never really shipped.

-chris
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.