Oracle SOA Blogs- Sandeep

" If you do nothing on dispatch policies in OSB proxy or business services, all is done in the Default Workmanager. But since some constructions, not only service call-outs, need other threads to finish the job,  you can get stuck threads because the workmanager's threadpool gets empty having all or near to all threads waiting , leaving no threads to pickup work to free the others.  If all threads in the default queue become stuck, the server changes its health state to "critical. If all threads in weblogic.admin.HTTP, weblogic.admin.RMI, or a user-defined execute queue become stuck, the server changes its health state to "warning. Work Managers have a Ignore Stuck Thread options that gives the ability to execute long running jobs.  " Based on our need we can create one of following work manager's: For OSB to work optimally and prevent floading WebLogic’s threadpool with hogged/stuck threads you should create 3 FairShareRequest classes ...

Hello All, This is next step to previous blog  Purging Strategy . In this blog we will see how Oracle SOA 12C auto-purging will save our time and disk space growth on parallel processing. How to manage the growth of large numbers of flow instances, adapter reports, and fault alerts in the database with the purge scripts in  Oracle Enterprise Manager Fusion Middleware Control  or SQL*Plus, table partitioning for enabling schema tables to be range-partitioned on time intervals, and the truncate script for removing all records from runtime tables without dropping the tables. Auto-Purging in Oracle SOA 12C: Use the Auto Purge page in  Oracle Enterprise Manager Fusion Middleware Control  to schedule and execute jobs that automatically remove older flow instances, adapter reports, and fault alerts data from the database. Recommendation from Oracle: you enable automatic purging on the Auto Purge page to optimize runtime environment performance. The stat...