Closed arinban closed 14 years ago
@arinban Commented
@arinban Commented @arinban Commented
@arinban Commented @arinban Commented @glassfishrobot Commented Reported by rampsarathy
@arinban Commented @arinban Commented @glassfishrobot Commented rampsarathy said: Available in build 1.7.a with documentation
@arinban Commented @arinban Commented @glassfishrobot Commented Was assigned to rampsarathy
@arinban Commented @arinban Commented @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-27
@arinban Commented @arinban Commented @glassfishrobot Commented Marked as fixed on Sunday, September 5th 2010, 8:21:08 pm
A message driven bean that is deployed on an application server cluster is deployed on all instances of the cluster. If the bean is listening to a JMS topic destination for messages then there are N ( N is the number of instances in the cluster) separate subscribers for the same topic. This causes the same message being received and processed by all N instances in the cluster. This results in duplicay and also in-efficiency, which are some of the undesirable characteristics of reliable and highly available enterprise systems. In any production system, to achieve maximum throughput with reliability, a message should be received and processed by one and only one instance of the application in a cluster.
Environment
Operating System: All Platform: Sun
Affected Versions
[v1.5]