No, because if they were ran before by a crashed/stopped instance they will be
only picked again by this instance, see
JobSandbox.runByInstanceId field and its use in JobManager.poll()
That's whay I prefer the
semaphore="fail" on the related service
solution to prevent collisions and still al
Thanks Jacques. It sounds like it is good practice to have separate
"unique.instanceId" for each VM, but having separate pools are optional.
If I kill a VM, and there were outstanding jobs, will another instance
take over?
On Wed, Mar 21, 2012 at 6:28 AM, Jacques Le Roux <
jacques.le.r...@les7ar
Here is what I was thinking.
If one of the OFBiz ecommerce VM's crashes (or I restart it), would another
server take over the job? Would this work If only the pool names were all
the same for all instances?
On Wed, Mar 21, 2012 at 6:08 AM, Brett Palmer wrote:
> Mike,
>
> I posted a similar ques
From: "Mike"
Playing around with running multiple instances of OFBiz in it's own VM, in
a cloud environment, to the same DB.
I ran across this on the OpenTaps docs:
Service engine job pool:
Modify the file framework/service/config/serviceengine.xml for each of your
instances and edit the threa
Mike,
I posted a similar question a while ago on this topic. The subject
was "How to assign JobSandbox jobs to specific application server?"
In the posting I asked if different app servers could be configured to
run against different job pools in the service engine.
Here is a copy of what I pos
