2 Replies Latest reply on Jan 14, 2009 11:39 AM by John Worley

    Unable to passivate due to ctx lock - JBoss 4.0.2

    Kaustuv Bhattacharya Newbie

      After the system ran a while(more than 7 days), the event log from GUI wouldn't display any more.

      By look at the corresponding log file, it shows as the following:

      2006-04-17 10:45:47,321 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.Device#findByPrimaryKey] Executing SQL: SELECT t0_Device.id, t0_Device.name, t0_Device.version, t0_Device.deviceType, t0_Device.options, t0_Device.ipAddress, t0_Device.userName, t0_Device.password, t0_Device.snmpPort, t0_Device.snmpReadCommunity, t0_Device.managed, t0_Device.deployed, t0_Device.changeStatus, t0_Device.undoConfigXml, t0_Device.syncCount FROM Device t0_Device WHERE t0_Device.id=?
      2006-04-17 10:45:47,324 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.Device] load relation SQL: SELECT DeviceFolder.folderId, Folder.name, Folder.type, Folder.data, Folder.changeStatus, Folder.undoConfigXml, Folder.syncCount, Folder.parentFolderId FROM DeviceFolder DeviceFolder, Folder Folder WHERE (DeviceFolder.folderId=Folder.id) AND ((DeviceFolder.deviceId=?))
      2006-04-17 10:45:47,326 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.Device] load relation SQL: SELECT id, sysDescr, sysName, sysContact, sysLocation, version, model, serial, maxClients, maxClientless, maxTcpBandwidth, startTimeSeconds, commStatus, localChanges, networkChanges, timestamp, currentBootLocation, changeStatus, undoConfigXml, syncCount, deviceId FROM DeviceSystemStatus WHERE (deviceId=?)
      2006-04-17 10:45:47,329 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.Device] load relation SQL: SELECT id, vvsId, vvsTag, vvsType, enableVvs, ipAddress, netmask, defaultGateway, dns1, dns2, dns3, defaultDomain, changeStatus, undoConfigXml, syncCount, deviceId FROM VvsConfig WHERE (deviceId=?)
      2006-04-17 10:45:50,119 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59d9097f000001019c1fe600d01163.]
      2006-04-17 10:45:50,119 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59d91d7f000001015f874e9b22622d.]
      2006-04-17 10:45:50,119 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59d98b7f000001009a3fdfe2a2b56a.]
      2006-04-17 10:45:50,119 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59d9a07f000001015f521d0838222b.]
      2006-04-17 10:45:50,120 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59f18f7f00000100a15988ae66c41d.]
      2006-04-17 10:45:50,120 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59f1a17f00000100ffa1ba40f9f863.]
      2006-04-17 10:45:50,120 WARN [org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx lock, id=[.1f59f1b67f0000010054694afd5b27ef.]


      Is this a JBoss problem in 4.0.2 or this can be controlled anyhow from the application? Please suggest. URGENT !!!

        • 1. Re: Unable to passivate due to ctx lock - JBoss 4.0.2
          Deepak Anupalli Newbie

          I'm seeing a similar warning message in JBoss 4.0.3 SP1, when I was trying to stress CMP beans (row-locking enabled).

          Has this warning message got something to do with the application behaviour? These messages keep coming through out the run from the begin to end. I don't see any application failures or unexpected rollbacks though.

          Test Details:
          Java client invokes a Stateless bean method that finds 2 Entity instances (picking randomly 2 PKs, rarely both could turn out to be the same PK) and performs updates on both the instances in a single transaction. (Informally this is an transfer operation randomly picking 2 accounts). This is done repeatedly with 40 threads and over a range of Entity instances(1000).

          Configuration:
          We have restricted CMP 2.x container's cache size to 200 and Stateless pool size to 100. As we have only 40 threads, atmost 40 stateless beans would be used which inturn use less than 80 entities simultaneously.

          • 2. Re: Unable to passivate due to ctx lock - JBoss 4.0.2
            John Worley Newbie

            I have run into the same error I think.
            jboss-4.0.3SP1

            [TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=cestestap/1732, BranchQual=, localId=1732] timed out. status=STATUS_ACTIVE

            [AbstractInstanceCache] Unable to passivate due to ctx lock, id=2007960

            Did you ever resolve this problem? Is it just a JBoss configuration problem or did you have to make changes to the application running on JBoss?