Yeah there are a miriad of solutions to this problem. First off, the immediate solutions is to add the patch I posted to the list - that is, to add in the MBean tags to the mbean descriptor XML file, describing the AJP 13 connector. That gets rid of the exception right away. This, of course, keeps you using the deprecated AJP 13 Connector. We had resisted moving since we did not realize that the new Coyote connector does work with the old mod_jk Apache mod. I've attached that patch.
Now, the options if you move to the Coyote JkHandler: 1) Easiest, immediate fix to the problem: Add " IntrospectionUtils.setProperty(protocolHandler, "channelSocket.port", "" + port);" to the file coyote/src/java/org/apache/coyote/tomcat4/CoyoteConnector.java", in the jakarta-tomcat-connectors project. Add this in the initialize method, right after the line that sets the port. What this does is take whatever port you have set in your server.xml and also sets that port for the "channelSocket". If you also have a value in jk2.properties, this value will over-ride that one. I've attached a patch that has the "unified diff" of this fix. 2) What really needs to happen is some way of associating the connector instances in server.xml with the connector properties in jk2.properties that allows you to have multiple instances of Tomcat. This would take a bit more work, though a lot of the support is already there in jk2.properties. (IE, instead of "channelSocket.port=8009" in jk2.properties, you can have "channelSocketPort.instance1.port=8009". The only thing left to do is associate the connector in server.xml with "instance1", maybe with a new attribute in the Connector XML tag). This would be a bit more involved, and I do not have a patch for this problem (yet?). With this solution, all of the configuration information that is common between the java Connector and the C-based Apache Mods can come from one file instead of two as in the past. I think this is the design the committers want ultimately. Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> Richard Doorduin <[EMAIL PROTECTED]> 10/22/02 4:57:20 AM >>> Dear Jeff, It seems that we are sharing the same problem that is if you still haven't found the solution for it. That is why I am emailing you. Because it would make it less difficult if you found the solution for it. I hope you can reply to me! Greetings, Richard Doorduin
mbeans-descriptors.patch
Description: Binary data
CoyoteConnector.patch
Description: Binary data
-- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
