Re: Users - Debugging Scheduled Jobs Tip

Posted by David E. Jones on Feb 16, 2006; 4:41pm
URL: http://ofbiz.116.s1.nabble.com/Users-Debugging-Scheduled-Jobs-Tip-tp137457p137462.html


Yes, this is the way to go...

We usually recommend keeping a local repository with a base set of  
code and configuration files for a "development" mode, and then  
keeping a directory with patches (in the repository) for the various  
servers. When OFBiz is deployed on each server (test, staging,  
production, perhaps multiple of each) you just check out the rev you  
want to deploy, apply the patch for that server, and build and run.  
This makes things more easy to reproduce and allows for configuration  
variations between servers.

-David


On Feb 16, 2006, at 8:58 AM, Florin T.PATRASCU (work) wrote:

> 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

 
_______________________________________________
Users mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/users