Announcement

Collapse
No announcement yet.

6.2.7 - CommitAllocUsage Object Locks

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

  • 6.2.7 - CommitAllocUsage Object Locks

    Has anyone run into an issue where OTM 6.2.7 fails to unlock a CommitAllocUsage object?

    From the log, it appears that it tries to unlock the object, fails and everything else that attempts to use that object will timeout. The only way we have found to resolve this is to restart OTM.


    Example stack trace:

    2015-01-22 17:29:13.848 318269 Error Exception java.lang.NullPointerException

    java.lang.NullPointerException
    at

    glog.server.synch.object.ObjectLock.unlockAll(Obje ctLock.java:53
    at glog.server.synch.object.TransactionObjectLock

    $LockSynchronization.afterCompletion(TransactionOb jectLock.java:82)
    at glog.util.transaction.GLTransactionHelper

    $GLSync.afterCompletion(GLTransactionHelper.java:2 96)
    at glog.util.transaction.GLTransactionHelper

    $GLSync.afterCompletion(GLTransactionHelper.java:2 83)
    at weblogic.transaction.internal.ServerSCInfo.doAfter Completion

    (ServerSCInfo.java:1023)
    at weblogic.transaction.internal.ServerSCInfo.callAft erCompletions(ServerSCInfo.java:999)


    at weblogic.transaction.internal.ServerTransactionImp l.callAfterCompletions(ServerTransactionImpl.java: 2996)
    at

    weblogic.transaction.internal.ServerTransactionImp l.afterCommittedStateHousekeeping(ServerTransactio nImpl.java:2896)
    at

    weblogic.transaction.internal.ServerTransactionImp l.setCommitted(ServerTransactionImpl.java:2941)
    at

    weblogic.transaction.internal.ServerTransactionImp l.globalRetryCommit(ServerTransactionImpl.java:272 7)
    at

    weblogic.transaction.internal.ServerTransactionImp l.globalCommit(ServerTransactionImpl.java:2646)
    at

    weblogic.transaction.internal.ServerTransactionImp l.internalCommit(ServerTransactionImpl.java:276)
    at

    weblogic.transaction.internal.ServerTransactionImp l.commit(ServerTransactionImpl.java:224)
    at

    weblogic.ejb.container.internal.BaseRemoteObject.p ostInvoke1(BaseRemoteObject.java:625)
    at

    weblogic.ejb.container.internal.StatelessRemoteObj ect.postInvoke1(StatelessRemoteObject.java:49)
    at

    weblogic.ejb.container.internal.BaseRemoteObject._ _WL_postInvokeTxRetry(BaseRemoteObject.java:445)
    at

    glog.business.shipment.ShipmentUpdateSessionHome_q j7mtr_EOImpl.commitShipmentGraph

    (ShipmentUpdateSessionHome_qj7mtr_EOImpl.java:1032 )
    at

    glog.business.action.ShipmentExecutionActionExecut or.assignProviderForRetender(ShipmentExecutionActi onExecutor.java:382)


    at glog.business.session.ShipmentExecutionActionSessi onBean.assignProviderForRetender

    (ShipmentExecutionActionSessionBean.java:107)
    at

    glog.business.session.ShipmentExecutionActionSessi onServerSideEJBWrapper.assignProviderForRetender

    (ShipmentExecutionActionSessionServerSideEJBWrappe r.java:114)
    at

    glog.business.session.ShipmentExecutionActionSessi onServerSideEJBWrapper_idwxv7_EOImpl.assignProvide rForRetender

    (ShipmentExecutionActionSessionServerSideEJBWrappe r_idwxv7_EOImpl.java:4989)
    at

    glog.server.workflow.tender.RetenderShipment$Redri ve.perform(RetenderShipment.java:343)
    at

    glog.server.workflow.Workflow.executeBody(Workflow .java:79)
    at glog.server.workflow.Workflow.execute(Workflow.jav a:51)


    at glog.server.workflow.WorkflowSessionBean.execute(W orkflowSessionBean.java:64)
    at

    glog.server.workflow.WorkflowSessionServerSideEJBW rapper.execute(WorkflowSessionServerSideEJBWrapper .java:3
    at

    glog.server.workflow.WorkflowSessionServerSideEJBW rapper_61kh96_EOImpl.execute

    (WorkflowSessionServerSideEJBWrapper_61kh96_EOImpl .java:206)
    at glog.server.workflow.WorkflowManager.execute

    (WorkflowManager.java:352)
    at glog.server.workflow.Trigger.trigger(Trigger.java: 122)
    at

    glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.java:146)
    at

    glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:9
    at glog.util.event.EventThread.run

    (EventThread.java:86)
    at java.lang.Thread.run(Thread.java:619)
    [customExecTenderReady - 41]

  • #2
    Re: 6.2.7 - CommitAllocUsage Object Locks

    I'm running into the same exact issue with OTM version 6.3.3. fails to unlock a CommitAllocUsage object until I reboot app server. Did you figure this out?

    Comment


    • #3
      Re: 6.2.7 - CommitAllocUsage Object Locks

      Seems it's a bug, we moved to 6.2.10 and it got worse. We're trying a patch they gave us to see if it resolves it.

      Comment


      • #4
        Re: 6.2.7 - CommitAllocUsage Object Locks

        Any luck with the patch for this?

        Comment


        • #5
          Re: 6.2.7 - CommitAllocUsage Object Locks

          So far, no.
          We were provided 4 additional patches, we're trying those now.

          Comment


          • #6
            Re: 6.2.7 - CommitAllocUsage Object Locks

            Do you use mviews and mview logs? I have noticed on our instance that it seems to be locking on an mlog$ table in OTM

            Comment


            • #7
              Re: 6.2.7 - CommitAllocUsage Object Locks

              We do not. Ours is related to a bug in decreasing a commitment allocation. For some reason an allocation will remain locked on a decrease after the lock was released. All further attempts to unlock it result in a NPE since the process associated with the lock no longer exists.

              Comment


              • #8
                Re: 6.2.7 - CommitAllocUsage Object Locks

                We've installed a total of 5 patches and it seems to have resolved the issue.

                Comment

                Working...
                X