GlassFish 3.1 RC2

According to the magic decoder ring the team has now cut another Release Candidate : 3.1 RC2 is here! Get promoted build 41 from the usual page.

Starting with the first RC last week, every promoted build is really a Release Candidate. I've taken a shot at generating a query returning the bugs fixed in this RC (I'm still a JIRA newbie).

If you had installed RC1, you can use the update center to update to RC2, a simple bin/pkg image-update will do. You can also start the Update Tool (bin/updatetool) and update the GlassFish install image.


Nice to see the bug I logged finally make it into a release, at least I can now deploy stuff! (Unfortunately though jsf regressions mean I can never actually use gf3.1)

Posted by Adriaaaaan on February 07, 2011 at 06:01 PM PST #

Thanks for reporting the bug!
Do you have references to the JSF problem you are seeing?

Posted by Alexis MP on February 07, 2011 at 06:54 PM PST #

Is any PDF (RC version) documentation available anywhere online? I cannot seem to find the necessary documentation surrounding an HA configuration of OpenMQ 4.5 that's delivered as part of Glassfish 3.1

Posted by JC on February 08, 2011 at 03:48 AM PST #

Cool. Now, is there a magic decoder ring for the file naming convention?: 05-Feb-2011 18:27 56M 05-Feb-2011 18:30 38M 05-Feb-2011 18:11 32M
glassfish-3.1-web-b41-windows-ml.exe 05-Feb-2011 18:33 38M
glassfish-3.1-web-b41-windows.exe 05-Feb-2011 18:13 32M 05-Feb-2011 18:09 44M

The windows/unix part is obvious, but the presence or absence of "ml'. What does ml stand for? And do we assume that the plain unsuffixed file name means source code?

Posted by George on February 08, 2011 at 05:55 AM PST #

@George: "ml" stands for multi-lingual.
The ZIP archive is a cross-platform version while the others are installers. More details in this earlier entry :

It should all be more obvious when we post the final bits and associated web pages.

Posted by Alexis MP on February 08, 2011 at 06:14 AM PST #

Its this one,

We've been using gf3 in production since last april but this bug now means that half our buttons wont work in gf3.1. We programatically construct our own rich datatables, google map and an igoogle style dashboard using nested ui:repeat.

Because of the issues with weld in 3.0.1 we'd very much like to upgrade to 3.1!

Posted by Adriaaaaan on February 08, 2011 at 07:21 PM PST #

We are exploring using 3.1 in an upcoming project and I was trying to find some documentation but keep coming up short. Are there any plans on releasing docs prior to the finalized release for review or preview? Specifically looking at jms clustering support.



Posted by Jesse Greenwald on February 09, 2011 at 06:37 AM PST #

I think the plan of record is to ship the final documentation with the final bits.

Posted by Alexis MP on February 09, 2011 at 07:14 AM PST #

So there is no way for the public to view/review the docs before they are final?

Posted by JC on February 09, 2011 at 12:22 PM PST #

We are working hard on documentation, drafts of which are publicly posted. Feel free to review (and comment) here:

Posted by John Clingan on February 09, 2011 at 04:03 PM PST #

Is there any plans to clean up the issue tracker at some point of time? There seems to be quite a many unresolved issues in the already closed versions (1356 issues to be exact). I think in general it would be a great practice that the released versions would not contain any unresolved issues.

Posted by Syvalta on February 10, 2011 at 04:35 PM PST #

There's been quite a bit of work on the issue tracker so I was under the impression most of this work had been carried out.
Let me check and get back to you.

Posted by Alexis MP on February 10, 2011 at 05:02 PM PST #

BTW, do you have a link to the query showing those 1356 issues?

Posted by Alexis MP on February 10, 2011 at 05:07 PM PST #

For all released versions including V2:

For V3:

(had to shorten the links as direct links were detected as spam).

Posted by Syvalta on February 10, 2011 at 05:38 PM PST #

And "Unresolved by version" shows it nicely:

Posted by Syvalta on February 10, 2011 at 05:41 PM PST #

Any updates on this?

Posted by Syvalta on February 16, 2011 at 08:28 PM PST #

I've chatted about this with a few folks and clearly we will need to clean up Jira. Your link includes everything (bugs/features/tasks/etc.) and looks scary at first sight.

Looking at the seven P1/Blocker bugs, three are resolved in 3.1 and 2 or the remaining are AIX-related (not a supported platform for the time being). For the rest of them 331/381 were evaluated and excluded for 3.1, some apply to the 2.x codebase. But as I said, we have some cleaning up to do (and bug fixing too).

Thanks for bringing this to our attention!

Posted by Alexis MP on February 16, 2011 at 09:19 PM PST #

Post a Comment:
Comments are closed for this entry.