Browse Prior Art Database

Automatically managing the lifecycle of JavaTM Message Service (JMS) durable subscriptions within an Application Server

IP.com Disclosure Number: IPCOM000016049D
Original Publication Date: 2002-Jul-14
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 43K

Publishing Venue

IBM

Abstract

A method is disclosed for automatically managing the lifecycle of Java* Message Service (JMS) durable subscriptions within an Application Server. Application Servers provide support for Message Driven Bean (MDB) EJBs* and container managed JMS resources that create durable (persistent) JMS subscriptions to topics. These types of components are packaged into Java 2 Enterprise Edition (J2EE*) applications, which are installed or removed through administration. The durable subscriptions are registered with a broker and are persistent until such a time as they are explicitly unsubscribed. The Application Server environment provides flexible administration such that a server could be restarted with certain applications removed or modified. As a result, the server is not always aware of the removal of MDBs or container managed resources that had previously created durable JMS subscriptions and these subscriptions will still exist as far as the broker is concerned. Messages will then still be published, to local JMS queues of the Application Server, and will then accumulate on the queues because there is no longer an active subscriber retrieving messages. This method provides a new type of Application Server component that will manage the existence of these subscriptions for any JMS provider, and ensure they are unsubscribed and tidied up as appropriate. The main advantage of using this method is that it ensures correct management of persistent durable JMS subscriptions, which, if they were left to accumulate, would use up valuable JMS queue resources on the application server. A Durable Subscription Manager component is introduced within the Application Server. This component persistently manages sets of current JMS durable subscriptions owned by J2EE applications for the given Application Server. The current set of durable subscriptions for a J2EE application are persistently stored in a log file specific to that application server. When an Application Server restarts the Durable Subscription Manager performs two phases for validating the current set of durable JMS subscriptions.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

  Automatically managing the lifecycle of JavaTM Message Service (JMS) durable subscriptions within an Application Server

A method is disclosed for automatically managing the lifecycle of Java* Message Service (JMS) durable subscriptions within an Application Server.

    Application Servers provide support for Message Driven Bean (MDB) EJBs* and container managed JMS resources that create durable (persistent) JMS subscriptions to topics. These types of components are packaged into Java 2 Enterprise Edition (J2EE*) applications, which are installed or removed through administration. The durable subscriptions are registered with a broker and are persistent until such a time as they are explicitly unsubscribed. The Application Server environment provides flexible administration such that a server could be restarted with certain applications removed or modified. As a result, the server is not always aware of the removal of MDBs or container managed resources that had previously created durable JMS subscriptions and these subscriptions will still exist as far as the broker is concerned. Messages will then still be published, to local JMS queues of the Application Server, and will then accumulate on the queues because there is no longer an active subscriber retrieving messages.

    This method provides a new type of Application Server component that will manage the existence of these subscriptions for any JMS provider, and ensure they are unsubscribed and tidied up as appropriate. The main advantage of using this method is that it ensures correct management of persistent durable JMS subscriptions, which, if they were left to accumulate, would use up valuable JMS queue resources on the application server.

    A Durable Subscription Manager component is introduced within the Application Server. This component persistently manages sets of current JMS durable subscriptions owned by J2EE applications for the given Application Server. The current set of durable subscriptions for a J2EE application a...