You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Remy Maucherat <re...@apache.org> on 2003/10/20 18:33:55 UTC
New builds ?
So, what do we do with 4.1.28 ? AFAIK, no significant issue has been
found with this build, with minor tweaks being made since then in the
connectors.
Is a 4.1.29 needed, or is it simply people forgot about that build ?
OTOH, there has been a few useful fixes and tweaks since 5.0.13 in the
5.0 branch, so I'll tag a new 5.0.14 at the end of the week (these .13
builds are all cursed :-D).
Comments ?
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: New builds ?
Posted by Remy Maucherat <re...@apache.org>.
David Rees wrote:
> Remy Maucherat wrote:
>
>> David Rees wrote:
>>
>>> I've been using 4.1.29 for development without any issues for a few
>>> days now. Just one minor annoyance, I get this message twice when
>>> starting
>>> Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
>>
>>
>> Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
>> Hopefully more people will vote next time :)
>
>
> Anyone have any idea on what's causing that message from Coyote to end
> up in the cataline log file?
Well, we switched to Coyote from TC 5, so this adds a requirement on
JMX. Apparently, it does work even if JMX isn't there (I'm a bit surprised).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: New builds ?
Posted by David Rees <dr...@greenhydrant.com>.
Remy Maucherat wrote:
> David Rees wrote:
>> I've been using 4.1.29 for development without any issues for a few
>> days now. Just one minor annoyance, I get this message twice when
>> starting
>> Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
>
> Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
> Hopefully more people will vote next time :)
Anyone have any idea on what's causing that message from Coyote to end
up in the cataline log file?
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Logs folder not present in 5.0.12 (Was: Re: New builds ?)
Posted by Sriram N <sr...@yahoo.com>.
Remy:
I downloaded 5.0.12 yesterday and tried it on Linux.
I got the following error
touch: creating `/root/jakarta-tomcat-5.0.12/logs/catalina.out': No such file
or directory
/root/jakarta-tomcat-5.0.12/bin/catalina.sh: line 231:
/root/jakarta-tomcat-5.0.12/logs/catalina.out: No such file or directory
I was able to remedy this by creating the "logs" folder myself. Could you fix
this in the next release ?
-- Sriram
--- Remy Maucherat <re...@apache.org> wrote:
> David Rees wrote:
>
> > Remy Maucherat wrote:
> >
> >> So, what do we do with 4.1.28 ? AFAIK, no significant issue has been
> >> found with this build, with minor tweaks being made since then in the
> >> connectors.
> >> Is a 4.1.29 needed, or is it simply people forgot about that build ?
> >>
> >> Comments ?
> >
> >
> > I've been using 4.1.29 for development without any issues for a few days
> > now. Just one minor annoyance, I get this message twice when starting
> > Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
> >
> > Now that new versions of commons dbcp and pool have been released,
> > upgrading to the latest may be a good idea and an excuse to retag
> > 4.1.30. I don't think you'll get many testers until it's called beta,
> > though.
> >
> > Other than that, looks good!
>
> Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
> Hopefully more people will vote next time :)
>
> R�my
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: New builds ?
Posted by Remy Maucherat <re...@apache.org>.
David Rees wrote:
> Remy Maucherat wrote:
>
>> So, what do we do with 4.1.28 ? AFAIK, no significant issue has been
>> found with this build, with minor tweaks being made since then in the
>> connectors.
>> Is a 4.1.29 needed, or is it simply people forgot about that build ?
>>
>> Comments ?
>
>
> I've been using 4.1.29 for development without any issues for a few days
> now. Just one minor annoyance, I get this message twice when starting
> Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
>
> Now that new versions of commons dbcp and pool have been released,
> upgrading to the latest may be a good idea and an excuse to retag
> 4.1.30. I don't think you'll get many testers until it's called beta,
> though.
>
> Other than that, looks good!
Very good point. I'll tag new 4.1.30 and 5.0.14 builds tomorrow.
Hopefully more people will vote next time :)
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: New builds ?
Posted by David Rees <dr...@greenhydrant.com>.
Remy Maucherat wrote:
> So, what do we do with 4.1.28 ? AFAIK, no significant issue has been
> found with this build, with minor tweaks being made since then in the
> connectors.
> Is a 4.1.29 needed, or is it simply people forgot about that build ?
>
> Comments ?
I've been using 4.1.29 for development without any issues for a few days
now. Just one minor annoyance, I get this message twice when starting
Tomcat up: "CoyoteConnector Coyote can't register jmx for protocol"
Now that new versions of commons dbcp and pool have been released,
upgrading to the latest may be a good idea and an excuse to retag
4.1.30. I don't think you'll get many testers until it's called beta,
though.
Other than that, looks good!
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: New builds ?
Posted by David Rees <dr...@greenhydrant.com>.
On Fri, October 24, 2003 1at 1:27 am, Remy Maucherat wrote:
> Remy Maucherat wrote:
>>
>> OTOH, there has been a few useful fixes and tweaks since 5.0.13 in the
>> 5.0 branch, so I'll tag a new 5.0.14 at the end of the week (these .13
>> builds are all cursed :-D).
>
> Ok, tomorrow or Sunday :) (I've been a bit sick this week, so I'm slow)
Any word? ;-)
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: New builds ?
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> So, what do we do with 4.1.28 ? AFAIK, no significant issue has been
> found with this build, with minor tweaks being made since then in the
> connectors.
> Is a 4.1.29 needed, or is it simply people forgot about that build ?
>
> OTOH, there has been a few useful fixes and tweaks since 5.0.13 in the
> 5.0 branch, so I'll tag a new 5.0.14 at the end of the week (these .13
> builds are all cursed :-D).
Ok, tomorrow or Sunday :) (I've been a bit sick this week, so I'm slow)
- 5.0.14 with pool & DBCP 1.1 (and the latest fixes); I'm going to
bundle the JSR 160 RI (the license is the same as the JMX 1.2 RI), and
I'll try to add support for it using a new server listener.
- 4.1.29 also with pool & DBCP 1.1; ideally, I'll have time to add
additional connector attributes (for compression configuration, among
other things).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org