|
From: Bruce M. <br...@mc...> - 2003-09-21 13:44:24
|
I dont know. On Sunday 21 September 2003 09:19 am, David Glick wrote: > Hi Bruce, > > Does the SQL journal solve this problem? > > David > > On Sunday 21 September 2003 5:43 am, Bruce McDonald wrote: > > David / Davor: > > > > If your are running two instances of babeldoc (two jvms) then all is good > > - the simple journals steps do not get mixed up. The problem arises when > > you are threading, in the same pipeline for the same journal ticket, then > > the ticket steps get mixed. > > > > The issue is that the simple journal uses the strict consecutive > > provision of ticket steps to know about ordering, etc. This is a problem > > if you have multiple threads - everything is out of order... > > > > regards, > > Bruce. > > > > On Sunday 21 September 2003 12:40 am, David Glick wrote: > > > Hi Davor, > > > > > > If you are executing multiple invocations of Babeldoc from the command > > > line, each invocation is running is a separate JVM and therefore you > > > shouldn't have any problems executing the same pipeline simultaneously > > > (with the possible exception of the Journal update... Bruce, how is > > > contention handled in the case of multiple JVM copies of Babeldoc > > > trying to simultaneously update the Journal?). > > > > > > If you are executing multiple invocations in the same JVM, I believe > > > that this situation is handled via the multi-threading model Babeldoc > > > supports. The section on Multithreaded Operation in the Users Guide is > > > an excellent source of info for this situation. > > > > > > > > > Hope this helps, > > > > > > David > > > > > > On Saturday 20 September 2003 1:57 am, SourceForge.net wrote: > > > > Read and respond to this message at: > > > > https://sourceforge.net/forum/message.php?msg_id=2201154 > > > > By: dchocky > > > > > > > > Hi! > > > > > > > > > > > > > > > > I'm using Babeldoc (and Xindice XML server) to construct a simple > > > > Document Workflow System (or at least that's what we call it), as a > > > > part of my college theses. I've built a custom (RMI)feeder-wrapper > > > > for Babeldoc. > > > > > > > > The application could work ok with this feeder, but I'd like to > > > > provide an alternative way of feeding documents into the pipeline. > > > > Here's the question: > > > > > > > > Is it possible to start in one process my (or any other) feeder for > > > > Babeldoc, and in another process to start a scanner (a mailbox > > > > scanner) and should I expect any problems or do these processes work > > > > independently (concurrent access to journal?,velocity log...)? > > > > Does it become a problem if both processes are operating on the same > > > > pipeline? ...on different pipelines? > > > > I've tried this and it seems to work fine, but... > > > > > > > > > > > > > > > > Davor Cokrlic > > > > > > > > > > > > > > > > _____________________________________________________________________ > > > >_ You are receiving this email because you elected to monitor this > > > > forum. To stop monitoring this forum, login to SourceForge.net and > > > > visit: https://sourceforge.net/forum/unmonitor.php?forum_id=190909 > > > > > > > > > > > > ------------------------------------------------------- > > > > This sf.net email is sponsored by:ThinkGeek > > > > Welcome to geek heaven. > > > > http://thinkgeek.com/sf > > > > _______________________________________________ > > > > Babeldoc-devel mailing list > > > > Bab...@li... > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |