Bug 19568699 is an Oracle internal bug#. The work around for bug
19568699 would be to use EMBEDDED or LOCAL jms-service.
Generally to report a bug, one can file an issue at
https://glassfish.java.net/ for GlassFish open source or contact Oracle
support for commercial GlassFish server
amy
On 01/08/2015 10:19 AM, MUNDT, CHRISTOPHER J CTR USAF AFWA AFWA/SEMS RM
3250-25 wrote:
> Ma'am,
>
> Yes our brokers are remote and Yes we have to use Open Source because Oracle ended Commercial support for new versions of GF.
>
> Thanks for your help. If we open a bug would any of you have a guess on how soon it could be ported to GF 4.X? If it is a long turn around then we will have to look at a different solution to fix our current problem.
>
> Is this bug listed on the Commercial Oracle side or is it on the Forum?
>
> Thanks,
> Chris
>
>
> //SIGNED//
>
> Christopher J. Mundt, Contractor, HQ AFWA/SEMSII SEMS / NORTHROP GRUMMAN Web/App Server Administrator / Software Engineer
> (402) 232-7823
> DSN 272-7823
> christopher.mundt.ctr_at_us.af.mil
>
> J2EE AppAdmin Support Info:
> J2EE.Admin_at_us.af.mil
> Cell Phone: 402-680-2179
>
>
> -----Original Message-----
> From: Amy Kang [mailto:amy.kang_at_oracle.com]
> Sent: Thursday, January 08, 2015 12:13 PM
> To: users_at_glassfish.java.net; CORDES, GREGORY M CTR USAF AFWA AFWA/SEMS RM 3250; MUNDT, CHRISTOPHER J CTR USAF AFWA AFWA/SEMS RM 3250-25
> Cc: liang.x.zhao_at_oracle.com; Nigel Deakin
> Subject: Re: [gf-users] Re: Glassfish 4.0 b89 Durable Subscriptions
>
>> I am running GF 4.0b89 in a cluster with 2 instances. I am trying to setup a Durable Subscription that previously worked under GF 2.1.1.
>> we have not been able to get this MDB to successfully establish a Durable Shared Subscription to the topic under GF 3.1.2.2, GF 4.0 build 8.9 or GF 4.1 Build 13.
> I suspect you might be using REMOTE mode jms-service for it sounds like GlassFish bug 19568699 - SHARED SUBSCRIPTIONS NOT WORKING WITH MDB TOPIC DURABLE SUBSCRIBERS
>
> which happens to REMOTE jms-service mode since 3.x but works in 2.1.1. The bug is introduced in GlassFish 3.x. 19568699 status says it's fixed in GlassFish 3.1.2.10. If that's the case and you have to use open source GlassFish, you may want to file a bug to GlassFish 4.1 and have the fix forward ported to GlassFish 4.x
>
> amy