Thank you for your time Madhu.
The messages sent are persistent, the following is the rest of my setup:
A client (MessageProducer) publishing (sending) 1000 messages to a specific
topic, a MessageDrivenBean registered to that topic and subscriptionDurability
set to durable. In my MDB:s
busawreck wrote :
| When all messages have been sent but only about half of them read I kill
the application, shouldn't the messages that have not been read be in the
database then? So that the subscriber can receive them when the app restarts?
At least, that is the kind of safety I'd like
Possible anwers:
- you may have a client who's consuming them (if a message is consumed,
resepctive rows are deleted)
- you may have non-persitence messages sent
- you may be sending to a topic where no listeners exist (the messages aren't
persited unless there's a current subscriber or durable
