> > Is there a way to have a message to a DurableSubscriber delivered
> > "exactly
> > once" ??
> > In my current setup, the publisher (publishes persistent messages) and
> > the
> > listener are both using
> > AUTO_ACKNOWLEDGE but as soon as I restart the listener, all "old"
> > messages
> > are redelivered.
>
> Session.AUTO_ACKNOWLEDGE works only for non-transacted sessions. It seems
> that your subscriber sessions are transacted.
They are.
> For transacted sessions you
> must use explicit commit.
For the receiver ? Where would I put a commit() call there ?? In the
messagelistener class ?? I'm asking because
I have a commit() in the sender of course but I really can't imagine where to
put that in a receiver ?! Especially
since everything seems to work just fine (besides getting all the messages
again when you restart the receiver,
that is).
>
>
> > It would also help having a way to delete a persistent message on the
> > router
> > somehow.
>
> Setting the message time-to-live (within the message producer) is the only
> way. You must also set an appropriate clean-up interval in the
> QueueManager config.
Hmmm. Maybe you want to add a possibility to the CLI in one of the next
versions because with the current
setup here, it is required keeping the messages until the USER decides to get
rid of them.
>
Happy New Year,
S. Zwedler
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
