tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <cmanola...@yahoo.com>
Subject Re: MBeanException w/AJP13Connector and (hopefully) itssolution
Date Tue, 15 Oct 2002 16:44:05 GMT
Jeff Tulley wrote:

> So I find that works on NetWare with our mod_jk, as you said.  The only
> thing that worries me is that the port value set in server.xml is not
> honored, on Windows or on NetWare.  Is there somewhere else it is pulling
> its configuration from?  I cannot have shifting ajp ports, since I might
> have two catalina instances running simultaneously, and I need to control
> what port Apache sends requests to, so that I can route them right.
> 
> What I saw was that I set the port to 9010, but Catalina still comes up
> with "ajp13 listening on tcp port 8009".  When I fire up the second
> instance of Catalina, it comes up listening on 8010, after unsuccessfully
> trying to get port 8009.  I cannot just use 8009 and 8010, due to both
> port conflicts on NetWare(with 8009), and because I do not want to rely on
> startup order of the two Catalina instances.
> 
> Is this a bug, or is there some part of the design that I'm missing?

Most likely a bug.

The problem is that we're using 2 configs - one is jk2.properties,
and the other is server.xml.

The original intention was that both mod_jk and the java side use the
same config file/format. Xml in C was considered too complex and too
big change. Unfortunately that wasn't implemented, but there is still
hope for 5.0, if the new config mechanism happens.

Regarding 8009, 8010, etc - that can be disabled ( set maxPort==port ),
it is intended to simplify load-balanced setup ( no need for multiple
configs - at least if you disable the shutdown and http ports which may
create conflicts ).

I'm pretty sure that if you set the port in jk2.properties it'll work,
I'll try to find out why the information is not passed from server.xml.
( if you can send a patch - it would be great ).

Regarding jk1/jk2 - the protocol is identical. The java side ( coyote-based) 
is stable for jk2, and it seems much better than the original connector,
so that's the default. The old one can be considered as deprecated. On the
C side, jk2 is getting there - but most people consider jk1 as more stable
and it's the only one to support netscape or aol - we only implemented the 
apache and iis adapters so far for jk2. Hopefully mod_jk2 will be released 
at the same time with 5.0.

We certainly need a mechanism to extend the mbeans.xml for thrid party
and other modules, again - a patch would be great :-)


Costin





--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message