Announcement

Collapse
No announcement yet.

Object Memory Locks

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Object Memory Locks

    Hi :

    We have a situation where order releases/Shipments are locked by OTM agents during processing. During this time updates to these order releases are queued up in the Integration queue and subsequently users are beginning to get Object Locks/Synchronous Time out errors.

    My question is :
    Is there a way we can programatically find out if an Order release/Shipment or any object is currently being locked by OTM or not ? Is there any any API ? This would definitely be a great win for us.

    I would greatly appreciate your help.

    Thanks
    J

  • #2
    Re: Object Memory Locks

    Use ObjectLock Servlet to find out what are the OR's and Shipment's are locked by OTM for what processing.
    ==============================================

    To activate a servlet, you have to enter the path of the servlet in the URL of your browser. For example, the path of the Application Properties Servlet is
    glog.webserver.properties.PropertiesServlet. If the URL of your OTM system is
    http://www.otmsystem.com/GC3/glog.we...rameGC3Servlet

    then you have to change it to

    http://www.otmsystem.com/GC3/glog.we...ockDiagServlet
    to access the servlet.
    ===============================================

    Thanks,
    Vinoth
    Thanks,
    Vinoth Gopalakrishnan
    http://www.vinoth.co/
    Reach out for OTM/GTM - Transportation/Logistics and Blockchain Consultations/Strategy

    Comment


    • #3
      Re: Object Memory Locks

      Also see http://www.otmfaq.com/forums/blogs/j...utilities.html
      --
      Joseph Liang
      MavenWire APAC
      http://www.mavenwire.com/

      Comment


      • #4
        Re: Object Memory Locks

        You can also perform a search on the Object Lock log file using the Order Release GID. Look for lines that have "Got... object" and "Release... object gid". You can determine which process/Agent has a lock by searching for timeout exception which will occur between the "Got" and the "Release of the object"

        Comment


        • #5
          Re: Object Memory Locks

          Hi,

          Anyone knows how can I automatically schedule a clean ups of the memory locks which are older than x number of days?

          I know we can schedule an object lock clean up, however I think this is for the table locks?

          Regards,
          Andi

          Comment


          • #6
            Re: Object Memory Locks

            Please have a look at OTM security guide (section - automated process). You can download it from Oracle Support.
            Regards,
            Prashant Jain
            Oracle Transport Management 6 Certified Implementation Specialist

            If my post was helpful please click on the Thanks! button

            Comment


            • #7
              Re: Object Memory Locks

              Thanks but I couldn't find that document (We're using OTM 5.5.), do you happen to have a copy of it?

              Comment


              • #8
                Re: Object Memory Locks

                Security Guide is only available in OTM 6.3 and it is only for the particular version.
                --
                Joseph Liang
                MavenWire APAC
                http://www.mavenwire.com/

                Comment


                • #9
                  Re: Object Memory Locks

                  I see.

                  We're currently have a lot of memory locks and items stuck in mediator for longer than 1 days.

                  Can anyone explain to me the role of Mediator?
                  If there is a memory lock / table lock will items in mediator be locked as well?

                  Comment


                  • #10
                    Re: Object Memory Locks

                    When you see many items are queuing in mediator (called "mediated waiters"), they are not actually locked by mediator. In fact, there must be a "holder" locking the object. Mediator constantly checks if the holder has released the lock so it can publish corresponding topics.
                    Please note that mediated locks never time out, so when you constantly see items stuck in mediator for too long it means there must be a dead lock in you workflow (e.g. two agents are updating the same object at the same time). Thus, I'd suggest you reviewing your workflow for possible dead lock.
                    --
                    Joseph Liang
                    MavenWire APAC
                    http://www.mavenwire.com/

                    Comment


                    • #11
                      Re: Object Memory Locks

                      Hi,

                      This note will guide you about object lock..

                      How to Determine if Object Lock Cleanup Has Been Scheduled [ID 1275181.1]

                      Comment


                      • #12
                        Re: Object Memory Locks

                        Hi,

                        What OTM logs can be turned ON that would help best identify the root cause of the Object lock ? Can we trace back an Object lock in OTM to a database lock (if any) ?

                        Thanks
                        J

                        Comment

                        Working...
                        X