You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Matt Hogstrom <ma...@hogstrom.org> on 2005/12/19 09:29:19 UTC
Release 1.0 Status - Release Candidate 20051219 Available for Review
The feedback on the candidate from yesterday was positive and most of the folks
reporting issues on the previous release have commented back and indicated that
those problems have been addressed. The most significant issue being the race
condition fixed by Dain as well as some console issues raised by other folks.
Thanks to all for their quick turnaround of problems and comments.
Today on e-mail and IRC there was discussion about three additional issues that
were asked to be considered for the final release. They were:
Correct a script for Windows to reduce the verbosity of the startup.
(GERONIMO-1385)
Fix a problem with Tomcat Clustering GBean (I think Jeff is opening a JIRA for
this one)
Security issue where the user requested secure pages but they were not being
honored by the server and potentially left them insecure (GERONIMO-1384).
After talking with Aaron, Jeff and John about the impacts I decided to apply
their fixes to the 1.0 branch to build and test them. My rationale was as
follows (-1's on my thinking welcome...we'll not really...but I'll accept them):
- We indicated that clustering would be available in 1.0. We knew there was an
issue and Jeff had the fix in hand. Given that we had to re-run CTS and this
fix was simple and localized I felt that it was important enough for the project
to be included.
- The security error was significant in that the user had no warning that a
requested feature would not be honored. The fix provided by Aaron effectively
detected the condition at deployment and aborted with an error message telling
the user what was wrong and to take corrective action. A better fix is planned
but was beyond the scope of 1.0 so this stop-gap is sufficient for 1.0.
- The verbose batch script on Windows was providing a lot of extra and
unnecessary information and since that is the user's first impression I felt it
was important enough to address for 1.0 and included that as well.
That said, as release manager I am officially declaring the release closed
barring TCK failures or any other serious issues. Serious in my mind means
corrupted data or intolerable outcomes.
That said, the new build is available at
http://people.apache.org/~hogstrom/geronimo-1.0 and the file names are:
geronimo-jetty-j2ee-1.0-20051219.zip
geronimo-jetty-j2ee-1.0-20051219.tar.gz
geronimo-jetty-tomcat-1.0-20051219.zip
geronimo-jetty-tomcat-1.0-20051219.tar.gz
Please take time to review the builds and provide your feedback. As noted
above, barring a catastrophe this will be the release that will go out as 1.0.
There are many additional features and fixes we want to get into the release
but we also need to get a release to our users. Assuming the TCK passes and
there is no negative feedback then we'll start a vote for the release. TCK
testing was started around 0300 EST on 12/19.
It is very important to take the 30 minutes needed to download and test the
server. Please take that precious time sooner than later :)
Matt
Re: Release 1.0 Status - Release Candidate 20051219 Available for
Review
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
Nice job with all this matt. It cant be easy.
inline...
On Dec 19, 2005, at 3:29 AM, Matt Hogstrom wrote:
>
>
> That said, as release manager I am officially declaring the release
> closed barring TCK failures or any other serious issues. Serious
> in my mind means corrupted data or intolerable outcomes.
>
How much time do you want to have people play with it? Given the
rush for the marketing deadline is passed, how about voting for a
"RC" that sits for a week for people to play with? We could even get
some notice out there on TSS et al to let people find the whoppers if
there are any left.
> That said, the new build is available at http://people.apache.org/
> ~hogstrom/geronimo-1.0 and the file names are:
>
> geronimo-jetty-j2ee-1.0-20051219.zip
> geronimo-jetty-j2ee-1.0-20051219.tar.gz
> geronimo-jetty-tomcat-1.0-20051219.zip
> geronimo-jetty-tomcat-1.0-20051219.tar.gz
>
What's the idea behind this naming scheme for the zips/tgzs?
geir
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Release 1.0 Status - Release Candidate 20051219 Available for Review
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
The JMS destination features are in fact completely broken, which is
why the links are commented out. Please don't use anything you find
to be commented out, and there's no need to report stack traces for
that particular area. :) This is something we'll look at for the
next release.
Thanks,
Aaron
On 12/19/05, Dave Whitla <da...@wotif.com> wrote:
> Testing geronimo-jetty-tomcat-1.0-20051219.tar.gz using Sun 1.4.2-10 JDK.
>
> Console application JMS destination configuration portals are completely broken.
> Add/edit functionality appears to be commented out in the JSPs. Attempts to use
> the Add/Edit URLs directly fails to create destinations.
>
> Afew other issues around JMS, I'll post some stack traces.
>
>
Re: Release 1.0 Status - Release Candidate 20051219 Available for
Review
Posted by Joe Bohn <jo...@earthlink.net>.
It appears that the ability to add queues/topics was removed during
ApacheCon because there was some concern about the functionality (I'm
not sure what that was ... but I remember some mention of problems with
persisting the queues or something).
It's pretty dangerous to just grab the URL from some commented code and
expect that it would work. Then enabled the URL would invoke an action
on the portlet which might look for information in the action request
which would not be set.
I understand that the functionality was expected in the console.
However, since it was specifically removed from the delivery I would not
call it "completely broken". Do you also get failures if you attempt
to add queues/topics outside of the admin console?
Joe
Dave Whitla wrote:
> Testing geronimo-jetty-tomcat-1.0-20051219.tar.gz using Sun 1.4.2-10 JDK.
>
> Console application JMS destination configuration portals are completely broken.
> Add/edit functionality appears to be commented out in the JSPs. Attempts to use
> the Add/Edit URLs directly fails to create destinations.
>
> Afew other issues around JMS, I'll post some stack traces.
>
>
>
--
Joe Bohn
joe.bohn@earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Release 1.0 Status - Release Candidate 20051219 Available for Review
Posted by Dave Whitla <da...@wotif.com>.
Testing geronimo-jetty-tomcat-1.0-20051219.tar.gz using Sun 1.4.2-10 JDK.
Console application JMS destination configuration portals are completely broken.
Add/edit functionality appears to be commented out in the JSPs. Attempts to use
the Add/Edit URLs directly fails to create destinations.
Afew other issues around JMS, I'll post some stack traces.
Re: Release 1.0 Status - Release Candidate 20051219 Available for Review
Posted by Paul McMahan <pa...@gmail.com>.
Jetty and tomcat tarballs look good so far on redhat. One quirky behavior I
noticed (but not a showstopper AFAICT) is that if the directory that you
start the server from is not writable then you get an error message saying
that velocity.log can't be created. I updated GERONIMO-1370 with the
appropriate info.
On 12/19/05, Dave Colasurdo < davecola@earthlink.net> wrote:
- redirect links for "additional docs" and "additional samples" are
> broken. Believe we can fix this up with the redirects at apache.org and
> doesn't require changes to the build.
The confluence links have changed, perhaps due to work on GERONIMO-1386(?).
You're correct that once the confluence links stabilize that we can update
the redirects at geronimo.apache.org without requiring changes to the build.
- As expected, the shutdown exception (GERONIMO-1371) still occurs.
> Would be nice to get this in the Release Notes if we respin for some
> other reason. Otherwise, perhaps we just have updated Release notes
> available on the download page..
I also see the shutdown exception and agree it would be nice to fix this in
the release notes if we respin. Also there is a minor typo in the release
notes at line159: "released" should be "releases".
Best wishes,
Paul
Re: Release 1.0 Status - Release Candidate 20051219 Available for
Review
Posted by Dave Colasurdo <da...@earthlink.net>.
Have downloaded and tested teh latest candidate and can offer the
following feedback:
- startup verbosity on windows is fixed..
- The latest Release note updates seem to be missing from the build. Hmm
the code change email notifications had indicated that Aaron committed
the changes.. ??
- redirect links for "additional docs" and "additional samples" are
broken. Believe we can fix this up with the redirects at apache.org and
doesn't require changes to the build.
- As expected, the shutdown exception (GERONIMO-1371) still occurs.
Would be nice to get this in the Release Notes if we respin for some
other reason. Otherwise, perhaps we just have updated Release notes
available on the download page..
- Deploying a sample application war results in a new deployment
exception for *Jetty*. This works fine for *Tomcat*.. Hadn't seen this
in previous builds..
org.apache.geronimo.common.DeploymentException: web.xml includes
security elements but Geronimo deployment plan is not provided or does
not contain <security-realm-name> and <security> elements necessary to
configured security accordingly.
at
org.apache.geronimo.jetty.deployment.JettyModuleBuilder.initContext(JettyModuleBuilder.java:426)
See the full exception stack:
http://www.rafb.net/paste/results/3aSLe566.html
Strange.. the error is shown in my console but not in the geronimo.log
file..
The war file are at:
http://svn.apache.org/repository/geronimo/wars/geronimo-servlet-examples-tomcat-5.5.12-1.war
Have attached both my Jetty and Tomcat Deployment plans.. BTW, this is
one of the default examples that we include in the distributuion. I
have changed the plan from car->war and changed the context-root as part
of the test..
Thoughts?
Thanks
-Dave-
Matt Hogstrom wrote:
>
> That said, the new build is available at
> http://people.apache.org/~hogstrom/geronimo-1.0 and the file names are:
>
> geronimo-jetty-j2ee-1.0-20051219.zip
> geronimo-jetty-j2ee-1.0-20051219.tar.gz
> geronimo-jetty-tomcat-1.0-20051219.zip
> geronimo-jetty-tomcat-1.0-20051219.tar.gz
>
> Please take time to review the builds and provide your feedback. As
> noted above, barring a catastrophe this will be the release that will go
> out as 1.0. There are many additional features and fixes we want to get
> into the release but we also need to get a release to our users.
> Assuming the TCK passes and there is no negative feedback then we'll
> start a vote for the release. TCK testing was started around 0300 EST
> on 12/19.
>
> It is very important to take the 30 minutes needed to download and test
> the server. Please take that precious time sooner than later :)
>
> Matt
>
>
>
Re: Release 1.0 Status - Release Candidate 20051219 Available for Review
Posted by Kevan Miller <ke...@gmail.com>.
As I recall, the .zip archives were going to contain text-based files
(.txt, xml, .sh, .bat) formatted for Windows (i.e. CR-LF) and tar.gz
archives would contain LF-only files. However, the two archives seem
to be identical (excepting file permissions). Text files all seem to
be LF-only, .bat files are CR-LF, and .sh files are LF-only. Perhaps
I missed a decision about the .bat and .sh files... However, .txt
files (e.g. RELEASE-NOTES-1.0.txt) are non-Notepad compatible for
Windows users... Unfortunate, but not a showstopper, IMO...
--kevan
On Dec 19, 2005, at 3:29 AM, Matt Hogstrom wrote:
> The feedback on the candidate from yesterday was positive and most
> of the folks reporting issues on the previous release have
> commented back and indicated that those problems have been
> addressed. The most significant issue being the race condition
> fixed by Dain as well as some console issues raised by other folks.
> Thanks to all for their quick turnaround of problems and comments.
>
> Today on e-mail and IRC there was discussion about three additional
> issues that were asked to be considered for the final release.
> They were:
>
> Correct a script for Windows to reduce the verbosity of the
> startup. (GERONIMO-1385)
>
> Fix a problem with Tomcat Clustering GBean (I think Jeff is opening
> a JIRA for this one)
>
> Security issue where the user requested secure pages but they were
> not being honored by the server and potentially left them insecure
> (GERONIMO-1384).
>
> After talking with Aaron, Jeff and John about the impacts I decided
> to apply their fixes to the 1.0 branch to build and test them. My
> rationale was as follows (-1's on my thinking welcome...we'll not
> really...but I'll accept them):
>
> - We indicated that clustering would be available in 1.0. We knew
> there was an issue and Jeff had the fix in hand. Given that we had
> to re-run CTS and this fix was simple and localized I felt that it
> was important enough for the project to be included.
>
> - The security error was significant in that the user had no
> warning that a requested feature would not be honored. The fix
> provided by Aaron effectively detected the condition at deployment
> and aborted with an error message telling the user what was wrong
> and to take corrective action. A better fix is planned but was
> beyond the scope of 1.0 so this stop-gap is sufficient for 1.0.
>
> - The verbose batch script on Windows was providing a lot of extra
> and unnecessary information and since that is the user's first
> impression I felt it was important enough to address for 1.0 and
> included that as well.
>
> That said, as release manager I am officially declaring the release
> closed barring TCK failures or any other serious issues. Serious
> in my mind means corrupted data or intolerable outcomes.
>
> That said, the new build is available at http://people.apache.org/
> ~hogstrom/geronimo-1.0 and the file names are:
>
> geronimo-jetty-j2ee-1.0-20051219.zip
> geronimo-jetty-j2ee-1.0-20051219.tar.gz
> geronimo-jetty-tomcat-1.0-20051219.zip
> geronimo-jetty-tomcat-1.0-20051219.tar.gz
>
> Please take time to review the builds and provide your feedback.
> As noted above, barring a catastrophe this will be the release that
> will go out as 1.0. There are many additional features and fixes
> we want to get into the release but we also need to get a release
> to our users. Assuming the TCK passes and there is no negative
> feedback then we'll start a vote for the release. TCK testing was
> started around 0300 EST on 12/19.
>
> It is very important to take the 30 minutes needed to download and
> test the server. Please take that precious time sooner than later :)
>
> Matt
>
Re: Release 1.0 Status - Release Candidate 20051219 Available for
Review
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
Nice job with all this matt. It cant be easy.
inline...
On Dec 19, 2005, at 3:29 AM, Matt Hogstrom wrote:
>
>
> That said, as release manager I am officially declaring the release
> closed barring TCK failures or any other serious issues. Serious
> in my mind means corrupted data or intolerable outcomes.
>
How much time do you want to have people play with it? Given the
rush for the marketing deadline is passed, how about voting for a
"RC" that sits for a week for people to play with? We could even get
some notice out there on TSS et al to let people find the whoppers if
there are any left.
> That said, the new build is available at http://people.apache.org/
> ~hogstrom/geronimo-1.0 and the file names are:
>
> geronimo-jetty-j2ee-1.0-20051219.zip
> geronimo-jetty-j2ee-1.0-20051219.tar.gz
> geronimo-jetty-tomcat-1.0-20051219.zip
> geronimo-jetty-tomcat-1.0-20051219.tar.gz
>
What's the idea behind this naming scheme for the zips/tgzs?
geir
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Release 1.0 Status - Release Candidate 20051219 Available for Review
Posted by anita kulshreshtha <a_...@yahoo.com>.
tomcat version works on win XP. There were few
trivial issues with the console, for which I have
opened Jira.
Thanks
Anita
--- Joe Bohn <jo...@earthlink.net> wrote:
> Looks pretty good to me on Win XP with both tomcat
> and jetty (aside from
> the problem with the links to confluence that Dave C
> already mentioned
> which we should be able to fix without a rebuild).
> +1
>
> Joe
>
> Matt Hogstrom wrote:
> > The feedback on the candidate from yesterday was
> positive and most of
> > the folks reporting issues on the previous release
> have commented back
> > and indicated that those problems have been
> addressed. The most
> > significant issue being the race condition fixed
> by Dain as well as some
> > console issues raised by other folks. Thanks to
> all for their quick
> > turnaround of problems and comments.
> >
> > Today on e-mail and IRC there was discussion about
> three additional
> > issues that were asked to be considered for the
> final release. They were:
> >
> > Correct a script for Windows to reduce the
> verbosity of the startup.
> > (GERONIMO-1385)
> >
> > Fix a problem with Tomcat Clustering GBean (I
> think Jeff is opening a
> > JIRA for this one)
> >
> > Security issue where the user requested secure
> pages but they were not
> > being honored by the server and potentially left
> them insecure
> > (GERONIMO-1384).
> >
> > After talking with Aaron, Jeff and John about the
> impacts I decided to
> > apply their fixes to the 1.0 branch to build and
> test them. My
> > rationale was as follows (-1's on my thinking
> welcome...we'll not
> > really...but I'll accept them):
> >
> > - We indicated that clustering would be available
> in 1.0. We knew there
> > was an issue and Jeff had the fix in hand. Given
> that we had to re-run
> > CTS and this fix was simple and localized I felt
> that it was important
> > enough for the project to be included.
> >
> > - The security error was significant in that the
> user had no warning
> > that a requested feature would not be honored.
> The fix provided by
> > Aaron effectively detected the condition at
> deployment and aborted with
> > an error message telling the user what was wrong
> and to take corrective
> > action. A better fix is planned but was beyond
> the scope of 1.0 so this
> > stop-gap is sufficient for 1.0.
> >
> > - The verbose batch script on Windows was
> providing a lot of extra and
> > unnecessary information and since that is the
> user's first impression I
> > felt it was important enough to address for 1.0
> and included that as well.
> >
> > That said, as release manager I am officially
> declaring the release
> > closed barring TCK failures or any other serious
> issues. Serious in my
> > mind means corrupted data or intolerable outcomes.
> >
> > That said, the new build is available at
> > http://people.apache.org/~hogstrom/geronimo-1.0
> and the file names are:
> >
> > geronimo-jetty-j2ee-1.0-20051219.zip
> > geronimo-jetty-j2ee-1.0-20051219.tar.gz
> > geronimo-jetty-tomcat-1.0-20051219.zip
> > geronimo-jetty-tomcat-1.0-20051219.tar.gz
> >
> > Please take time to review the builds and provide
> your feedback. As
> > noted above, barring a catastrophe this will be
> the release that will go
> > out as 1.0. There are many additional features
> and fixes we want to get
> > into the release but we also need to get a release
> to our users.
> > Assuming the TCK passes and there is no negative
> feedback then we'll
> > start a vote for the release. TCK testing was
> started around 0300 EST
> > on 12/19.
> >
> > It is very important to take the 30 minutes needed
> to download and test
> > the server. Please take that precious time sooner
> than later :)
> >
> > Matt
> >
> >
> >
>
> --
> Joe Bohn
> joe.bohn@earthlink.net
>
> "He is no fool who gives what he cannot keep, to
> gain what he cannot
> lose." -- Jim Elliot
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Release 1.0 Status - Release Candidate 20051219 Available for
Review
Posted by Joe Bohn <jo...@earthlink.net>.
Looks pretty good to me on Win XP with both tomcat and jetty (aside from
the problem with the links to confluence that Dave C already mentioned
which we should be able to fix without a rebuild). +1
Joe
Matt Hogstrom wrote:
> The feedback on the candidate from yesterday was positive and most of
> the folks reporting issues on the previous release have commented back
> and indicated that those problems have been addressed. The most
> significant issue being the race condition fixed by Dain as well as some
> console issues raised by other folks. Thanks to all for their quick
> turnaround of problems and comments.
>
> Today on e-mail and IRC there was discussion about three additional
> issues that were asked to be considered for the final release. They were:
>
> Correct a script for Windows to reduce the verbosity of the startup.
> (GERONIMO-1385)
>
> Fix a problem with Tomcat Clustering GBean (I think Jeff is opening a
> JIRA for this one)
>
> Security issue where the user requested secure pages but they were not
> being honored by the server and potentially left them insecure
> (GERONIMO-1384).
>
> After talking with Aaron, Jeff and John about the impacts I decided to
> apply their fixes to the 1.0 branch to build and test them. My
> rationale was as follows (-1's on my thinking welcome...we'll not
> really...but I'll accept them):
>
> - We indicated that clustering would be available in 1.0. We knew there
> was an issue and Jeff had the fix in hand. Given that we had to re-run
> CTS and this fix was simple and localized I felt that it was important
> enough for the project to be included.
>
> - The security error was significant in that the user had no warning
> that a requested feature would not be honored. The fix provided by
> Aaron effectively detected the condition at deployment and aborted with
> an error message telling the user what was wrong and to take corrective
> action. A better fix is planned but was beyond the scope of 1.0 so this
> stop-gap is sufficient for 1.0.
>
> - The verbose batch script on Windows was providing a lot of extra and
> unnecessary information and since that is the user's first impression I
> felt it was important enough to address for 1.0 and included that as well.
>
> That said, as release manager I am officially declaring the release
> closed barring TCK failures or any other serious issues. Serious in my
> mind means corrupted data or intolerable outcomes.
>
> That said, the new build is available at
> http://people.apache.org/~hogstrom/geronimo-1.0 and the file names are:
>
> geronimo-jetty-j2ee-1.0-20051219.zip
> geronimo-jetty-j2ee-1.0-20051219.tar.gz
> geronimo-jetty-tomcat-1.0-20051219.zip
> geronimo-jetty-tomcat-1.0-20051219.tar.gz
>
> Please take time to review the builds and provide your feedback. As
> noted above, barring a catastrophe this will be the release that will go
> out as 1.0. There are many additional features and fixes we want to get
> into the release but we also need to get a release to our users.
> Assuming the TCK passes and there is no negative feedback then we'll
> start a vote for the release. TCK testing was started around 0300 EST
> on 12/19.
>
> It is very important to take the 30 minutes needed to download and test
> the server. Please take that precious time sooner than later :)
>
> Matt
>
>
>
--
Joe Bohn
joe.bohn@earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot