it worked! Thanks! But I have a observation. When the broker starts, it shows the wrong total recovered message number from Journal. This may not be the activemq-cpp related. Can you help to verify? This happens when you cosumed all the messages, and restart the broker. It shows non-zero message recovered.
On 12/11/06, Timothy Bish (JIRA) <[EMAIL PROTECTED]> wrote:
[ https://issues.apache.org/activemq/browse/AMQCPP-23?page=comments#action_37647] Timothy Bish commented on AMQCPP-23: ------------------------------------ I've checked a fix into trunk. Seems to work for me, try it out if you can and let me know if it resolves the issue. > active-cpp persistent problem > ----------------------------- > > Key: AMQCPP-23 > URL: https://issues.apache.org/activemq/browse/AMQCPP-23 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: Stomp > Affects Versions: 1.0 > Environment: ActiveMQ 4.0.2 > activemq-cpp-1.0 > fedora 5 > Reporter: james nomingo > Assigned To: Timothy Bish > Fix For: 1.1 > > > I'm struggling with persistent option in activemq-cpp client. (my java client does the trick) > part of my code looks like: > producer->setDeliveryMode( DeliveryMode::PERSISTANT ); > The problem is after I send a message, and stop the broker. The message is gone. > If I send a lot of message exceeding the memory size the broker handles, I got resource unavailable exception. > It looks to me the message I send over using cpp doesn't instruct the broker to use persistent. > I'm using ActiveMQ 4.0.2, and activemq-cpp-1.0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira