[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2082) JMS Topic subscriptions never released

JMS Topic subscriptions never released -------------------------------------- Key: JBSEAM-2082 URL: https://jira.jboss.org/jira/browse/JBSEAM-2082 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.0.GA, 1.2.1.GA, 2.0.0.CR1, 2.0.0.CR2, 2.0.0.CR3, 2.0.2.SP1 Environment: JBossAS 4.2.3.GA, All platforms. Reporter: Scott McNab Assignee: Norman Richards Fix For: 2.2.1.CR1 In the current Seam remoting implementation, there is no mechanism to clean up and release JMS topic subscriptions for clients that may have subscribed to a JMS topic, but who do not explicitly unsubscribe() (e.g. due to a coding error or if the client simply disappears) Unless a web-client specifically calls Seam.Remoting.unsubscribe(), the RemoteSubscriber object is never released, and the corresponding TopicSession and TopicSubscriber resources will be held open indefinitely. This will cause the JMS provider to store an ever-growing list of undelivered topic messages, which will eventually result in an out of memory crash. Seam Remoting needs to be able to correctly identify situations whereby a RemoteSubscriber is no longer in use, and release resources accordingly. One possible solution might be to periodically check all subscriptions in the SubscriptionRegistry and release any which have not had a recent poll request beyond a certain time limit.