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

"Could not acquire lock..." issue preventing order deployment

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: Wickford
    • Fix Version/s: Wickford
    • Component/s: None
    • Labels:
      None
    • Environment:

      • BigMgr – WICKFORD-RELEASE p1
      • Core – WICKFORD_RELEASE p1
      • Reseller UI - 73
      • Merchant UI - 73
      • Sapi - 261
      • Templates - 22
      • Data Util Jar – 36

      Description

      when deploying an orders, they sometimes get stuck in the processing state. Upon further investigation, it seems as though the order update service cannot acquire a lock and therefore will not process orders or update their statuses. This error is in the tomcat logs:

      2013-09-18 12:49:36,906-59276256 [OrderScheduler_Worker-3] WARN com.thesearchagency.sapi.services.order.OrderStatusUpdateJob [] - Could not acquire lock. Will not attempt to update deployed orders in this pass.

      This error will remain until tomcat is restarted. even after tomcat is restarted, these orders remain in processing and the system will attempt to update their status. to get the orders out of processing, I have to use groovy.

      Orders currently stuck in the system:
      2013-09-18 12:48:06,217-59185567 [OrderScheduler_Worker-2] INFO com.thesearchagency.sapi.services.order.OrderService [] - Attempting to update order status for order 2e60e7ff-c713-466a-be51-ec7bb9217444
      2013-09-18 12:48:06,267-59185617 [OrderScheduler_Worker-2] INFO com.thesearchagency.sapi.services.order.OrderService [] - Attempting to update order status for order fac83cb2-0995-44ca-b218-3ea0c5ade626

        Attachments

          Activity

            People

            • Assignee:
              atul.sanagar Atul Sanagar (Inactive)
              Reporter:
              jeff.brown Jeff Brown (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: