Bill, You've forwarded a link to documentation for an unrelated product, so I want to make sure you're doing this the ActiveMQ way and not the IBM MessageSight way. Are you saying that you configured the RetainedMessageSubscriptionRecoveryPolicy subscription recovery policy as described in http://activemq.apache.org/subscription-recovery-policy.html, and that you've also set the ActiveMQ.Retain property to true on the messages you're publishing?
Given that you're using a topic, you're right that you won't be able to see the message in the web console. But do you have at least one consumer on the topic? If so, does it receive the message as usual? If not, is the behavior any different if you redo the test with a consumer attached? Normal messages sent to a topic will just be discarded if there is no consumer for them, and I'm not sure whether that is supposed to change with retained messages. Also, that web page doesn't specify whether retained messages are supposed to survive a broker restart. If not, it would make sense for them to be stored in the memory store, which would mean that the functionality might be working even though the message isn't in the database. Have you tried subscribing a retroactive consumer to see whether the message is delivered to it? Tim On Jun 6, 2017 9:21 PM, "Bill Chen" <billc...@iii.org.tw> wrote: > Hi, Tim > > I'm not sure the retained flag is the same as the persistent flag. > About the retained flag as follows: > https://www.ibm.com/support/knowledgecenter/en/SSCGGQ_1.0. > 0/com.ibm.ism.doc/Overview/ov00033.html > > I publish to a message to a topic, not to a queue. So, I don't have any > information in that queue on the web console. Is it the cause of no message > in the database table? > > Bill > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/JDBC-persistence-for-postgresql-tp4727004p4727131.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
