Posted by
Florin T.PATRASCU (work) on
Feb 16, 2006; 3:58pm
URL: http://ofbiz.116.s1.nabble.com/Users-Debugging-Scheduled-Jobs-Tip-tp137457p137461.html
Hi,
The way to avoid this is to use the service engine *pool* feature that
allows each service engine instance to specify which pool it "publishes"
to by default, and which pool(s) it "subscribes" to.
excerpt from serviceengine.xml installed on a Test server:
<!-- Thread pool configuration (max/min threads, uses to live and
time to live) -->
<thread-pool send-to-pool="hobbit1"
purge-job-days="4"
....
poll-db-millis="20000">
<run-from-pool name="hobbit1"/>
</thread-pool>
while the same serviceengine config file but on a Production machine
will look different a bit:
<thread-pool send-to-pool="everest01"
....
poll-db-millis="20000">
<run-from-pool name="everest01"/>
</thread-pool>
Just make sure they have different names for your development servers
and your production servers and this problem should go away. We
encountered this issue in the past. So you can still share your db and
get advantages from that;)
I hope it helps.
-florin
PS
Sorry for my English if it is confusing :( but I believe is better than
the one Andrew Dupa is "using" ;)
Lon F. Binder wrote:
> All -
>
> After spending a few hours working through an issue, I'd like to
> provide an interesting (albeit obvious in hindsight) tip.
>
> We had two different OFBiz installations sharing the same database.
> One was a dev environment, the other was a QA environment (for the
> same target application). This led to different versions of the same
> codebase across the two environments. All in all, this was a fine
> approach for sharing the general data (store, catalog, parties, etc.).
>
> However, a consequence was overlapping job queue workers. Depending
> on the timing jobs would be worked on by the two applications
> running. And because the code base was slightly different (due to
> ongoing development), sometimes the jobs would work and sometimes they
> wouldn't.
>
> TIP: Don't let multiple OFBiz application environments (dev, qa, etc.)
> share a single OFBiz database, at least while you're
> testing/developing scheduled jobs.
>
> - Lon
>
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> Users mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/users_______________________________________________
Users mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/users