[MarkLogic Dev General] ML: Task Server Persistence Issue
SinghDang, Balvinder (ELS-OXF)
B.SinghDang at elsevier.com
Mon Mar 8 05:40:57 PST 2010
We are currently developing an application for storing XML Content in ML
database, and noticed couple of issues
Task Persistence Issue: Tasks queued in the Task Server do not seem to
survive a server restart. This behaviour is in contrast to JMS servers
that usually provide multiple persistence options (file journal,
Graceful Shutdown Issue: During a server shutdown, tasks being executed
by Task Server at that point (in the 4 threads) "may" not complete
execution. We checked this using a Task that takes 10sec (we used the
sleep API) to execute. ML server shuts down in about 4 secs. We noticed
that the entry into the task was logged, but the exit from the task was
not logged - suggesting that the task started execution but did not
Just wanted to check, if there is a recommended workaround from
MarkLogic to achieve message persistence? Any workaround that any of you
would have used in any of the projects.
Any help is greatly appreciated.
Elsevier Limited. Registered Office: The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom, Registration No. 1982084 (England and Wales).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the General