You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/08/22 18:47:20 UTC
DO NOT REPLY [Bug 22663] New: -
Inner Taglibs not being evaluated as taglibs, but static content
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22663>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22663
Inner Taglibs not being evaluated as taglibs, but static content
Summary: Inner Taglibs not being evaluated as taglibs, but static
content
Product: Tomcat 5
Version: Nightly Build
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Major
Priority: Other
Component: Jasper2
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: jason.hodge@unishippers.com
When taglibs are embedded within each other, the inner taglibs are being
treated as static content rather than evaluated as taglibs. The external code
runs (which is security code), but the inner one only displays as text. This
works in JRun4 as expected.
<uone:RestrictAccess roles="ReadWrite, ReadWriteUpdate,
ReadWriteUpdateVoid">
<uone:button label="Secure" width="300" onClick="JavaScript:alert
('Hello World!')"/><br>
</uone:RestrictAccess>
Re: [VOTE] 5.0.9 stability rating
Posted by Bill Barker <wb...@wilshire.com>.
Just realized that I marked the wrong box (d*** hanging chads :). Changing
my vote to 'Alpha' for reasons given below.
"Bill Barker" <wb...@wilshire.com> wrote in message
news:00bf01c368ed$40b57ec0$ec66a8c0@bbarkerxp...
>
> ----- Original Message -----
> From: "Remy Maucherat" <re...@apache.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Friday, August 22, 2003 10:20 AM
> Subject: [VOTE] 5.0.9 stability rating
>
>
> > <ballot>
> > [ ] Alpha
> > [X] Beta
> > </ballot>
> >
>
> 1) The admin webapp lies about Connector properties.
> 2) Authorization isn't spec-compliant (I mis-read the spec when I did it).
> However, I heard a rumor that the spec may move closer to what Tomcat is
> currently doing (what's in pfd3 is pretty nonsensical :), so I haven't
been
> in a rush to "fix" this.
>
>
>
----------------------------------------------------------------------------
----
> 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: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Amy Roh wrote:
> Remy Maucherat wrote:
>> Please don't add get/set on the CoyoteConnector class itself (we're
>> trying to avoid that, as it's protocol dependent; you can look at
>> Bill's patch - which I reverted for performance reasons, but which did
>> the right thing on principle). IMO, you should add those to the
>> ConnectorMBean, and use get/setProperty. What do you think ?
>
> I thought we're moving away from using *MBean classes and instead using
> the actual class for management implementation. But I see that why we
> want to avoid the getters and setters from the class due to protocol
> dependency. We can definitely move the getters/setters into a
> ConnectorMBean as long as modeler keeps supporting extending class
> mbean. I can either update o.a.c.mbeans.ConnectorMBean and use it or
> put the ConnectorMBean in the coyote directory with the mbean-descriptor
> and the Connector class. I'll need to update admin to represent thread
> pool configuration changes.
The connector is the exception, basically. Attributes processing for
that element is different from the other elements, so this goes along
with that. Since the MBean is related to management, you can IMO leave
it in the mbeans package.
Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Amy Roh <am...@apache.org>.
btw, why does Http11Protocol.getAttribute always return null? Is it on
purpose or just not implement yet since no usage?
Amy Roh wrote:
> Resend. It's been almost 3 hours since I sent the original email.
> wonder if it's my mail server or apache...
>
> Amy Roh wrote:
>
>> Remy Maucherat wrote:
>>
>>> Amy Roh wrote:
>>>
>>>> Remy Maucherat wrote:
>>>>
>>>>> Amy Roh wrote:
>>>>>
>>>>>> I'll update the mbean-descriptor.xml and admin page for Connector
>>>>>> soon.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thanks. Sorry for the trouble.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> No Problem. I just committed the updates. Let me know if there is
>>>> additional updates or if I missed/overlooked anything.
>>>
>>>
>>>
>>>
>>> The changes are a bit more complex than what you did. The new syntax is:
>>>
>>> HTTP/1.1:
>>>
>>> <Connector port="8080"
>>> maxThreads="150" minSpareThreads="25"
>>> maxSpareThreads="75"
>>> enableLookups="false" redirectPort="8443"
>>> acceptCount="100"
>>> debug="0" connectionTimeout="20000"
>>> disableUploadTimeout="true" />
>>> (the thread pool configuration changed, basically)
>>>
>>> AJP/1.3:
>>>
>>> <Connector port="8009"
>>> enableLookups="false" redirectPort="8443" debug="0"
>>> protocol="AJP/1.3" />
>>> (ie, no thread pool configuration here)
>>>
>>> Please don't add get/set on the CoyoteConnector class itself (we're
>>> trying to avoid that, as it's protocol dependent; you can look at
>>> Bill's patch - which I reverted for performance reasons, but which
>>> did the right thing on principle). IMO, you should add those to the
>>> ConnectorMBean, and use get/setProperty. What do you think ?
>>
>>
>>
>> I thought we're moving away from using *MBean classes and instead
>> using the actual class for management implementation. But I see that
>> why we want to avoid the getters and setters from the class due to
>> protocol dependency. We can definitely move the getters/setters into
>> a ConnectorMBean as long as modeler keeps supporting extending class
>> mbean. I can either update o.a.c.mbeans.ConnectorMBean and use it or
>> put the ConnectorMBean in the coyote directory with the
>> mbean-descriptor and the Connector class. I'll need to update admin
>> to represent thread pool configuration changes.
>>
>> Amy
>>
>>>
>>> Remy
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>>>
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: [VOTE] 5.0.9 stability rating
Posted by Amy Roh <am...@apache.org>.
Resend. It's been almost 3 hours since I sent the original email.
wonder if it's my mail server or apache...
Amy Roh wrote:
> Remy Maucherat wrote:
>
>> Amy Roh wrote:
>>
>>> Remy Maucherat wrote:
>>>
>>>> Amy Roh wrote:
>>>>
>>>>> I'll update the mbean-descriptor.xml and admin page for Connector
>>>>> soon.
>>>>
>>>>
>>>>
>>>>
>>>> Thanks. Sorry for the trouble.
>>>
>>>
>>>
>>>
>>> No Problem. I just committed the updates. Let me know if there is
>>> additional updates or if I missed/overlooked anything.
>>
>>
>>
>> The changes are a bit more complex than what you did. The new syntax is:
>>
>> HTTP/1.1:
>>
>> <Connector port="8080"
>> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>> enableLookups="false" redirectPort="8443"
>> acceptCount="100"
>> debug="0" connectionTimeout="20000"
>> disableUploadTimeout="true" />
>> (the thread pool configuration changed, basically)
>>
>> AJP/1.3:
>>
>> <Connector port="8009"
>> enableLookups="false" redirectPort="8443" debug="0"
>> protocol="AJP/1.3" />
>> (ie, no thread pool configuration here)
>>
>> Please don't add get/set on the CoyoteConnector class itself (we're
>> trying to avoid that, as it's protocol dependent; you can look at
>> Bill's patch - which I reverted for performance reasons, but which did
>> the right thing on principle). IMO, you should add those to the
>> ConnectorMBean, and use get/setProperty. What do you think ?
>
>
> I thought we're moving away from using *MBean classes and instead using
> the actual class for management implementation. But I see that why we
> want to avoid the getters and setters from the class due to protocol
> dependency. We can definitely move the getters/setters into a
> ConnectorMBean as long as modeler keeps supporting extending class
> mbean. I can either update o.a.c.mbeans.ConnectorMBean and use it or
> put the ConnectorMBean in the coyote directory with the mbean-descriptor
> and the Connector class. I'll need to update admin to represent thread
> pool configuration changes.
>
> Amy
>
>>
>> Remy
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>>
>
>
Re: [VOTE] 5.0.9 stability rating
Posted by Amy Roh <am...@apache.org>.
Bill Barker wrote:
> If you need help in implementation, I'm more than happy to lend a hand ;-).
> Point of fact was that I was assuming that I would be making the changes
> you've made myself.
Cool. So I looked at your reverted patch. I think it makes sense to
put similar implemntation into ConnectorMBean class then. Would you
like to do it or do you want me to use your patch and apply it?
Thanks,
Amy
Re: [VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Bill Barker wrote:
> ----- Original Message -----
> From: "Amy Roh" <am...@apache.org>
> To: "Tomcat Developers List" <to...@jakarta.apache.org>
> Sent: Tuesday, August 26, 2003 12:11 PM
> Subject: Re: [VOTE] 5.0.9 stability rating
>
>
>
>>Remy Maucherat wrote:
>>
>>
>>>Amy Roh wrote:
>>>
>>>
>>>>Remy Maucherat wrote:
>>>>
>>>>
>>>>>Amy Roh wrote:
>>>>>
>>>>>
>>>>>>I'll update the mbean-descriptor.xml and admin page for Connector
>
> soon.
>
>>>>>
>>>>>
>>>>>Thanks. Sorry for the trouble.
>>>>
>>>>
>>>>
>>>>No Problem. I just committed the updates. Let me know if there is
>>>>additional updates or if I missed/overlooked anything.
>>>
>>>
>>>The changes are a bit more complex than what you did. The new syntax is:
>>>
>>>HTTP/1.1:
>>>
>>> <Connector port="8080"
>>> maxThreads="150" minSpareThreads="25"
>
> maxSpareThreads="75"
>
>>> enableLookups="false" redirectPort="8443"
>
> acceptCount="100"
>
>>> debug="0" connectionTimeout="20000"
>>> disableUploadTimeout="true" />
>>>(the thread pool configuration changed, basically)
>>>
>>>AJP/1.3:
>>>
>>> <Connector port="8009"
>>> enableLookups="false" redirectPort="8443" debug="0"
>>> protocol="AJP/1.3" />
>>>(ie, no thread pool configuration here)
>>>
>>>Please don't add get/set on the CoyoteConnector class itself (we're
>>>trying to avoid that, as it's protocol dependent; you can look at Bill's
>>>patch - which I reverted for performance reasons, but which did the
>>>right thing on principle). IMO, you should add those to the
>>>ConnectorMBean, and use get/setProperty. What do you think ?
>>
>>I thought we're moving away from using *MBean classes and instead using
>>the actual class for management implementation. But I see that why we
>>want to avoid the getters and setters from the class due to protocol
>>dependency. We can definitely move the getters/setters into a
>>ConnectorMBean as long as modeler keeps supporting extending class
>>mbean. I can either update o.a.c.mbeans.ConnectorMBean and use it or
>>put the ConnectorMBean in the coyote directory with the mbean-descriptor
>>and the Connector class. I'll need to update admin to represent thread
>>pool configuration changes.
>>
>>Amy
>
>
> Yeah, I know that this is a six-hour-stale message ;-). The Connector has
> become somewhat of a special case, so it probably merits getting it's own
> intelligent MBean. There are properties that make sense on one Connector
> (e.g. maxKeepAliveRequest on HTTP/1.1, but not on AJP), and default values
> that are wildly different (e.g. connectionTimeout, which should be enabled
> to a short value on HTTP/1.1, and disabled on AJP).
>
> I attempted to implement this in the Connector class, but as Remy pointed
> out, it's not practical given the need to access attributes in the critical
> path. So, the Connectors need a custom MBean to allow JMX to be able to
> configure them correctly.
I think only a subset of the attributes are needed in the critical path.
IMO we should handle them as special cases (ie, cache them as local
fields) and reapply your patch (it looked like a really good idea before
I did some profiling).
> If you need help in implementation, I'm more than happy to lend a hand ;-).
> Point of fact was that I was assuming that I would be making the changes
> you've made myself.
Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Amy Roh" <am...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Tuesday, August 26, 2003 12:11 PM
Subject: Re: [VOTE] 5.0.9 stability rating
> Remy Maucherat wrote:
>
> > Amy Roh wrote:
> >
> >> Remy Maucherat wrote:
> >>
> >>> Amy Roh wrote:
> >>>
> >>>> I'll update the mbean-descriptor.xml and admin page for Connector
soon.
> >>>
> >>>
> >>>
> >>> Thanks. Sorry for the trouble.
> >>
> >>
> >>
> >> No Problem. I just committed the updates. Let me know if there is
> >> additional updates or if I missed/overlooked anything.
> >
> >
> > The changes are a bit more complex than what you did. The new syntax is:
> >
> > HTTP/1.1:
> >
> > <Connector port="8080"
> > maxThreads="150" minSpareThreads="25"
maxSpareThreads="75"
> > enableLookups="false" redirectPort="8443"
acceptCount="100"
> > debug="0" connectionTimeout="20000"
> > disableUploadTimeout="true" />
> > (the thread pool configuration changed, basically)
> >
> > AJP/1.3:
> >
> > <Connector port="8009"
> > enableLookups="false" redirectPort="8443" debug="0"
> > protocol="AJP/1.3" />
> > (ie, no thread pool configuration here)
> >
> > Please don't add get/set on the CoyoteConnector class itself (we're
> > trying to avoid that, as it's protocol dependent; you can look at Bill's
> > patch - which I reverted for performance reasons, but which did the
> > right thing on principle). IMO, you should add those to the
> > ConnectorMBean, and use get/setProperty. What do you think ?
>
> I thought we're moving away from using *MBean classes and instead using
> the actual class for management implementation. But I see that why we
> want to avoid the getters and setters from the class due to protocol
> dependency. We can definitely move the getters/setters into a
> ConnectorMBean as long as modeler keeps supporting extending class
> mbean. I can either update o.a.c.mbeans.ConnectorMBean and use it or
> put the ConnectorMBean in the coyote directory with the mbean-descriptor
> and the Connector class. I'll need to update admin to represent thread
> pool configuration changes.
>
> Amy
Yeah, I know that this is a six-hour-stale message ;-). The Connector has
become somewhat of a special case, so it probably merits getting it's own
intelligent MBean. There are properties that make sense on one Connector
(e.g. maxKeepAliveRequest on HTTP/1.1, but not on AJP), and default values
that are wildly different (e.g. connectionTimeout, which should be enabled
to a short value on HTTP/1.1, and disabled on AJP).
I attempted to implement this in the Connector class, but as Remy pointed
out, it's not practical given the need to access attributes in the critical
path. So, the Connectors need a custom MBean to allow JMX to be able to
configure them correctly.
If you need help in implementation, I'm more than happy to lend a hand ;-).
Point of fact was that I was assuming that I would be making the changes
you've made myself.
>
> >
> > Remy
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: [VOTE] 5.0.9 stability rating
Posted by Amy Roh <am...@apache.org>.
Remy Maucherat wrote:
> Amy Roh wrote:
>
>> Remy Maucherat wrote:
>>
>>> Amy Roh wrote:
>>>
>>>> I'll update the mbean-descriptor.xml and admin page for Connector soon.
>>>
>>>
>>>
>>> Thanks. Sorry for the trouble.
>>
>>
>>
>> No Problem. I just committed the updates. Let me know if there is
>> additional updates or if I missed/overlooked anything.
>
>
> The changes are a bit more complex than what you did. The new syntax is:
>
> HTTP/1.1:
>
> <Connector port="8080"
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> debug="0" connectionTimeout="20000"
> disableUploadTimeout="true" />
> (the thread pool configuration changed, basically)
>
> AJP/1.3:
>
> <Connector port="8009"
> enableLookups="false" redirectPort="8443" debug="0"
> protocol="AJP/1.3" />
> (ie, no thread pool configuration here)
>
> Please don't add get/set on the CoyoteConnector class itself (we're
> trying to avoid that, as it's protocol dependent; you can look at Bill's
> patch - which I reverted for performance reasons, but which did the
> right thing on principle). IMO, you should add those to the
> ConnectorMBean, and use get/setProperty. What do you think ?
I thought we're moving away from using *MBean classes and instead using
the actual class for management implementation. But I see that why we
want to avoid the getters and setters from the class due to protocol
dependency. We can definitely move the getters/setters into a
ConnectorMBean as long as modeler keeps supporting extending class
mbean. I can either update o.a.c.mbeans.ConnectorMBean and use it or
put the ConnectorMBean in the coyote directory with the mbean-descriptor
and the Connector class. I'll need to update admin to represent thread
pool configuration changes.
Amy
>
> Remy
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: [VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Amy Roh wrote:
> Remy Maucherat wrote:
>
>> Amy Roh wrote:
>>
>>> I'll update the mbean-descriptor.xml and admin page for Connector soon.
>>
>>
>> Thanks. Sorry for the trouble.
>
>
> No Problem. I just committed the updates. Let me know if there is
> additional updates or if I missed/overlooked anything.
The changes are a bit more complex than what you did. The new syntax is:
HTTP/1.1:
<Connector port="8080"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
debug="0" connectionTimeout="20000"
disableUploadTimeout="true" />
(the thread pool configuration changed, basically)
AJP/1.3:
<Connector port="8009"
enableLookups="false" redirectPort="8443" debug="0"
protocol="AJP/1.3" />
(ie, no thread pool configuration here)
Please don't add get/set on the CoyoteConnector class itself (we're
trying to avoid that, as it's protocol dependent; you can look at Bill's
patch - which I reverted for performance reasons, but which did the
right thing on principle). IMO, you should add those to the
ConnectorMBean, and use get/setProperty. What do you think ?
Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Amy Roh <am...@apache.org>.
Remy Maucherat wrote:
> Amy Roh wrote:
>> I'll update the mbean-descriptor.xml and admin page for Connector soon.
>
> Thanks. Sorry for the trouble.
No Problem. I just committed the updates. Let me know if there is
additional updates or if I missed/overlooked anything.
Amy
> Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Amy Roh wrote:
>> 1) The admin webapp lies about Connector properties.
>
> I'll update the mbean-descriptor.xml and admin page for Connector soon.
Thanks. Sorry for the trouble.
Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Amy Roh <am...@apache.org>.
> 1) The admin webapp lies about Connector properties.
I'll update the mbean-descriptor.xml and admin page for Connector soon.
Amy
Re: [VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Bill Barker wrote:
> 1) The admin webapp lies about Connector properties.
Yes, I mentioned that. To be accurate, I don't think the admin webapp
has ever been glitch free in any release.
> 2) Authorization isn't spec-compliant (I mis-read the spec when I did it).
> However, I heard a rumor that the spec may move closer to what Tomcat is
> currently doing (what's in pfd3 is pretty nonsensical :), so I haven't been
> in a rush to "fix" this.
Given that the final behavior is unclear, I do not quite see how this is
a major problem. If this build becomes a beta, I'll add a note about
that also.
We're not going to get anywhere IMO by trying to release a bug free
*first* beta. For example, I don't know right now any bugs or issues I
should work on, so I'm wasting my time.
Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Remy Maucherat" <re...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Friday, August 22, 2003 10:20 AM
Subject: [VOTE] 5.0.9 stability rating
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
>
1) The admin webapp lies about Connector properties.
2) Authorization isn't spec-compliant (I mis-read the spec when I did it).
However, I heard a rumor that the spec may move closer to what Tomcat is
currently doing (what's in pfd3 is pretty nonsensical :), so I haven't been
in a rush to "fix" this.
Re: [VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
Unlike 5.0.8, I haven't found any problems with this build, other than
the two issues I mentioned.
Remy
Re: [VOTE] 5.0.12 stability rating
Posted by Jean-Francois Arcand <jf...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X ] Beta
> </ballot>
-- Jeanfrancois
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.12 stability rating
Posted by Bill Barker <wb...@wilshire.com>.
----- Original Message -----
From: "Hans Bergsten" <ha...@gefionsoftware.com>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Sent: Wednesday, September 17, 2003 8:18 PM
Subject: Re: [VOTE] 5.0.12 stability rating
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [x] Beta
> </ballot>
I've lost the original message. However, I've finally had time to finish
testing, so I'll go for Beta.
RE: [VOTE] 5.0.12 stability rating
Posted by Richard Norman <Ja...@hotmail.com>.
I agree... Beta... I had a little problem with the ISAPI redirector... But
that all is working now...
All applications and Database access I am doing works as well.
I still would like Isapi redirector 2 to work, but that may be something
more to do with my configuration as opposed to any issues with Tomcat...
Solid Beta all the way baby...
Richard Norman
Web/Application Developer
-----Original Message-----
From: Hans Bergsten [mailto:hans@gefionsoftware.com]
Sent: Wednesday, September 17, 2003 8:19 PM
To: Tomcat Developers List
Subject: Re: [VOTE] 5.0.12 stability rating
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [x] Beta
> </ballot>
It runs all examples in my upcoming JSP 2.0 book, so it looks fine to me. I
had some problems with a bundled Xerces version, but for now I consider that
an application problem rather than a container problem. If further analysis
proves otherwise, I'll let you know.
Hans
--
Hans Bergsten <ha...@gefionsoftware.com>
Gefion Software <http://www.gefionsoftware.com/>
Author of O'Reilly's "JavaServer Pages", covering JSP 1.2 and JSTL 1.0
Details at <http://TheJSPBook.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
RE: [VOTE] 5.0.12 stability rating
Posted by Richard Norman <Ja...@hotmail.com>.
I agree... Beta... I had a little problem with the ISAPI redirector... But
that all is working now...
All applications and Database access I am doing works as well.
I still would like Isapi redirector 2 to work, but that may be something
more to do with my configuration as opposed to any issues with Tomcat...
Solid Beta all the way baby...
Richard Norman
Web/Application Developer
-----Original Message-----
From: Hans Bergsten [mailto:hans@gefionsoftware.com]
Sent: Wednesday, September 17, 2003 8:19 PM
To: Tomcat Developers List
Subject: Re: [VOTE] 5.0.12 stability rating
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [x] Beta
> </ballot>
It runs all examples in my upcoming JSP 2.0 book, so it looks fine to me. I
had some problems with a bundled Xerces version, but for now I consider that
an application problem rather than a container problem. If further analysis
proves otherwise, I'll let you know.
Hans
--
Hans Bergsten <ha...@gefionsoftware.com>
Gefion Software <http://www.gefionsoftware.com/>
Author of O'Reilly's "JavaServer Pages", covering JSP 1.2 and JSTL 1.0
Details at <http://TheJSPBook.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.12 stability rating
Posted by Hans Bergsten <ha...@gefionsoftware.com>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [x] Beta
> </ballot>
It runs all examples in my upcoming JSP 2.0 book, so it looks fine
to me. I had some problems with a bundled Xerces version, but for
now I consider that an application problem rather than a container
problem. If further analysis proves otherwise, I'll let you know.
Hans
--
Hans Bergsten <ha...@gefionsoftware.com>
Gefion Software <http://www.gefionsoftware.com/>
Author of O'Reilly's "JavaServer Pages", covering JSP 1.2 and JSTL 1.0
Details at <http://TheJSPBook.com/>
Re: [VOTE] 5.0.12 stability rating
Posted by Amy Roh <am...@apache.org>.
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
Amy
Re: [VOTE] 5.0.12 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> I didn't get futher reports concerning bug 21763 (and related), so I
> assume this means things improved. It would be a good idea to release a
> new 4.1.28 build once this is confirmed to also provide a fix for Tomcat
> 4.1.x.
I've had some updates on this:
- Rex Young confirmed than bug 21763 has been fixed (very cool ! Thanks
for testing).
- Ryan Lissack still experiences problems with the almost-latest (I
think it doesn't include the latest catch Throwable change) tomcat-util
from TC 5 (no thread is listening on the server socket anymore - for an
unknown reason - after a period of time, under low to medium load;
debugging traces show that the management of control runnables inside
the pool is not at fault). Ryan is using Sun 1.4.1 Server JVM under
Linux 2.4 on a 4 CPU server. I had doubts on the Sun Server VM, so he's
going to test with the IBM VM (to which he'll switch to, as it performs
faster, apparently). I hope the VM switch fixes the issue, because I
don't see any problem with the socket handling code (unless the catch
Throwable is somehow the needed fix, but there's apparently no trace in
the logs about a problem like that).
Remy
Re: [VOTE] 5.0.12 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> I didn't get futher reports concerning bug 21763 (and related), so I
> assume this means things improved. It would be a good idea to release a
> new 4.1.28 build once this is confirmed to also provide a fix for Tomcat
> 4.1.x.
I've had some updates on this:
- Rex Young confirmed than bug 21763 has been fixed (very cool ! Thanks
for testing).
- Ryan Lissack still experiences problems with the almost-latest (I
think it doesn't include the latest catch Throwable change) tomcat-util
from TC 5 (no thread is listening on the server socket anymore - for an
unknown reason - after a period of time, under low to medium load;
debugging traces show that the management of control runnables inside
the pool is not at fault). Ryan is using Sun 1.4.1 Server JVM under
Linux 2.4 on a 4 CPU server. I had doubts on the Sun Server VM, so he's
going to test with the IBM VM (to which he'll switch to, as it performs
faster, apparently). I hope the VM switch fixes the issue, because I
don't see any problem with the socket handling code (unless the catch
Throwable is somehow the needed fix, but there's apparently no trace in
the logs about a problem like that).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.12 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
I didn't get futher reports concerning bug 21763 (and related), so I
assume this means things improved. It would be a good idea to release a
new 4.1.28 build once this is confirmed to also provide a fix for Tomcat
4.1.x.
Since the amount of other outstanding issues is also very low, I think
5.0.12 should be a solid beta.
Remy
Re: [VOTE] 5.0.12 stability rating
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
I didn't get futher reports concerning bug 21763 (and related), so I
assume this means things improved. It would be a good idea to release a
new 4.1.28 build once this is confirmed to also provide a fix for Tomcat
4.1.x.
Since the amount of other outstanding issues is also very low, I think
5.0.12 should be a solid beta.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.12 stability rating
Posted by Amy Roh <am...@apache.org>.
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
Amy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.12 stability rating
Posted by Eric Carmichael <ec...@alumni.rice.edu>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] 5.0.12 stability rating
Posted by Eric Carmichael <ec...@alumni.rice.edu>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X] Beta
> </ballot>
Eric
Re: [VOTE] 5.0.12 stability rating
Posted by Jean-Francois Arcand <jf...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X ] Beta
> </ballot>
-- Jeanfrancois
Re: [VOTE] 5.0.12 stability rating
Posted by Hans Bergsten <ha...@gefionsoftware.com>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [x] Beta
> </ballot>
It runs all examples in my upcoming JSP 2.0 book, so it looks fine
to me. I had some problems with a bundled Xerces version, but for
now I consider that an application problem rather than a container
problem. If further analysis proves otherwise, I'll let you know.
Hans
--
Hans Bergsten <ha...@gefionsoftware.com>
Gefion Software <http://www.gefionsoftware.com/>
Author of O'Reilly's "JavaServer Pages", covering JSP 1.2 and JSTL 1.0
Details at <http://TheJSPBook.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[VOTE] 5.0.12 stability rating
Posted by Remy Maucherat <re...@apache.org>.
<ballot>
[ ] Alpha
[ ] Beta
</ballot>
<plea>As usual, please vote :)</plea>
Add comments if needed.
5.0.12 is similar to 5.0.11, with changes focusing on the Coyote
connector (addition of buffering at the socket layer for significantly
improved network efficiency, and two important bugfixes to the thread
pool and socket handling code). Please check it for regressions.
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[VOTE] 5.0.12 stability rating
Posted by Remy Maucherat <re...@apache.org>.
<ballot>
[ ] Alpha
[ ] Beta
</ballot>
<plea>As usual, please vote :)</plea>
Add comments if needed.
5.0.12 is similar to 5.0.11, with changes focusing on the Coyote
connector (addition of buffering at the socket layer for significantly
improved network efficiency, and two important bugfixes to the thread
pool and socket handling code). Please check it for regressions.
Remy
[VOTE] 5.0.11 stability rating
Posted by Remy Maucherat <re...@apache.org>.
<ballot>
[ ] Alpha
[ ] Beta
</ballot>
<plea>As usual, please vote :)</plea>
Add comments if needed.
5.0.11 is similar to 5.0.10 (with the exception of the commons-logging
integration). Please check it for regressions.
Remy
Re: [VOTE] 5.0.9 stability rating
Posted by Jean-Francois Arcand <jf...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [ ] Alpha
> [X ] Beta
> </ballot>
Except for validation (which I'm still investigating (try to create
smaller test case for the Xerces folks)
-- Jeanfrancois
[VOTE] 5.0.9 stability rating
Posted by Remy Maucherat <re...@apache.org>.
<ballot>
[ ] Alpha
[ ] Beta
</ballot>
<plea>As usual, please vote :)</plea>
Add comments if needed.
Remy
(sorry, this is repost, my original mail is apparently getting delayed
indefinitely :-( )