Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [messaging-dev] Clarification on Jakarta Messaging 3.1 Shared Subscriptions
  • From: Ed Burns <Edward.Burns@xxxxxxxxxxxxx>
  • Date: Thu, 19 Dec 2024 22:59:16 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=RsupYCuaA0mp+ASc4nRJrgmr6mH7PvNbTaDC8mqjhgE=; b=VRnReOnzYc1O5F+fTOu5hB9xbOPqr3BXytX55eaOF9Z0DB3i/ekqz4FDbvFJ1PTsQf1Er03b0k/oLPYPs4VjYdSU7JJIxdMXqkhTM9yvoMwRZ1kELBRHDz2+lBSPSaJbIiOveJYAUHHt7qJgLfZmiQxpLDmmkHOdSkEyBL7ZoDeTIOLSAXigQoSuVF6UPh60c4stpKjgOyK/ADMFnMdvFBpOEzZsNJ9OwrDHE8zKPRudaKhnS+sZuKgRPKRfCoCUCy3GjRjznia5Lusya+y6Xf6gbCUSsRTfk+HSaibD97SX+g64Lnt1y3pbHIsFWqL+uBcU5uGw/nOS9gKRBbv2SA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=kOM1eyGwB4/IgK8HMuaxE6Gl0ppl/BoVNM4vSJXcpHIAcsNz+J+lu2EGNMrauoi2s6FEeOq8TZBN9wWYa5BVtzFykEaJdTeC7Eq7W8ijWiOBOmfrXAvjL0VZu/CngFMjDtlQlsO2p9jwY+ZkzjcSz8MjjVx2o1EhzZHcnTz0y1OLo10oMYktVFaFEOk2y9yC3D2omwHz+ewGhNLiILVmTkZ5pghjHiF/Vbq9CyUt4g3bejvdoF7vWjK3YJH9GL3/BvsQpLYW8LMQs9AHTwl8IZsLHhiBueshMmUW8ENZrhu75lAXkOPqFSy1JhDET/GnkANfgLZNAucCIuxf8/nbHg==
  • Delivered-to: messaging-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/messaging-dev/>
  • List-help: <mailto:messaging-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/messaging-dev>, <mailto:messaging-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/messaging-dev>, <mailto:messaging-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2024-12-19T22:52:17.1609017Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard
  • Thread-index: AQHbUl+vzFHXzj3B0EaBIDSHnpwrRrLuLI5K
  • Thread-topic: Clarification on Jakarta Messaging 3.1 Shared Subscriptions
Thanks for your message Patrick Deasy,

I suggest we consult the TCK Signature Tests. Do they have the createSharedConnectionConsumer and createSharedDurableConnectionConsumer on the Connection interface.

I see no reason why they would not also need to be implemented. They are specified in the normative javadoc for the specification:
https://jakarta.ee/specifications/platform/9/apidocs/jakarta/jms/connection#createSharedConnectionConsumer-jakarta.jms.Topic-java.lang.String-java.lang.String-jakarta.jms.ServerSessionPool-int-
https://jakarta.ee/specifications/platform/9/apidocs/jakarta/jms/connection#createSharedDurableConnectionConsumer-jakarta.jms.Topic-java.lang.String-java.lang.String-jakarta.jms.ServerSessionPool-int-

But both of these methods have this interesting text in their JavaDoc:

This is an expert facility not used by ordinary Jakarta Messaging clients.

This method must not be used in a Jakarta EE web or EJB application. Doing so may cause a JMSException to be thrown though this is not guaranteed.

However, this text does not mean the methods are somehow not required.

I'll defer to a messaging expert, but my read is that these methods are indeed required for compliance.

Ed

From: messaging-dev <messaging-dev-bounces@xxxxxxxxxxx> on behalf of Patrick Deasy via messaging-dev <messaging-dev@xxxxxxxxxxx>
Date: Thursday, December 19, 2024 at 13:48
To: messaging-dev@xxxxxxxxxxx <messaging-dev@xxxxxxxxxxx>
Cc: Patrick Deasy <pa-deasy@xxxxxxxxxxx>
Subject: [EXTERNAL] [messaging-dev] Clarification on Jakarta Messaging 3.1 Shared Subscriptions

You don't often get email from messaging-dev@xxxxxxxxxxx. Learn why this is important
Hello,

I seek clarification on Jakarta Messaging 3.1 and JMS 2.0 specification in relation to shared subscriptions(ref 8.3.2 and 8.3.4).

It outlines the addition of createSharedDurableConsumer and createSharedConsumer on JMSContext and Session. These need to be implemented to be Jakarta Messaging 3.1 compliant.

Connection also has createSharedConnectionConsumer and createSharedDurableConnectionConsumer methods added. Do those connection methods need to be implemented in order to be Jakarta Messaging 3.1 compliant? They are not mentioned in the spec(ref 8.3.2 and 8.3.4).

Kind regards,
Patrick

Back to the top