[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster-devel] about persistent mechanism in xmlblaster
Hello, sira) The message in the callback queue should be removed once the
acknowledge of the subscriber's update (or the fake ack from the
protocol driver) method has reached the server.
I use the persistence mechanism in XmlBlaster and have the following problem:
1) the message have been sent to subscribe succesful, and stored in database.
the problem is : when the xmlblaster server will delete the message in
b) The topic is removed when the topic expires.
c) The history entries are kept depending on what specified in the
publish qos but should also be removed once the topic is removed.
Yes it will retry until the maximum number of retries has been reached.
Thereafter it will generate a dead message and remove the entry from the
2) the xmlblaster send message to subscriber
but the subscriber's update method doesnot return RET_OK,
will the xmlBlaster Server resend the message to the failed subscriber?
3) use the persistence mechanism, when the message content is bigger
the database report error.
Mmm, sounds a limitation in the DB you are using. Could you send us the
size of the message, the DB used and the error description ?
ÖÐ¹ú×î´óµÄÃâ·ÑÓÊÏäÔÚµÈÄã 25Õ×¿Õ¼ä 4Õ×¸½¼þ£¡ http://mail.163.com
mailto:laghi at swissinfo.org
tel. +46 8 7492952 / mob. +46 70 4103964