Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 3.1.2.2
    • Fix Version/s: 4.1
    • Component/s: None
    • Labels:
      None

      Description

      GlassFish up to 3.1.2.2 contains some really nasty showstoppers (i. e. bugs which makes it impossible to use GlassFish under particular circumstances, and for which applying a workaround is rather complex) for which fixes do exist meanwhile. For example, some EARs do not deploy on GF 3.1.2.2, and there is a NPE in Eclipse in GF 3.1.2.2.

      As 4.0 is still far away and potentially introduces new bugs, there is a high demand in den GlassFish community to get a GF 3.1.3 rahter soon, containing all so far fixed bugs in GF itself and all of its modules.

      Please publish 3.1.3 before end of 2012!

        Activity

        Hide
        mkarg added a comment -

        Sad to see that when cloning a bug report, one cannot edit the description...

        As there had been fixes made in the 3.1.x line of GlassFish, but have not been included in 3.1.2.2, and as the embedded parts like EclipseLink also published bug fixes, the current situation is that one must manually compile and replace some parts of 3.1.2.2 to get the latest fixes.

        As the time to 4.x GA is long, I want to suggest to plan a bug fix rollup GF 3.1.2.3 in next months to make it easiert to deploy an at-most bug free GF instance without manually changing .class and .jar files.

        Show
        mkarg added a comment - Sad to see that when cloning a bug report, one cannot edit the description... As there had been fixes made in the 3.1.x line of GlassFish, but have not been included in 3.1.2.2, and as the embedded parts like EclipseLink also published bug fixes, the current situation is that one must manually compile and replace some parts of 3.1.2.2 to get the latest fixes. As the time to 4.x GA is long, I want to suggest to plan a bug fix rollup GF 3.1.2.3 in next months to make it easiert to deploy an at-most bug free GF instance without manually changing .class and .jar files.
        Hide
        shreedhar_ganapathy added a comment -

        This issue lacks crucial details of specific issues - As we are on the final build of 4.0, the fixes if any can be brought in in the next release.

        Show
        shreedhar_ganapathy added a comment - This issue lacks crucial details of specific issues - As we are on the final build of 4.0, the fixes if any can be brought in in the next release.
        Hide
        shreedhar_ganapathy added a comment -

        As the issue also points to some cases of deployment problems, assigning to Hong for tracking in the next release.

        Show
        shreedhar_ganapathy added a comment - As the issue also points to some cases of deployment problems, assigning to Hong for tracking in the next release.
        Hide
        Hong Zhang added a comment -

        Please include the details for the issues that were showstoppers and we will try to address them soon.

        Show
        Hong Zhang added a comment - Please include the details for the issues that were showstoppers and we will try to address them soon.
        Hide
        mkarg added a comment -

        The following issues are fixed but had not been included in 3.1.2.2, hence should be included in 3.1.2.3:

        (1) GF 3.1.2.2 includes EclipseLink JPA 2.3.2, which had several bugs. To make our application run well, we need patch level 2.3.4 instead which we obtained directly from the EclipseLink team as a bundle of JARs to drop into GF's modules folder. 2.3.4 was not publicly released but is existing internally at the EclipseLink team.

        (2) GF 3.1.2.2 cannot deploy some modules (see https://java.net/jira/browse/GLASSFISH-18877), so the file "ConnectorDescritpr.class" has to be patched into dol.jar manually after installing GF.

        I think it would be a great policy to always publish a bug fix release in the current release track when Publishing the first release of the next release track (i. e. 3.1.2.3 together with 4.0.0.0 here), as for safety reasons production environments will not be switched to a hot-pressed major release and soon, but are in the need of having all the lastest bug fixes.

        Show
        mkarg added a comment - The following issues are fixed but had not been included in 3.1.2.2, hence should be included in 3.1.2.3: (1) GF 3.1.2.2 includes EclipseLink JPA 2.3.2, which had several bugs. To make our application run well, we need patch level 2.3.4 instead which we obtained directly from the EclipseLink team as a bundle of JARs to drop into GF's modules folder. 2.3.4 was not publicly released but is existing internally at the EclipseLink team. (2) GF 3.1.2.2 cannot deploy some modules (see https://java.net/jira/browse/GLASSFISH-18877 ), so the file "ConnectorDescritpr.class" has to be patched into dol.jar manually after installing GF. I think it would be a great policy to always publish a bug fix release in the current release track when Publishing the first release of the next release track (i. e. 3.1.2.3 together with 4.0.0.0 here), as for safety reasons production environments will not be switched to a hot-pressed major release and soon, but are in the need of having all the lastest bug fixes.
        Hide
        Hong Zhang added a comment -

        Shreedhar: Based on the additional information the bug filer submitted, I will reassign the issue back to you.

        For the two things that have been brought up, the first item is related to EclipseLink which you can ask relevant module owner to provide information. The second item is related to deployment, but that bug was fixed in trunk already, there is not much I can do from the engineering side (I can follow up with the sustaining engineer to see if we can port the fix to the sustaining patch, but I think the patch is only available to customers with support contract so might not help the bug filer here).

        Show
        Hong Zhang added a comment - Shreedhar: Based on the additional information the bug filer submitted, I will reassign the issue back to you. For the two things that have been brought up, the first item is related to EclipseLink which you can ask relevant module owner to provide information. The second item is related to deployment, but that bug was fixed in trunk already, there is not much I can do from the engineering side (I can follow up with the sustaining engineer to see if we can port the fix to the sustaining patch, but I think the patch is only available to customers with support contract so might not help the bug filer here).
        Hide
        mkarg added a comment -

        Found one more showstopper in 3.1.2.2 unfortunately:

        https://java.net/jira/browse/GLASSFISH-20507

        Works in 3.1.1, but throws NPE in 3.1.2.2.

        Show
        mkarg added a comment - Found one more showstopper in 3.1.2.2 unfortunately: https://java.net/jira/browse/GLASSFISH-20507 Works in 3.1.1, but throws NPE in 3.1.2.2.

          People

          • Assignee:
            shreedhar_ganapathy
            Reporter:
            mkarg
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: