Type	NEW
Priority	LOW
Status	CLOSED

Topic	Published messages in PtP mode can be queued by xmlBlaster if the receiver is not logged in
Des cription	If you publish a message in PtP mode and the receiver is not online, you get an exception by default. If the forceQueuing attribute is set in the publishing qos, the messages are queued by xmlBlaster. As soon as the receiver logs in, all queued messages are flushed to the receiver. Messages for a destination are stored in a queue called subject queue. The subject queue holds a reference only which points the the real message which is stored in the message store. NOTE: The login qos may disallow PtP messages, ForceQueing will be ignored then.
Example XML	<-- Publish QoS to send a message to 'joe' --> <qos> <destination queryType='EXACT' forceQueuing='true'> joe </destination> <!-- Default is no queuing --> </qos>
Configure	NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details. Columns named Impl tells you if the feature is implemented. Columns named Hot tells you if the configuration is changeable in hot operation.
See REQ	engine.qos.publish.destination.PtP
See REQ	engine.qos.publish.destination.offline
See REQ	interface.publish
See API	org.xmlBlaster.client.qos.PublishQos
See TEST	org.xmlBlaster.test.qos.TestPtDQueue

This page is generated from the requirement XML file xmlBlaster/doc/requirements/engine.qos.publish.destination.ForceQueuing.xml

Back to overview