Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1
Bill Barker wrote: - Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 7:46 AM Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1 Henri Gomez wrote: Bill Barker wrote: The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team I make test on it and play with JMXSupport and noticed : - XSL problem with HTTP connector : [Error] common.xsl:14:80: Element type xsl:stylesheet must be declared. [Error] common.xsl:16:38: Element type xsl:import must be declared. [Error] common.xsl:19:35: Element type xsl:param must be declared. [Error] common.xsl:21:96: Element type xsl:variable must be declared. [Error] common.xsl:24:28: Element type xsl:template must be declared. [Error] common.xsl:25:30: Element type xsl:if must be declared. It seems Costin patch the xsl sometimes ago at mx4j, so should we included this modified version ? - As many, in my web application, I allready load HTTP/JRMP connector (at special ports with custom login/pwd), but since JMXSupport is loaded before my app, it didn't use my HTTP port settings. What about set port to -1 by default in interceptors.xml to avoid such problems ? org.apache.coyote.tomcat3.CoyoteInterceptor2 didn't present many informations via JMX, could we use a trick to present what is present in processor class ? I haven't looked at JMXSupport in a while, but it should be possible to add this in. o.a.jk and o.a.c.http11 already have the self-registration code. It's just a matter of triggering it. I could do it but wonder where to put the registration, org.apache.coyote.tomcat3.Coyote2 ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1
- Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 4:04 AM Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1 Bill Barker wrote: - Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 7:46 AM Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1 Henri Gomez wrote: Bill Barker wrote: The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team I make test on it and play with JMXSupport and noticed : - XSL problem with HTTP connector : [Error] common.xsl:14:80: Element type xsl:stylesheet must be declared. [Error] common.xsl:16:38: Element type xsl:import must be declared. [Error] common.xsl:19:35: Element type xsl:param must be declared. [Error] common.xsl:21:96: Element type xsl:variable must be declared. [Error] common.xsl:24:28: Element type xsl:template must be declared. [Error] common.xsl:25:30: Element type xsl:if must be declared. It seems Costin patch the xsl sometimes ago at mx4j, so should we included this modified version ? - As many, in my web application, I allready load HTTP/JRMP connector (at special ports with custom login/pwd), but since JMXSupport is loaded before my app, it didn't use my HTTP port settings. What about set port to -1 by default in interceptors.xml to avoid such problems ? org.apache.coyote.tomcat3.CoyoteInterceptor2 didn't present many informations via JMX, could we use a trick to present what is present in processor class ? I haven't looked at JMXSupport in a while, but it should be possible to add this in. o.a.jk and o.a.c.http11 already have the self-registration code. It's just a matter of triggering it. I could do it but wonder where to put the registration, org.apache.coyote.tomcat3.Coyote2 ? For 3.3.3 that is probably a good place for it. However, I'm not very happy about introducing a dependancy on c-m into the Connector this late in the release cycle. I'll stick it into JMXSupport for now, and we can re-visit JMX in 3.3 again after the release (assuming that there is still interest :). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1
Bill Barker wrote: - Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 4:04 AM Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1 Bill Barker wrote: - Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 7:46 AM Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1 Henri Gomez wrote: Bill Barker wrote: The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team I make test on it and play with JMXSupport and noticed : - XSL problem with HTTP connector : [Error] common.xsl:14:80: Element type xsl:stylesheet must be declared. [Error] common.xsl:16:38: Element type xsl:import must be declared. [Error] common.xsl:19:35: Element type xsl:param must be declared. [Error] common.xsl:21:96: Element type xsl:variable must be declared. [Error] common.xsl:24:28: Element type xsl:template must be declared. [Error] common.xsl:25:30: Element type xsl:if must be declared. It seems Costin patch the xsl sometimes ago at mx4j, so should we included this modified version ? - As many, in my web application, I allready load HTTP/JRMP connector (at special ports with custom login/pwd), but since JMXSupport is loaded before my app, it didn't use my HTTP port settings. What about set port to -1 by default in interceptors.xml to avoid such problems ? org.apache.coyote.tomcat3.CoyoteInterceptor2 didn't present many informations via JMX, could we use a trick to present what is present in processor class ? I haven't looked at JMXSupport in a while, but it should be possible to add this in. o.a.jk and o.a.c.http11 already have the self-registration code. It's just a matter of triggering it. I could do it but wonder where to put the registration, org.apache.coyote.tomcat3.Coyote2 ? For 3.3.3 that is probably a good place for it. However, I'm not very happy about introducing a dependancy on c-m into the Connector this late in the release cycle. I'll stick it into JMXSupport for now, and we can re-visit JMX in 3.3 again after the release (assuming that there is still interest :). I'd like to have it of course :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1
Bill Barker wrote: The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team I make test on it and play with JMXSupport and noticed : - XSL problem with HTTP connector : [Error] common.xsl:14:80: Element type xsl:stylesheet must be declared. [Error] common.xsl:16:38: Element type xsl:import must be declared. [Error] common.xsl:19:35: Element type xsl:param must be declared. [Error] common.xsl:21:96: Element type xsl:variable must be declared. [Error] common.xsl:24:28: Element type xsl:template must be declared. [Error] common.xsl:25:30: Element type xsl:if must be declared. It seems Costin patch the xsl sometimes ago at mx4j, so should we included this modified version ? - As many, in my web application, I allready load HTTP/JRMP connector (at special ports with custom login/pwd), but since JMXSupport is loaded before my app, it didn't use my HTTP port settings. What about set port to -1 by default in interceptors.xml to avoid such problems ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1
Henri Gomez wrote: Bill Barker wrote: The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team I make test on it and play with JMXSupport and noticed : - XSL problem with HTTP connector : [Error] common.xsl:14:80: Element type xsl:stylesheet must be declared. [Error] common.xsl:16:38: Element type xsl:import must be declared. [Error] common.xsl:19:35: Element type xsl:param must be declared. [Error] common.xsl:21:96: Element type xsl:variable must be declared. [Error] common.xsl:24:28: Element type xsl:template must be declared. [Error] common.xsl:25:30: Element type xsl:if must be declared. It seems Costin patch the xsl sometimes ago at mx4j, so should we included this modified version ? - As many, in my web application, I allready load HTTP/JRMP connector (at special ports with custom login/pwd), but since JMXSupport is loaded before my app, it didn't use my HTTP port settings. What about set port to -1 by default in interceptors.xml to avoid such problems ? org.apache.coyote.tomcat3.CoyoteInterceptor2 didn't present many informations via JMX, could we use a trick to present what is present in processor class ? The goal is to be able to change some attributes, like port or listen adress from JMX console. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1
- Original Message - From: Henri Gomez [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 7:46 AM Subject: Re: [ANN] Apache Tomcat 3.3.2 Release Candidate 1 Henri Gomez wrote: Bill Barker wrote: The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team I make test on it and play with JMXSupport and noticed : - XSL problem with HTTP connector : [Error] common.xsl:14:80: Element type xsl:stylesheet must be declared. [Error] common.xsl:16:38: Element type xsl:import must be declared. [Error] common.xsl:19:35: Element type xsl:param must be declared. [Error] common.xsl:21:96: Element type xsl:variable must be declared. [Error] common.xsl:24:28: Element type xsl:template must be declared. [Error] common.xsl:25:30: Element type xsl:if must be declared. It seems Costin patch the xsl sometimes ago at mx4j, so should we included this modified version ? - As many, in my web application, I allready load HTTP/JRMP connector (at special ports with custom login/pwd), but since JMXSupport is loaded before my app, it didn't use my HTTP port settings. What about set port to -1 by default in interceptors.xml to avoid such problems ? org.apache.coyote.tomcat3.CoyoteInterceptor2 didn't present many informations via JMX, could we use a trick to present what is present in processor class ? I haven't looked at JMXSupport in a while, but it should be possible to add this in. o.a.jk and o.a.c.http11 already have the self-registration code. It's just a matter of triggering it. The goal is to be able to change some attributes, like port or listen adress from JMX console. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Unet Requests #117871] [ANN] Apache Tomcat 3.3.2 Release Candidate 1
This is an automated response. There is no need to reply. Hello, from Networking Telecommunication Services. Your message regarding: [Unet Requests #117871] [ANN] Apache Tomcat 3.3.2 Release Candidate 1 has been received and assigned a request number of 117871. In order help us track the progress of this request, we ask that you include the string [Unet Requests #117871] in the subject line of any further mail about this particular request. For example: Subject: [Unet Requests #117871] [ANN] Apache Tomcat 3.3.2 Release Candidate 1 You may do this simply by replying to this e-mail. Generally, your request should be done within one business day from the time your e-mail is received. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Apache Tomcat 3.3.2 Release Candidate 1
The Tomcat Team announces the immediate availability of Apache Tomcat 3.3.2 Release Candidate 1. Downloads: http://www.apache.org/~larryi/tomcat-3.3.2-rc1 The Apache Tomcat Team This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
