Mr. Zhao,
I tried setting the following on my JMS Connection factory in GF 4.
subscriptionDurability Durable
subscriptionName my-name
For both of these properties I get an error in the logs "RAR7097: No setter method present for the property .... in the class com.sun.messaging.jms.ra.ManagedConnectionFactory".
When I start a single instance of Glassfish using these properties I am seeing errors in my broker logs like the following:
Entry 1: .................................... Create unshared durable subscription ..... on destination ........
Entry 2: ............. Durable subscription .... is already active on destination ................. Stack Trace
Then if I try to start a second Glassfish Instance I get errors in my Glassfish logs of:
........... Client ID is already in use ..............
Any more suggestions?
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: David Zhao [mailto:liang.x.zhao_at_oracle.com]
Sent: Saturday, November 15, 2014 2:07 AM
To: MUNDT, CHRISTOPHER J CTR USAF AFWA AFWA/SEMS RM 3250-25; users_at_glassfish.java.net
Subject: Re: [gf-users] Glassfish 4.0 b89 Durable Subscriptions
Hi Chris,
Please see if the information can help.
Thanks,
David Zhao
On 11/15/14 12:58 AM, MUNDT, CHRISTOPHER J CTR USAF AFWA AFWA/SEMS RM 3250-25 wrote:
To GF Guru's,
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.
In my connection factory I have the following Additional Properties set:
useSharedSubscriptionInClusteredContainer true
ClientId my-client-id
Under GF 2.1.1 we used the following settings but the setter functions are not available in GF 4:
DurableSubscriberName
DurableSubscriptionName
SubscriptionDurable
I am not sure where/how did you set the three properties in the old GF 2.1.1 release. But in JMS 2.0, which is implemented by GF 4, the corresponding MDB activation properties are subscriptionDurability, subscriptionName.
I removed these 3 properties that don't have setters but when my app runs in GF 4, I am getting the following 2 errors:
[2014-11-14T16:50:24.342+0000] [glassfish 4.0] [WARNING] [poolmgr.get_connection_failure] [javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors] [tid: _ThreadID=175 _ThreadName=cdfsiiEventJmsContainer-5] [timeMillis: 1415983824342] [levelValue: 900] [[
RAR5117 : Failed to obtain/create connection from connection pool [ jms/CDFSIIDataNotificationDestinationFactory-Connection-Pool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: MQRA:MC:InvalidClientIDException-[C4052]: Client ID is already in use - my-client-id user=myuser, broker=myhost:7677(65123)]]
Or
[2014-11-14T16:53:39.351+0000] [glassfish 4.0] [WARNING] [poolmgr.get_connection_failure] [javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors] [tid: _ThreadID=175 _ThreadName=cdfsiiEventJmsContainer-5] [timeMillis: 1415984019351] [levelValue: 900] [[
RAR5117 : Failed to obtain/create connection from connection pool [ jms/CDFSIIDataNotificationDestinationFactory-Connection-Pool ]. Reason : com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.]]
Is there something different in GF 4 that I need to have to enable durable subscriptions?
Regarding to MDB, please set subscriptionDurability to Durable for enabling it.
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