No More JK2
I had some issues trying to migrate from Apache 2.0.52 to 2.0.53 on one of my Gentoo servers, which is a story in itself, but while doing so, I came across this:
==============================================================================
15 November - JK2 is officially unsupported
JK2 has been put in maintainer mode and no further development will take place. The reason for shutting down JK2 development was the lack of developers interest. Other reason was lack of users interest in adopting JK2, caused by configuration complexity when compared to JK.
The latest official JK2 release is 2.0.4.
JK2 will have it’s successor within core Apache2.1/2.2 distribution. We have developed new proxy_ajp that is an addition to the mod_proxy and uses Tomcat’s AJP protocol stack. It is developed in httpd-2.1 and integrated in it. We have also developed a new proxy_balancer module for load balancing http and ajp protocol stacks.
==============================================================================
Am I the only one frustrated with things like this? First there was JServ. Then there JK. Then JK2. Oh, and also mod_webapp. So many ways to connect Tomcat to Apache. Which is fine. And it’s fine that they are creating yet another connector. My big problem is the comment about lack of user interest due to configuration complexity. I definitely found this to be the case, but for the simple reason that the documentation sucks (or at least it did; and I haven’t checked it recently). I managed to figure it out the same way everyone else seemed to; a combination of trial and error and Google searches.
I can’t wait for the struggle that will likely happen when the proxy_ajp is released and I need to figure out how to use it.
Wed, 09 Mar 2005 04:10 Posted in Software
