Hi Nico,

that notification is reported when a delayed update has been finally processed.

If the cluster's parameter 'UpdateTimeout' is set to something greater than 0, the thread that initially handles the update request will wait that amount of milliseconds prior to return no matter if the update is still pending or not - the HTTP code in that case will be 204. So when the update is finally processed (in some future moment( that notification is fired to inform for the result )

so that have nothing to do with the way you send updates to the master node - in a single transaction in separate successive ones.

When an update is delayed and the initial thread is about to return HTTP 204, another notification is sent describing the situation and reporting the runtime id of that update for future reference - e.g. so one to be able to track the result - failed or success - when the above notification is sent after processing the delayed update

HTH
Damyan Ognyanov
Ontotext AD

On 11/7/2012 4:55 PM, Broccoli Nico wrote:

Hi,

in my notifications i see

"Delayed update #2149 processed !"

whats means ?

in my program :

- autocommit=false

- select /construct

- delete item

- insert same new item (with little change)

- commit

I can ?

or i have to commit the delete operation and after commit the new insert?

thanks

nico


------------------------------------------------------------------------

Le informazioni contenute nella presente e-mail potrebbero essere confidenziali e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa è vietato qualunque tipo di distribuzione o copia. Chi riceva questo messaggio per errore è pregato di inoltrarlo al mittente e di distruggere questa e-mail.

This e-mail may contain confidential information and is intended only for the use of the addressee(s) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and destroy the message.


_______________________________________________
Owlim-discussion mailing list
Owlim-discussion@ontotext.com
http://ontomail.semdata.org/cgi-bin/mailman/listinfo/owlim-discussion

_______________________________________________
Owlim-discussion mailing list
Owlim-discussion@ontotext.com
http://ontomail.semdata.org/cgi-bin/mailman/listinfo/owlim-discussion

Reply via email to