> From: Evan Ireland [mailto:[EMAIL PROTECTED]]

> > - for all active instances listening to a Topic, how many should receive
the
> > message?
>
> One.

Then how does JMS tell a replicated listener from a regular listener?

Because based on what you're saying, JMS will magically know what listeners
should be ignored because they're redundant instances in the cluster.

> I don't believe that duplicate processing of messages sent to MDBs
> is a legitimate behaviour. Please show me where in the EJB 2.0 spec
> that it says this behaviour is permitted.

Not duplicates.  The same message, but delivered to all listeners of that
Topic.

> What it boils down to is: does your cluster present a "single
> system image" in respect of the expected JMS/EJB/MDB behaviour. If not,
you
> should probably lobby your vendor for a better implementation.

That's not the problem.  The problem is that once an MDB has started its
session and is listening to a Topic, it is a JMSListener just like everybody
else, even if it was deployed as part of a clustering strategy.

--
Cedric

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to