WebSVN – SmartDukaan – Diff – //trunk/profitmandi-cron/src/main/java/com/smartdukaan/cron/scheduled/ScheduledSkeleton.java

 import java.time.LocalDate;
 import java.time.LocalDateTime;
 import java.time.LocalTime;
 import java.time.YearMonth;
 import java.util.Date;
-import java.util.LinkedHashMap;
 @Component
 //@ConditionalOnProperty(name = "scheduled", havingValue = "true", matchIfMissing = true)
 public class ScheduledSkeleton {
         scheduledTasks.partnerProblemAlert();
         log.info("endTime" + LocalDateTime.now());
+    }
-    /*
-     * @Scheduled(cron = "0 30 10 * * MON-SAT") public void
-     * sendMorningAttendanceAlert() throws Throwable { log.info("startTime" +
-     * LocalDateTime.now()); LinkedHashMap<String, String> propertiesDetails = new
-     * LinkedHashMap<>(); propertiesDetails.put("sendMorningAttendanceAlert", "0");
-     * writeToPropertiesFile.saveParamChanges(propertiesDetails,
-     * nagiosCronPropertiesFile);
-     *
-     * scheduledTasks.sendAttendanceMorningAlert();
-     * propertiesDetails.put("sendMorningAttendanceAlert", "1");
-     * writeToPropertiesFile.saveParamChanges(propertiesDetails,
-     * nagiosCronPropertiesFile);
-     *
-     * log.info("endTime" + LocalDateTime.now()); }
-     *
-     * @Scheduled(cron = "0 30 20 * * MON-SAT") public void
-     * sendEveningAttendanceAlert() throws Throwable { log.info("startTime" +
-     * LocalDateTime.now()); LinkedHashMap<String, String> propertiesDetails = new
-     * LinkedHashMap<>(); propertiesDetails.put("sendEveningAttendanceAlert", "0");
-     * writeToPropertiesFile.saveParamChanges(propertiesDetails,
-     * nagiosCronPropertiesFile);
-     *
-     * scheduledTasks.sendAttendanceEveningAlert();
-     * propertiesDetails.put("sendEveningAttendanceAlert", "1");
-     * writeToPropertiesFile.saveParamChanges(propertiesDetails,
-     * nagiosCronPropertiesFile);
-     *
-     * log.info("endTime" + LocalDateTime.now()); }
-     */
     @Scheduled(cron = "0 0 10 * * *")
     public void onboardingEventDelays() throws Throwable {
         log.info("startTime" + LocalDateTime.now());
         onBoardingRelatedSchelduleTask.onboardingEventDelays();
         onBoardingRelatedSchelduleTask.brandingAlert();
         log.info("endTime" + LocalDateTime.now());
+    }
-//    @Scheduled(cron = "0 0 8 * * *")
-//    public void advancePaymentPendingAlert() throws Throwable {
-//        log.info("startTime" + LocalDateTime.now());
-//
-//        LinkedHashMap<String, String> propertiesDetails = new LinkedHashMap<>();
-//        propertiesDetails.put("advancePaymentPendingAlert", "0");
-//        writeToPropertiesFile.saveParamChanges(propertiesDetails, nagiosCronPropertiesFile);
-//
-//        onBoardingRelatedSchelduleTask.advancePaymentPendingAlert();
-//        propertiesDetails.put("advancePaymentPendingAlert", "1");
-//        writeToPropertiesFile.saveParamChanges(propertiesDetails, nagiosCronPropertiesFile);
-//
-//        log.info("endTime" + LocalDateTime.now());
-//    }
     @Scheduled(cron = "0 0 8 * * *")
     public void fullPaymentPendingAlert() throws Throwable {
         log.info("startTime" + LocalDateTime.now());
         onBoardingRelatedSchelduleTask.fullPaymentPendingAlert();
         log.info("endTime" + LocalDateTime.now());
+    }
-//    @Scheduled(cron = "0 0 9 * * *")
-//    public void advancePaymentPendinglegalAlert() throws Throwable {
-//        log.info("startTime" + LocalDateTime.now());
-//        LinkedHashMap<String, String> propertiesDetails = new LinkedHashMap<>();
-//        propertiesDetails.put("advancePaymentPendinglegalAlert", "0");
-//        writeToPropertiesFile.saveParamChanges(propertiesDetails, nagiosCronPropertiesFile);
-//
-////        onBoardingRelatedSchelduleTask.advancePaymentPendinglegalAlert();
-//
-//        propertiesDetails.put("advancePaymentPendinglegalAlert", "1");
-//        writeToPropertiesFile.saveParamChanges(propertiesDetails, nagiosCronPropertiesFile);
-//
-//        log.info("endTime" + LocalDateTime.now());
-//    }
     @Scheduled(cron = "0 */5 * * * *")
     public void onBoardingCompleteEventEmail() throws Throwable {
         log.info("startTime" + LocalDateTime.now());
         onBoardingRelatedSchelduleTask.onBoardingCompleteEventEmail();
     @Scheduled(fixedDelay = 5 * 60 * 1000)
     public void fetchPartnerStat() throws Throwable {
         scheduledTasks.fetchParnterStats();
+    }
-//    @Scheduled(cron = "0 0 9 * * *")
-//    public void storeTimelinePromoterPending() throws Throwable {
-//        log.info("startTime" + LocalDateTime.now());
-//
-//        LinkedHashMap<String, String> propertiesDetails = new LinkedHashMap<>();
-//        propertiesDetails.put("storeTimelinePromoterPending", "0");
-//        writeToPropertiesFile.saveParamChanges(propertiesDetails, nagiosCronPropertiesFile);
-//
-////        onBoardingRelatedSchelduleTask.storeTimelinePromoterPending();
-//        propertiesDetails.put("storeTimelinePromoterPending", "1");
-//        writeToPropertiesFile.saveParamChanges(propertiesDetails, nagiosCronPropertiesFile);
-//
-//        log.info("endTime" + LocalDateTime.now());
-//    }
-    //@Scheduled(cron = "0 0 23 * * *")
+    @Scheduled(cron = "0 0 23 * * *")
     public void checkItelImeiActivationNew() throws Throwable {
         log.info("startTime" + LocalDate.now());
         log.info("startTimecheckItelImeiActivation" + LocalDate.now());
         scheduledTasks.checkItelImeiActivationNew(LocalDate.now(), 90);
         long secs = (new Date().getTime()) / 1000;
         log.info("endTimecheckItelImeiActivation" + LocalDate.now());
+    }
+    /**
+     * Vivo: one full pass a day, then nothing until tomorrow.
+     *
+     * Was two parallel jobs every 5 minutes capped at 50 and 10 imeis, which never
+     * finished a pass over a 9,510-row pool and retried a failed lookup five minutes
+     * later instead of the next day. Vivo stays on its own schedule and its own thread:
+     * it is direct HTTP plus the captcha solver, no ChromeDriver, so it does not
+     * contend for the resource the oppo/realme pass is rationing.
+     *
+     * ~9,510 imeis at roughly 2.5s each is about 6.6 hours.
+     */
-    @Scheduled(fixedDelay = 5 * 60 * 1000)
+    @Scheduled(cron = "0 15 0 * * *")
     public void vivoImeiActivation() throws Throwable {
         log.info("startTimevivoImeiActivation" + LocalDateTime.now());
         scheduledTasks.checkImeiActivation();
-        long secs = (new Date().getTime()) / 1000;
-        log.info("endTimevivoImeiActivation" + LocalDateTime.now());
-    }
-    @Scheduled(fixedDelay = 5 * 60 * 1000)
-    public void vivoImeiActivationTertiary() throws Throwable {
-        log.info("startTimevivoImeiActivationTertiary" + LocalDateTime.now());
+        log.info("endTimevivoImeiActivation" + LocalDateTime.now());
-        scheduledTasks.checkImeiActivationTertiary();
-        log.info("endTimevivoImeiActivationTertiary" + LocalDateTime.now());
+    }
     @Scheduled(cron = "0 0 8 * * *")
     public void reviewUncontactablePartner() throws Throwable {
         log.info("startTime" + LocalDateTime.now());
     private StandAlone standAlone;
     @Autowired
     OrderTrackingService orderTrackingService;
+    // ONE thread, ONE full pass a day, for oppo and realme together.
+    //
+    // This replaces four @Scheduled jobs (oppo and realme x secondary and tertiary,
-    // Oppo runs its two pools in PARALLEL again (r37447 merged them; measured cost was
+    // every 5 minutes), and it supersedes the r37447 / r37448 / r37449 argument about
+    // how many ChromeDrivers to run. That argument was about the wrong variable.
+    //
-    // 5,280 -> 3,456/day because merging serialises the work, and at ~21s/imei merged
+    // The revert in r37449 was sized on lookups ATTEMPTED per day, and the re-merge that
+    // followed blamed the resulting collapse on CPU contention pushing the captcha
-    // there is no batch size or delay that reaches its target). Two drivers for oppo is
+    // render past the element waits. The logs do not support contention:
+    //
-    // the price of its throughput; realme stays merged since it has headroom.
+    //   29 Aug        imeis   canvas timeouts   captcha ok   distinct imeis   asks each
+    //   oppo          4,350                 0       ~100%            4,238        1.03
+    //   realme        4,524             3,390         19%            1,004        4.50
+    //
+    // Same box, same six cores, same driver count, same captcha vendor, load average
+    // 0.9 -- and oppo took ZERO timeouts in all 24 hours, including the 15:00-23:00
+    // window in which realme solved nothing at all. Realme's own canvas wait is 15s
-    @Scheduled(fixedDelay = 5 * 60 * 1000)
+    // against oppo's 8s, so the LONGER wait is the one expiring.
+    //
+    // What realme's timeout rate actually tracks is its own daily request volume, and
+    // it resets at midnight: 920/day -> 0.3%, 3,467/day -> 28%, 4,524/day -> 75%. That
-    public void oppo() throws Throwable {
+    // is realme.com declining to serve the widget, not a busy box.
+    //
+    // The 4.5 asks per imei is why it ran away. A failed lookup never reaches
+    // dateMap.put, so no row is written, so createTimestamp is not bumped, so the same
+    // imei was eligible again five minutes later -- more requests hardened the block,
+    // which caused more failures, which caused more requests. A snapshotted daily pass
+    // bounds that by construction: a failure costs one retry tomorrow, never one in
-        standAlone.checkOppoImeiStatus();
+    // five minutes, however the far end behaves.
-    }
+    //
+    // Judge this change on dates written, not on timeout count.
+    @Scheduled(cron = "0 30 0 * * *")
+    public void oppoRealmeImeiActivation() throws Throwable {
+        log.info("startTimeOppoRealmeImeiActivation {}", LocalDateTime.now());
-    @Scheduled(fixedDelay = 5 * 60 * 1000)
-    public void oppoTertiary() throws Throwable {
-        standAlone.checkOppoImeiStatusTertiary();
+        standAlone.checkBrowserImeiActivation();
-    }
-    // Realme unmerged too. Merging it saved a driver, but once oppo went back to two
-    // browsers realme's per-imei went 14.2s -> 29s purely from CPU contention, and at 29s
-    // its merged ceiling (86400/29 = 2,979/day) sits just under the 3,054/day the daily
-    // re-check needs -- so no batch size could close it. Two parallel pools restore the
-    // ~3,900/day it managed historically at this driver count.
-    @Scheduled(fixedDelay = 5 * 60 * 1000)
-    public void realme() throws Throwable {
-        standAlone.checkRealmeImeiStatus();
-    }
-    @Scheduled(fixedDelay = 5 * 60 * 1000)
-    public void realmeTertiary() throws Throwable {
-        standAlone.checkRealmeImeiStatusTertiary();
+        log.info("endTimeOppoRealmeImeiActivation {}", LocalDateTime.now());
+    }
     @Scheduled(cron = "0 0 * * * *")
     public void markBlueDartOrderDelivered() throws Throwable {
         log.info("startTime" + LocalDateTime.now());

Subversion Repositories SmartDukaan

(root)//trunk/profitmandi-cron/src/main/java/com/smartdukaan/cron/scheduled/ScheduledSkeleton.java – Rev 37449 → 37472