Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-3821

Exception on deploying Bing orders with low budget

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Mercury
    • Fix Version/s: Mercury
    • Labels:
      None
    • Environment:

      Tested on QA4
      Bid Manager #990

    • Sprint:
      Sprint 13

      Description

      Deployed an order to both Google and Bing with monthly budgets as $4 and $1 respectively. Bing campaigns are expected to be paused as daily budget is 0.02

      Following exception seen in the listener log,

      2015-11-25 10:33:05.532 (3) [pool-48-thread-1]: ------------Google Content Editor done
      2015-11-25 10:33:05.540 (2) [pool-3-thread-6]: Error: CampID: 4908_GM Info: Error during update request.
      2015-11-25 10:33:05.540 (2) [pool-3-thread-6]: Error: CampID: 4908_GT Info: Error during update request.
      2015-11-25 10:33:05.540 (2) [pool-3-thread-6]: Error: CampID: 4909_GM Info: Error during update request.
      2015-11-25 10:33:05.540 (2) [pool-3-thread-6]: Error: CampID: 4909_GT Info: Error during update request.
      2015-11-25 10:33:05.541 (1) [pool-3-thread-6]: Exception [Error during update request.]:java.util.concurrent.ExecutionException: java.lang.NullPointerException
      at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
      at java.util.concurrent.FutureTask.get(FutureTask.java:83)
      at com.thesearchagency.admaxlistener.deployer.MultiplexAccountDeployer.updateCampaigns(MultiplexAccountDeployer.java:305)
      at com.thesearchagency.admaxlistener.worker.CampaignUpdateWorker.call(CampaignUpdateWorker.java:106)
      at com.thesearchagency.admaxlistener.worker.AccountWorker.updateCampaigns(AccountWorker.java:530)
      at com.thesearchagency.admaxlistener.worker.AccountWorker.deploySync(AccountWorker.java:396)
      at com.thesearchagency.admaxlistener.worker.AccountWorker.call(AccountWorker.java:155)
      at com.thesearchagency.admaxlistener.worker.RequestWorker.call(RequestWorker.java:297)
      at com.thesearchagency.admaxlistener.worker.RequestWorker.call(RequestWorker.java:96)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:662)
      Caused by: java.lang.NullPointerException
      at com.thesearchagency.searchengines.bing.BingAccountDeployer.updateCampaigns(BingAccountDeployer.java:527)
      at com.thesearchagency.admaxlistener.worker.SearchEngineCampaignWorker.call(SearchEngineCampaignWorker.java:62)
      at com.thesearchagency.admaxlistener.worker.SearchEngineCampaignWorker.call(SearchEngineCampaignWorker.java:20)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      ... 5 more

      Note: When deployed with active budget (>0.05) no exception is seen in listener log.

      Bing Ads and database show the expected values for both active and inactive campaigns.

      See the attached listener log.

        Attachments

          Activity

            People

            • Assignee:
              Madhan Madhan Pulipati [X] (Inactive)
              Reporter:
              Madhan Madhan Pulipati [X] (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: