Hi Lenny,
In this case, there's no way to really know unless you test, but the
way that Payara maintains their fork is NOT by pulling in every commit
to the glassfish source code per se, but rather they "cherry pick" bug
fixes and such from the glassfish main branch and merge these into
their fork in a fairly structured manner. This keeps the payara
source a little more stable. They also maintain branches for each
maintenance release that they do... which are very stable.
If you can attach a simple war file to the glassfish jira issue along
with some steps to reproduce I'd be happy to take a little time to see
if it's reproducible on a payara build containing jersey 2.17.
Also, it looks like MarekP forwarded your mails about the problem over
to the glassfish list and RomainG has replied with some instructions
on updating jersey in glassfish 4.1.
- Phillip
On Wed, Jun 24, 2015 at 5:02 PM, Lenny Primak <lprimak_at_hope.nyc.ny.us> wrote:
> Hi, Philip,
>
> The latest Glassfish nightly as well as Payara my guess have this bug that
> is critical for our apps
> https://java.net/jira/browse/GLASSFISH-21379
>
> So even though the original jersey bug is fixed this latest bug prevents any
> kind of newer Glassfish builds to be used. I think the same applies to
> Payara.
>
>
> On Jun 24, 2015, at 1:02 PM, Phillip Ross <phillip.w.g.ross_at_gmail.com>
> wrote:
>
> Hi Lenny...
>
> You're correcet in saying that Payara is built from glassfish sources,
> but the Payara team integrates newer versions of the projects like
> Eclipselink, Jersey, Tyrus, et al... as well as bugfixes from
> glassfish into Payara. If the bug is soley based in Jersey, and has
> been fixed in jersey 2.13... then it will likely be fixed in the
> latest maintenance release of Payara. As Matyas pointed out, Payara
> has integrated jersey 2.17 in their latest maintenance release... so
> logically it would contain the bugfixes that you're referring to.
>
> I recommend downloading the latest maintenance release of Payara
> (v4.1.152.1) and seeing if you still have the problem... and if you DO
> have the problem with that version, you can log an issue on github and
> possibly get quick assistance from Payara team or community members
> without having to wait however many months/years for the next stable
> glassfish release.
>
> I think you'll be pleasantly surprised :)
>
> Hope that helps!
> - Phillip
>
> On Wed, Jun 24, 2015 at 12:35 PM, Lenny Primak <lprimak_at_hope.nyc.ny.us>
> wrote:
>
> As far as I understand Payara is built from glassfish sources.
>
> So it would have the same bug. It's a race condition and I doubt that it's
>
> fixed in Payara and not in glassfish. Also it's a high risk proposition to
>
> switch app servers for a single bug.
>
>
>
> On Jun 24, 2015, at 9:38 AM, Matyas Bene <matyas.bene_at_youstice.com> wrote:
>
>
> Why don’t you use one of the Payara builds?
>
>
> http://www.payara.co.uk/home
>
>
>
>
> Latest version includes Jersey 2.17
>
>
>
>
>
>
> From: Lenny Primak [mailto:lenny_at_flowlogix.com]
>
> Sent: Wednesday, June 24, 2015 4:36 PM
>
> To: users_at_jersey.java.net
>
> Subject: [Jersey] Instructions to upgrade current Glassfish 4.1 stable
>
>
>
>
> Hi,
>
>
>
>
> I am trying to get Jersey 2.18 working with Glassfish. I tried the nightly
>
> build, but
>
>
> it fails due to other bugs.
>
>
> Can someone let me know what the steps are to upgrade the stable GF 4.1
>
> release to Jersey 2.18?
>
>
>
>
> Specifically, I am interested in a fix for this bug:
>
>
> https://java.net/jira/browse/JERSEY-2661
>
>
> which was fixed since Jersey 2.13
>
>
> Thank you
>
>