Lock release

Hi All,
I have a situation regarding locks in oracle database.
An end user is accessing a oracle database as follows :
Java Applet (Running on a Browser) <==> Oracle Forms Process ( This is created on your Oracle 6i forms server) <==> Oracle Database.
Now the end user has queried a form and did some change but has not committed yet. This creates a lock in database as FOR UPDATE OF clause is being used.
Now the end user closes the browser itself before closing the application, which leaves the form still running in the middle layer. Due to this, the lock remains in the system and this hampers the further use of the application as all other sessions hangs up. If the session is killed forcibly, this problem gets solved and other are able to use the database.
My question is, is there any way this lock can be removed automatically after some specific amount of time, if it is not released by then?
One option is to set locking mode property of the block = Deferred. But this can tell on the integrity of the system as lots of transaction happen within a short span of time using this application.
Regards
Rajesh.R

Hi Andreas,
thanks for your prompt reply.
My problem is as follows: In the planning cube, I do planning on a profit center, while the planning function checks a lookup table, which is using business units. The lookup table doesn't contain the profit center (otherwise I would have to cartesian-multiply the BU-PC entries), so the selection in the planning function filter uses a restriction on PC = #. Neither do planning function have such a thing as "constant selection". The lookup table is only being read, but I don't see how to have different restrictions on different cubes within a single planning function. My last resort would be writing an abap function to read the lookup values and then be called in the fox formula.
Regards,
Tilman

Similar Messages

  • Possible to force file lock release?

    Is there any way to force the JVM to release a lock on a certain file?
    I am reading from a BufferedReader wrapped around a FileReader. At some point, an IOException is thrown (I'm reading a file that is being written by another process, and occaisonally this will happen, but I'm handling it so it doesn't really bother me). When this happens, I can not call reader.close(), the lock never gets released, and I can never delete the file I was reading from.
    So I'm wondering if there is some way to force it to be unlocked. Ideally a static method like
    FileLock.releaseLock(File pleaseReleaseMeLetMeGo)
    ?????

    Well, I do call it, but I'm sure it is throwing an exception (I have a try/catch around just that one call in the IOException handler).
    I'm doing this on windows. The only solution I can come up with so far is to launch a separate Java process to shutdown the current process and then delete the file and restart the process in question (it needs to be running continuously). This seems like a really dirty hack though and unnecessarily complicates the program.
    Also, it may be possible to open the file I want to delete for writing. I don't really have to delete it, I just want to overwrite what's in it. Sometimes it seems that Java will let you re-write a file even though it won't let you delete it...

  • Lock release inside of update process

    Hi All,
    Is there any way to release (dequeue) a lock inside of an update process that was originally created inside of the dialog process (with scope 2)?
    It appears to me that since they are separate processes, they have separate lock owners and therefore itu2019s impossible for the update process to release it.
    There must be a way...

    ...Or maybe there isn't a way...

  • Object lock release

    Hi experts,
                  How to release object lock like  BOM TROLLEY 1 MDU 1 is locked by user  ,
                Even  after closing all the screens relevent to that BOM , the problem exist .
    how to rectify this
    Regards
    s.suresh kanna

    hi
    this might be becosue of lock entries,
    check form SM12 and delete them
    -ashok

  • Admin console lock&release button monitoring

    Hi!
    Need some help here.
    Is there any way to log or trace when and by which IP lock-button was enabled in adminstration console?
    Thanks.

    I suppose access.log from .../domain/servers/AdminServer can be helpful for my case. Unfortunately it contains only certain logs:
    #Version: 1.0
    #Fields: time cs-method cs-uri sc-status c-ip cs-uri-stem cs-uri-query
    #Software: WebLogic
    #Start-Date: 2013-01-09 11:22:59
    12:49:49 GET /bea_wls_deployment_internal/DeploymentService 200 x.x.x.38 /bea_wls_deployment_internal/DeploymentService -
    12:55:28 GET / 404 10.7.62.38 / -
    13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:02:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    13:11:16 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:19:25 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:21:52 GET /bea_wls_management_internal2/wl_management 200 x.x.x.163 /bea_wls_management_internal2/wl_management -
    15:22:00 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:22:03 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:22:04 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:23:38 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:25:53 GET /favicon.ico 404 x.x.x.38 /favicon.ico -
    15:26:03 GET /favicon.ico 404 x.x.x.38 /favicon.ico -
    15:56:30 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    15:56:31 POST /bea_wls_deployment_internal/DeploymentService 200 x.x.x.163 /bea_wls_deployment_internal/DeploymentService -
    and no messages about logging in or something like that.
    What should I do to see them?

  • When is synch lock released

    Hi, I have a question.
    When is the static synchLock released in the following case:
    A thread calls a static non-synchronized method. That method calls a static synchronized method.
    So, when is the static synchLock released? After thread leaves synchronized method or after it leaves non-synchronized method?
    Thanks a lot,
    --MB
    Message was edited by:
    Massive.Boisson

    You need a little common sense here.

  • Automatic Locking of Production Order on release

    Dear Experts,
    When the production order is released, the order should be "Locked" automatically. When changes are required, the production order is unlocked manually and changes are done. This is our requirement.
    Is it possible to lock the order on release.
    If yes what are the settings?
    Regards,
    Jejesh

    Hi,
    Go to T.code BS02.
    - Create new Status Profile , if required do it by copy any standard one.
    - Then go to Detail screen.
    - Assign order status.For your reference I have used 2 order status.
    - CRTD - Created.Set this one as Initial one.
    - LOCK - Release and Locked.
    - Now assign Object type to this status Profile.You have to select PP/PM Order Header.
    - Now double click on Status CRTD and press New Entry tab to find and set allowed Transection.Here you have to select and restrict transaction types this status.
    - Now go to Status LOCK and double click.Then press New Entry tab.You will find the list of transactions.
    First select Transaction Release and make it as allowed and also activate radio button for Set.It will activate the status LOCK automatically after release of order.
    - Now make forbidden of all other transactions like change of order,Confirmations etc. as per your suitability.
    - You can assign any other user status also for further transaction control.
    - Then save your status profile.
    - Now assign this Status Profile to Order type using T.code OPJH.
    Regards,
    Dhaval

  • Releasing table locks when user closes browser

    Hi, I've read the blogs and tried some of the code that people have suggested but it just never seems to work.  I have locked table entries belonging to a stateful 2003 BSP.  The user closes the browser by means of the 'X' and the table locks remain.  I have table lock releases in the 'OnDestroy' event but that never seems to occur.  I have tried inserting JavaScript to capture the closing of the window but either it captures every other event or it gets confused when navigating to another page.  I have the redirect examples however they all seem to be part of a proper logoff procedure, rather than the cowboy approach of just shutting down the browser.  There must be a simple procedure out there to do this.  Is there a complete example somewhere?
    Any help will be appreciated,
    Kevin

    Hi Raja, ok I discovered why it isn't working and it really is quite obvious.  The browser that it's being tested on has a Google toolbar installed. Among other things this toolbar allows users to block the display of popups.  If this is selected the script will not run properly as it needs the alert to allow the server side to run.  This is going to be frustrating because while most of the user's desktop is managed by the corporation they still have the ability to add toolbars to their browsers and configure them, and I'm sure most people will select the popup blocker. 
    Kevin

  • Locking in EntityFramework - calling empty stored procedure releases lock acquired using sp_getapplock

    I have a patient table in the SQL Server database. Clients connect to the database and checkout one of the patients and do some operations on it and save it afterwards.
    Since multiple clients might access the patient at the same time. I wanted to implement pessimistic locking mechanism, So that if one client can acquire a lock to a particular patient at a time.
    Also if one of the clients locks a particular patient and either crashes or closes the client application the lock should be released. In case of crash the lock should be released when we detect that the connection of client with the database is closed.
    I found out that I could use sp_getapplock and sp_releaseapplock to
    do achieve this and specify @LockOwner
    = 'Session' when calling sp_getapplock,
    this ensures that the lock is released once the database session with the client closes.
    From the code, I call a stored procedure in database to acquire the lock. This acquires the lock correctly and if i close off the client app or the client app crashes the lock is released. This is behaving as I wanted it to.
    The problem happens when I call another stored procedure which is supposed to release the lock. As soon as the stored procedure is entered the lock is released, before we even execute sp_releaseapplock
    @patientId, @LockOwner = 'Session' the line which is actually supposed to release the lock.
    I tried creating an empty stored procedure (just commented out
    DECLARE @result int
    EXEC @result = sp_releaseapplock @patientId, @LockOwner = 'Session'
    This stored procedure still releases the lock I acquired using sp_getapplock.
    I can't seem to understand why this is happening. It should only release when I explicitly call `sp_releaseapplock @patientId, @LockOwner = 'Session'``
    CREATE PROCEDURE [dbo].[uspReleaseAppLock]
    @patientId nvarchar(max), -- Patient ID
    @ReturnValue int Output
    AS
    BEGIN
    DECLARE @result int
    EXEC @result = sp_releaseapplock @patientId, @LockOwner = 'Session'
    SET @ReturnValue = @@SPID
    END
    Could someone tell me why this is happening. What am I missing here ? I checked that the session ids of both the stored procedures (for acquiring and releasing the lock) are same, so it dose not seem that a new session is being created by entity frame work
    for each call to the stored procedure. Something else is going on which I am not able to comprehend. Any ideas ?

    Hi oalvi,
    The Stored Procedure(SP) sp_getApplock initialed with "@LockOwner='Session'" is
    session scoped. Your procedure
    [dbo].[uspReleaseAppLock]
    did the same work as you explicitly call "sp_releaseapplock @Resource = @patientId, @LockOwner='Session'", after the SP
    uspReleaseAppLock
    called or the current session ends, the lock released.
    It doesn't make sense to call the uspReleaseAppLock to release the lock initialized in another session. If you try, you get the error like below, as I mentioned, the lock is session scoped.
    "Cannot release the application lock (Database Principal: 'public', Resource: 'patient1') because it is not currently
    held"
    Regarding the same session ID you get from calling 2 SPs separately in Entity Framework(EF). As per my limitation knowledge on EF, If the maxsize of the project connection
    pool equals 1, you may get the same session always.
    Some cautions for sp_getApplock
    Locks can be explicitly released with sp_releaseapplock. When an application calls sp_getapplock multiple times for the same lock resource, sp_releaseapplock must be called the same number of times to release the lock.
    Due to the connection pool, the sessions may last long, that's what you need to take into account.
    By the way, is there any reason that you have to use the sp_getApplock? What is the procedure doing that you cannot rely on SQL Servers build-in concurrency control mechanisms?
    If you have any question, feel free to let me know.
    Eric Zhang
    TechNet Community Support

  • Transaction in TaskFlow and locking

    Hello
    I'm using JDeveloper 11g 11.1.2.1.0
    I came across strange (in my opinion) behaviour of the transaction option inside taskFlow: if taskFlow's transaction option set as something other than "<No Controller Transaction>" (for example, "Use Existing Transaction if Possible"), then taskFlow always use the pessimistic Locking Mode (not depend what is set in adf-config's "Locking Mode").
    I have done simple test.
    There is the table in Oracle database, the entity and the editable view object in the Model project.
    There is one jsf page inside the view project. Inside that jsf page - one bounded taskFlow with one page fragment with simple edit form bounded to View Object from Model project.
    adf-config: "Locking Mode" - "Optimistic"
    Application Module: LocalConfiguration, jbo.locking.mode = 'optimistic'
    TaskFlow: transaction - "Use Existing Transaction if Possible"
    I run the application and after the form SUBMIT (with comandButton or autosubmit="true") I see next log:
    <ADFLogger> <begin> Lock Entity
    <OracleSQLBuilderImpl> <doEntitySelectForAltKey> [600] (125) OracleSQLBuilderImpl.doEntitySelectForAltKey(672) OracleSQLBuilder Executing doEntitySelect on: SAR_TEST.SAR_REPORTS (true)
    <ADFLogger> <begin> Entity read all attributes
    <OracleSQLBuilderImpl> <buildSelectString> [601] (0) OracleSQLBuilderImpl.buildSelectString(2808) Built select: 'SELECT REPORT_ID, PERIOD_DATE, TEMPLATE_ID, SHOP_ID, EDIT_DATE, STATUS, USER_LOGIN, SAVE_COUNTER FROM SAR_TEST.SAR_REPORTS ReportEO'
    <OracleSQLBuilderImpl> <doEntitySelectForAltKey> [602] (0) OracleSQLBuilderImpl.doEntitySelectForAltKey(782) Executing LOCK...SELECT REPORT_ID, PERIOD_DATE, TEMPLATE_ID, SHOP_ID, EDIT_DATE, STATUS, USER_LOGIN, SAVE_COUNTER FROM SAR_TEST.SAR_REPORTS ReportEO WHERE REPORT_ID=:1 FOR UPDATE NOWAIT
    <ADFLogger> <addContextData> Entity read all attributes
    <OracleSQLBuilderImpl> <bindWhereAttrValue> [603] (0) OracleSQLBuilderImpl.bindWhereAttrValue(2296) Where binding param 1: 287
    <ADFLogger> <addContextData> Entity read all attributes
    <ADFLogger> <end> Entity read all attributes
    <ADFLogger> <end> Lock EntitySo, I have "Executing LOCK..." with "FOR UPDATE NOWAIT"
    Record is locked on the database level, and it's impossible to edit it from other session
    If I set taskFlow's transaction to "<No Controller Transaction>" - I do not have any locking.
    So, what is the relations between adf-config: "Locking Mode" and taskFlow's transaction control?
    As I understood I should never use taskFlow's transaction control if I want to have on optimistic locking mode through an application.
    Is this an error?
    Anatolii

    Frank, thank for replay
    I don't understand why the update of the record in database happens. I don't execute commit, I perform the form submit (I want to update the model only, not database records), and during this sumbmit operation the database record's update happens.
    Neither of commit and rollback happen, and record remain locked.
    And I have FOR UPDATE NOWAIT in this situation even with adf-config: "Locking Mode" - "none" or "Optupdate". Why?
    Where did you see that lock released after update?
    Anatolii
    Edited by: Anatolii. on 12.01.2012 7:57
    Edited by: Anatolii. on 12.01.2012 8:00

  • BDB read performance problem: lock contention between GC and VM threads

    Problem: BDB read performance is really bad when the size of the BDB crosses 20GB. Once the database crosses 20GB or near there, it takes more than one hour to read/delete/add 200K keys.
    After a point, of these 200K keys there are about 15-30K keys that are new and this number eventually should come down and there should not be any new keys after a point.
    Application:
    Transactional Data Store application. Single threaded process, that's trying to read one key's data, delete the data and add new data. The keys are really small (20 bytes) and the data is large (grows from 1KB to 100KB)
    On on machine, I have a total of 3 processes running with each process accessing its own BDB on a separate RAID1+0 drive. So, according to me there should really be no disk i/o wait that's slowing down the reads.
    After a point (past 20GB), There are about 4-5 million keys in my BDB and the data associated with each key could be anywhere between 1KB to 100KB. Eventually every key will have 100KB data associated with it.
    Hardware:
    16 core Intel Xeon, 96GB of RAM, 8 drive, running 2.6.18-194.26.1.0.1.el5 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
    BDB config: BTREE
    bdb version: 4.8.30
    bdb cache size: 4GB
    bdb page size: experimented with 8KB, 64KB.
    3 processes, each process accesses its own BDB on a separate RAIDed(1+0) drive.
    envConfig.setAllowCreate(true);
    envConfig.setTxnNoSync(ourConfig.asynchronous);
    envConfig.setThreaded(true);
    envConfig.setInitializeLocking(true);
    envConfig.setLockDetectMode(LockDetectMode.DEFAULT);
    When writing to BDB: (Asynchrounous transactions)
    TransactionConfig tc = new TransactionConfig();
    tc.setNoSync(true);
    When reading from BDB (Allow reading from Uncommitted pages):
    CursorConfig cc = new CursorConfig();
    cc.setReadUncommitted(true);
    BDB stats: BDB size 49GB
    $ db_stat -m
    3GB 928MB Total cache size
    1 Number of caches
    1 Maximum number of caches
    3GB 928MB Pool individual cache size
    0 Maximum memory-mapped file size
    0 Maximum open file descriptors
    0 Maximum sequential buffer writes
    0 Sleep after writing maximum sequential buffers
    0 Requested pages mapped into the process' address space
    2127M Requested pages found in the cache (97%)
    57M Requested pages not found in the cache (57565917)
    6371509 Pages created in the cache
    57M Pages read into the cache (57565917)
    75M Pages written from the cache to the backing file (75763673)
    60M Clean pages forced from the cache (60775446)
    2661382 Dirty pages forced from the cache
    0 Dirty pages written by trickle-sync thread
    500593 Current total page count
    500593 Current clean page count
    0 Current dirty page count
    524287 Number of hash buckets used for page location
    4096 Assumed page size used
    2248M Total number of times hash chains searched for a page (2248788999)
    9 The longest hash chain searched for a page
    2669M Total number of hash chain entries checked for page (2669310818)
    0 The number of hash bucket locks that required waiting (0%)
    0 The maximum number of times any hash bucket lock was waited for (0%)
    0 The number of region locks that required waiting (0%)
    0 The number of buffers frozen
    0 The number of buffers thawed
    0 The number of frozen buffers freed
    63M The number of page allocations (63937431)
    181M The number of hash buckets examined during allocations (181211477)
    16 The maximum number of hash buckets examined for an allocation
    63M The number of pages examined during allocations (63436828)
    1 The max number of pages examined for an allocation
    0 Threads waited on page I/O
    0 The number of times a sync is interrupted
    Pool File: lastPoints
    8192 Page size
    0 Requested pages mapped into the process' address space
    2127M Requested pages found in the cache (97%)
    57M Requested pages not found in the cache (57565917)
    6371509 Pages created in the cache
    57M Pages read into the cache (57565917)
    75M Pages written from the cache to the backing file (75763673)
    $ db_stat -l
    0x40988 Log magic number
    16 Log version number
    31KB 256B Log record cache size
    0 Log file mode
    10Mb Current log file size
    856M Records entered into the log (856697337)
    941GB 371MB 67KB 112B Log bytes written
    2GB 262MB 998KB 478B Log bytes written since last checkpoint
    31M Total log file I/O writes (31624157)
    31M Total log file I/O writes due to overflow (31527047)
    97136 Total log file flushes
    686 Total log file I/O reads
    96414 Current log file number
    4482953 Current log file offset
    96414 On-disk log file number
    4482862 On-disk log file offset
    1 Maximum commits in a log flush
    1 Minimum commits in a log flush
    160KB Log region size
    195 The number of region locks that required waiting (0%)
    $ db_stat -c
    7 Last allocated locker ID
    0x7fffffff Current maximum unused locker ID
    9 Number of lock modes
    2000 Maximum number of locks possible
    2000 Maximum number of lockers possible
    2000 Maximum number of lock objects possible
    160 Number of lock object partitions
    0 Number of current locks
    1218 Maximum number of locks at any one time
    5 Maximum number of locks in any one bucket
    0 Maximum number of locks stolen by for an empty partition
    0 Maximum number of locks stolen for any one partition
    0 Number of current lockers
    8 Maximum number of lockers at any one time
    0 Number of current lock objects
    1218 Maximum number of lock objects at any one time
    5 Maximum number of lock objects in any one bucket
    0 Maximum number of objects stolen by for an empty partition
    0 Maximum number of objects stolen for any one partition
    400M Total number of locks requested (400062331)
    400M Total number of locks released (400062331)
    0 Total number of locks upgraded
    1 Total number of locks downgraded
    0 Lock requests not available due to conflicts, for which we waited
    0 Lock requests not available due to conflicts, for which we did not wait
    0 Number of deadlocks
    0 Lock timeout value
    0 Number of locks that have timed out
    0 Transaction timeout value
    0 Number of transactions that have timed out
    1MB 544KB The size of the lock region
    0 The number of partition locks that required waiting (0%)
    0 The maximum number of times any partition lock was waited for (0%)
    0 The number of object queue operations that required waiting (0%)
    0 The number of locker allocations that required waiting (0%)
    0 The number of region locks that required waiting (0%)
    5 Maximum hash bucket length
    $ db_stat -CA
    Default locking region information:
    7 Last allocated locker ID
    0x7fffffff Current maximum unused locker ID
    9 Number of lock modes
    2000 Maximum number of locks possible
    2000 Maximum number of lockers possible
    2000 Maximum number of lock objects possible
    160 Number of lock object partitions
    0 Number of current locks
    1218 Maximum number of locks at any one time
    5 Maximum number of locks in any one bucket
    0 Maximum number of locks stolen by for an empty partition
    0 Maximum number of locks stolen for any one partition
    0 Number of current lockers
    8 Maximum number of lockers at any one time
    0 Number of current lock objects
    1218 Maximum number of lock objects at any one time
    5 Maximum number of lock objects in any one bucket
    0 Maximum number of objects stolen by for an empty partition
    0 Maximum number of objects stolen for any one partition
    400M Total number of locks requested (400062331)
    400M Total number of locks released (400062331)
    0 Total number of locks upgraded
    1 Total number of locks downgraded
    0 Lock requests not available due to conflicts, for which we waited
    0 Lock requests not available due to conflicts, for which we did not wait
    0 Number of deadlocks
    0 Lock timeout value
    0 Number of locks that have timed out
    0 Transaction timeout value
    0 Number of transactions that have timed out
    1MB 544KB The size of the lock region
    0 The number of partition locks that required waiting (0%)
    0 The maximum number of times any partition lock was waited for (0%)
    0 The number of object queue operations that required waiting (0%)
    0 The number of locker allocations that required waiting (0%)
    0 The number of region locks that required waiting (0%)
    5 Maximum hash bucket length
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Lock REGINFO information:
    Lock Region type
    5 Region ID
    __db.005 Region name
    0x2accda678000 Region address
    0x2accda678138 Region primary address
    0 Region maximum allocation
    0 Region allocated
    Region allocations: 6006 allocations, 0 failures, 0 frees, 1 longest
    Allocations by power-of-two sizes:
    1KB 6002
    2KB 0
    4KB 0
    8KB 0
    16KB 1
    32KB 0
    64KB 2
    128KB 0
    256KB 1
    512KB 0
    1024KB 0
    REGION_JOIN_OK Region flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Lock region parameters:
    524317 Lock region region mutex [0/9 0% 5091/47054587432128]
    2053 locker table size
    2053 object table size
    944 obj_off
    226120 locker_off
    0 need_dd
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Lock conflict matrix:
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Locks grouped by lockers:
    Locker Mode Count Status ----------------- Object ---------------
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Locks grouped by object:
    Locker Mode Count Status ----------------- Object ---------------
    Diagnosis:
    I'm seeing way to much lock contention on the Java Garbage Collector threads and also the VM thread when I strace my java process and I don't understand the behavior.
    We are spending more than 95% of the time trying to acquire locks and I don't know what these locks are. Any info here would help.
    Earlier I thought the overflow pages were the problem as 100KB data size was exceeding all overflow page limits. So, I implemented duplicate keys concept by chunking of my data to fit to overflow page limits.
    Now I don't see any overflow pages in my system but I still see bad bdb read performance.
    $ strace -c -f -p 5642 --->(607 times the lock timed out, errors)
    Process 5642 attached with 45 threads - interrupt to quit
    % time     seconds  usecs/call     calls    errors syscall
    98.19    7.670403        2257      3398       607 futex
     0.84    0.065886           8      8423           pread
     0.69    0.053980        4498        12           fdatasync
     0.22    0.017094           5      3778           pwrite
     0.05    0.004107           5       808           sched_yield
     0.00    0.000120          10        12           read
     0.00    0.000110           9        12           open
     0.00    0.000089           7        12           close
     0.00    0.000025           0      1431           clock_gettime
     0.00    0.000000           0        46           write
     0.00    0.000000           0         1         1 stat
     0.00    0.000000           0        12           lseek
     0.00    0.000000           0        26           mmap
     0.00    0.000000           0        88           mprotect
     0.00    0.000000           0        24           fcntl
    100.00    7.811814                 18083       608 total
    The above stats show that there is too much time spent locking (futex calls) and I don't understand that because
    the application is really single-threaded. I have turned on asynchronous transactions so the writes might be
    flushed asynchronously in the background but spending that much time locking and timing out seems wrong.
    So, there is possibly something I'm not setting or something weird with the way JVM is behaving on my box.
    I grep-ed for futex calls in one of my strace log snippet and I see that there is a VM thread that grabbed the mutex
    maximum number(223) of times and followed by Garbage Collector threads: the following is the lock counts and thread-pids
    within the process:
    These are the 10 GC threads (each thread has grabbed lock on an avg 85 times):
      86 [8538]
      85 [8539]
      91 [8540]
      91 [8541]
      92 [8542]
      87 [8543]
      90 [8544]
      96 [8545]
      87 [8546]
      97 [8547]
      96 [8548]
      91 [8549]
      91 [8550]
      80 [8552]
    VM Periodic Task Thread" prio=10 tid=0x00002aaaf4065000 nid=0x2180 waiting on condition (Main problem??)
     223 [8576] ==> grabbing a lock 223 times -- not sure why this is happening…
    "pool-2-thread-1" prio=10 tid=0x00002aaaf44b7000 nid=0x21c8 runnable [0x0000000042aa8000] -- main worker thread
       34 [8648] (main thread grabs futex only 34 times when compared to all the other threads)
    The load average seems ok; though my system thinks it has very less memory left and that
    I think is because its using up a lot of memory for the file system cache?
    top - 23:52:00 up 6 days, 8:41, 1 user, load average: 3.28, 3.40, 3.44
    Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie
    Cpu(s): 3.2%us, 0.9%sy, 0.0%ni, 87.5%id, 8.3%wa, 0.0%hi, 0.1%si, 0.0%st
    Mem: 98999820k total, 98745988k used, 253832k free, 530372k buffers
    Swap: 18481144k total, 1304k used, 18479840k free, 89854800k cached
    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    8424 rchitta 16 0 7053m 6.2g 4.4g S 18.3 6.5 401:01.88 java
    8422 rchitta 15 0 7011m 6.1g 4.4g S 14.6 6.5 528:06.92 java
    8423 rchitta 15 0 6989m 6.1g 4.4g S 5.7 6.5 615:28.21 java
    $ java -version
    java version "1.6.0_21"
    Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
    Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
    Maybe I should make my application a Concurrent Data Store app as there is really only one thread doing the writes and reads. But I would like
    to understand why my process is spending so much time in locking.
    Can I try any other options? How do I prevent such heavy locking from happening? Has anyone seen this kind of behavior? Maybe this is
    all normal. I'm pretty new to using BDB.
    If there is a way to disable locking that would also work as there is only one thread that's really doing all the job.
    Should I disable the file system cache? One thing is that my application does not utilize cache very well as once I visit a key, I don't visit that
    key again for a very long time so its very possible that the key has to be read again from the disk.
    It is possible that I'm thinking this completely wrong and focussing too much on locking behavior and the problem is else where.
    Any thoughts/suggestions etc are welcome. Your help on this is much appreciated.
    Thanks,
    Rama

    Hi,
    Looks like you're using BDB, not BDB JE, and this is the BDB JE forum. Could you please repost here?:
    Berkeley DB
    Thanks,
    mark

  • Killing all sessions at once who are locking the objects

    Hello all,
    i am working in 9i Oracle RDBMS on AIX IBM OS
    most of the time we face locking issue and there comes more then different 50 sessions which locking different tables.
    here is my script to find out what sessions are locking what tables.
    set lines 200
    set pages 50000
    col SID for 99999
    col SERIAL# for 999999
    col username format a12
    col sql format a55
    col event format a50
    col program format a40
    col MINS for 9999
    col ID1 for 999999
    col object_name for a35
    col locktype for a8;
    select  /*+ ORDERED */ s.sid,s.serial#,s.status,round(s.last_call_et/60) MINS,s.program,l.ID1,d.object_name,d.object_type,l.type as locktype
    from v$lock l,v$session s, dba_objects d
    where l.sid = s.sid
    and l.ID1 = d.object_id
    and s.username = 'MULDMS'
    and last_call_et > 120 and l.type <> 'TX' order by s.status,MINS,l.ID1,l.type; and the out put it gives something like
      SID SERIAL# STATUS    MINS PROGRAM                                      ID1 OBJECT_NAME                         OBJECT_TYPE        LOCKTY
    8981    1069 ACTIVE       2 frmweb@Appsdms31 (TNS V1-V3)               30407 VH_BTN                              TABLE              TM
    1642     512 ACTIVE      15 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
      690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
      699    1787 ACTIVE      17 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
      690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
      690    1057 ACTIVE      17 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                      TABLE              TM
    10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
    6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    1912    1655 ACTIVE      18 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
    6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    1912    1655 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    1754    1582 ACTIVE      18 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    10877     895 ACTIVE      18 [email protected] (TNS V1-V3)     30643 VT_CHECK_INOUT                      TABLE              TM
    6654    1085 ACTIVE      18 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                      TABLE              TM
    10708     982 ACTIVE      19 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    5428     855 ACTIVE      19 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    10708     982 ACTIVE      19 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    5428     855 ACTIVE      19 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    10278     897 ACTIVE      20 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
    6261    1056 ACTIVE      20 frmweb@appsdms12 (TNS V1-V3)               28846 AM_DOCS                             TABLE              TM
    6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     28846 AM_DOCS                             TABLE              TM
    1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    28846 AM_DOCS                             TABLE              TM
    10278     897 ACTIVE      20 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
    6261    1056 ACTIVE      20 frmweb@appsdms12 (TNS V1-V3)               30407 VH_BTN                              TABLE              TM
    1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    3521     717 ACTIVE      20 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     30407 VH_BTN                              TABLE              TM
    6598    1413 ACTIVE      20 [email protected] (TNS V1-V3)     30643 VT_CHECK_INOUT                     TABLE              TM
    1312    1000 ACTIVE      20 [email protected] (TNS V1-V3)    30643 VT_CHECK_INOUT                   TABLE              TM
    9131    1002 INACTIVE     2 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
    4887    1040 INACTIVE     2 [email protected] (TNS V1-V3)     30455 VH_PSF                              TABLE              TM
      151    1982 INACTIVE     2 [email protected] (TNS V1-V3)     80224 RD_ENQEXD                           TABLE              TM
      846     988 INACTIVE     3 [email protected] (TNS V1-V3)    29228 GM_VIN                              TABLE              TM
    5364    1149 INACTIVE     3 [email protected] (TNS V1-V3)    30407 VH_BTN                              TABLE              TM
    9934     789 INACTIVE     3 [email protected] (TNS V1-V3)     30455 VH_PSF                              TABLE              TM
    7511    1092 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
    3595    1104 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
      846     988 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TM
      945     670 INACTIVE     3 [email protected] (TNS V1-V3)    30455 VH_PSF                              TABLE              TMand then i have to kill the session one by one . thaat is a tedious task to do.
    i want to modify this script which will give me all the kill statement and i just have to run it
    can someone help me in this regard as i am weak in sql/plsql
    thanks and many thanks

    >
    i want to modify this script which will give me all the kill statement and i just have to run it
    >
    Karthick's script will 'kill' the sessions but before you use that script you may want to read the docs about the KILL and DISCONNECT clauses.
    See the DISCONNECT SESSION and KILL SESSION clauses in the SQL Language doc
    http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm#sthref4724
    >
    DISCONNECT SESSION Clause
    Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever).
    The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
    KILL SESSION Clause
    The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources.
    IMMEDIATE Specify IMMEDIATE to instruct Oracle Database to roll back ongoing transactions, release all session locks, recover the entire session state, and return control to you immediately.
    >
    For DISCONNECT the IMMEDIATE clause will recover the session state 'immediately'.
    Using KILL, even with the IMMEDIATE clause, you are telliing Oracle to roll back any ongoing transactions and that can take a lot of time.
    Make sure you are really doing the operation you want to do. If you want to get the locks released immediately you need to use 'DISCONNECT IMMEDIATE'.

  • File Locking!!! Is this a BUG or there is something wrong in my code.

    In new JDK v 1.4. new means of file locking are introuced, and it seems it is a little bit buggy yet (or maybe this one isn't a one). though it's better than nothing :)
    here is 2 classes. first locks a file, the second attemts to change it.
    import java.io.*;
    import java.nio.*;
    import java.nio.channels.*;
    class FileLocker {
      static File targetFile = new File ("D:\\Java",
                                         "manual.chm");
      public static void main(String[] args)
          throws Exception
        RandomAccessFile fin = new RandomAccessFile (targetFile, "rw");
        FileChannel fChan = fin.getChannel();
        FileLock lock = fChan.lock();
        // to let other process to attempt to change the same file.
        Thread.currentThread().sleep(100000);
        lock.release();
        fChan.close();
        fin.close();
    }and the other class
    import java.io.*;
    import java.nio.*;
    import java.nio.channels.*;
    class FileWriter {
      static File targetFile = new File ("D:\\Java",
                                         "manual.chm");
      public static void main(String[] args)
          throws Exception
        // this is better/more secure way to access files.
        RandomAccessFile f = new RandomAccessFile (targetFile, "rw");
        // next line deletes the file content even if file locked.
    //    FileOutputStream f = new FileOutputStream (targetFile);
    //--this parts is not needed as the problem is in first 2 lines
        FileChannel fChan = f.getChannel();
        if (fChan.isOpen()) {
          System.out.println("File is Opened, can't write");
        } else
          f.write(-1);
    }so when i use FileInputStream for open stream to write,
    constructor deletes the targetFile (makes it size equal to 0)
    at once i create new FileInputStream object. Since, when i
    use RandomAccessFile to open stream for writting nothing happens.
    after that, f.write (-1); throws exception regardless the way the
    uoutput stream was created.
    So i think there is some problem in FileInputStream class' constructor.

    OK, I know you mean FileOutputStream instead of FileInputStream in the above message. Looks to me like you've discovered a bug in the way Java is locking the file - locking the whole contents of a file (using the no-args lock or tryLock methods) doesn't prevent other programs, including Java, from overwriting some, if not all, of the file. Note that this occurs even on Windows 2000, where exclusive locks appear to be well supported.
    I've found a similar problem where saving from Outlook appears to zero the whole of the locked file. Saving from other programs that are a little more careful, such as XEmacs, appears to only (!) truncate the file to 0, as the FileOutputStream does.
    From what I can tell, in JDK 1.4.2 RandomAccessFiles respect each others' locks, but nothing else does.

  • Lock never expires

    Hello,
    About once a month it happens that a lock of a "ENV->txn_checkpoint( ENV, 0, 0, 0 )"
    simply blocks and does not expire. In the down below `db_stat -CA` the lock is kept
    more than 5 hours ("*expires 02-01-00:03:07.151182000*"), until I could do a
    `db_recover` and bring BDB back to life.
    The environment is set to:
    ENV->set_lk_detect( ENV, DB_LOCK_OLDEST );
    ENV->set_timeout( ENV, 60 * 1000 * 1000, DB_SET_LOCK_TIMEOUT );
    ENV->set_timeout( ENV, 60 * 1000 * 1000, DB_SET_TXN_TIMEOUT );
    Once a minute i do:
    ENV->lock_detect( ENV, 0, DB_LOCK_OLDEST, &rejected );
    ENV->lock_detect( ENV, 0, DB_LOCK_EXPIRE, &rejected );
    From "00:03:00" to "05:22:00" I have seen many rejected locks but the perpetual
    lock "80b7b6fb" (PID:32179) from the txn_checkpoint() was never brocken.
    Thanks
    Josef
    I had to remove quite a lot from `db_stat -CA` not to exceed 30000 chars:
    Default locking region information:
    435392  Last allocated locker ID
    0x7fffffff  Current maximum unused locker ID
    9   Number of lock modes
    32768   Maximum number of locks possible
    32768   Maximum number of lockers possible
    32768   Maximum number of lock objects possible
    80  Number of lock object partitions
    6401    Number of current locks
    7214    Maximum number of locks at any one time
    283 Maximum number of locks in any one bucket
    0   Maximum number of locks stolen by for an empty partition
    0   Maximum number of locks stolen for any one partition
    6397    Number of current lockers
    6397    Maximum number of lockers at any one time
    159 Number of current lock objects
    1413    Maximum number of lock objects at any one time
    3   Maximum number of lock objects in any one bucket
    0   Maximum number of objects stolen by for an empty partition
    0   Maximum number of objects stolen for any one partition
    3231M   Total number of locks requested (3231111865)
    3231M   Total number of locks released (3231086892)
    1928    Total number of locks upgraded
    423527  Total number of locks downgraded
    70117   Lock requests not available due to conflicts, for which we waited
    18553   Lock requests not available due to conflicts, for which we did not wait
    1   Number of deadlocks
    60M Lock timeout value (60000000)
    34509   Number of locks that have timed out
    60M Transaction timeout value (60000000)
    4514    Number of transactions that have timed out
    17MB 360KB  The size of the lock region
    24M The number of partition locks that required waiting (0%)
    8468160 The maximum number of times any partition lock was waited for (0%)
    3545    The number of object queue operations that required waiting (0%)
    57474   The number of locker allocations that required waiting (0%)
    64  The number of region locks that required waiting (0%)
    3   Maximum hash bucket length
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Lock REGINFO information:
    Lock    Region type
    5   Region ID
    __db.005    Region name
    0x925f1000  Region address
    0x925f10c4  Region primary address
    0   Region maximum allocation
    0   Region allocated
    Region allocations: 169 allocations, 0 failures, 0 frees, 1 longest
    Allocations by power-of-two sizes:
      1KB   2
      2KB   0
      4KB   0
      8KB   1
    16KB   0
    32KB   160
    64KB   0
    128KB   0
    256KB   0
    512KB   2
    1024KB  0
    REGION_JOIN_OK  Region flags
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Lock region parameters:
    65561   Lock region region mutex [64/12M 0% 16646/3074799296] <wakeups 10/11>
    32771   locker table size
    32771   object table size
    724 obj_off
    3020556 locker_off
    0   need_dd
    next_timeout: 02-01-05:22:01.599805000
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Lock conflict matrix:
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Locks grouped by lockers:
    Locker   Mode      Count Status  ----------------- Object ---------------
    [...] sniped rows starting with a ' ' [...]
    80b88442 dd= 6 locks held 1    write locks 0    pid/thread 16452/3064153872 priority 100       expires 02-01-05:22:22.246053000 lk expires 02-01-05:22:22.246053000
    80b88442 READ          1 WAIT    mediastatistic.db         page          0
    80b88442 READ          1 HELD    mediastatistic.db         handle        0
    80b88445 dd= 1 locks held 1    write locks 0    pid/thread 16634/3063199504 priority 100       expires 02-01-05:23:01.279172000 lk expires 02-01-05:23:01.279172000
    80b88445 READ          1 WAIT    mediastatistic.db         page          0
    80b88445 READ          1 HELD    mediastatistic.db         handle        0
    80b7b6fb dd=4548 locks held 3    write locks 3    pid/thread 32179/3064153872 priority 100       expires 02-01-00:03:07.151182000
    80b7b6fb WRITE         1 HELD    queue_status.db           page          1
    80b7b6fb WAS_WRITE     1 HELD    queue_user.db             page         15
    80b7b6fb WAS_WRITE     2 HELD    queue.db                  page       3417
    80b883ee dd=57 locks held 5    write locks 5    pid/thread 21788/3063506704 priority 100       expires 02-01-05:22:02.091000000 lk expires 02-01-05:22:02.091000000
    80b883ee READ          1 WAIT    queue_status.db           page          1
    80b883ee WAS_WRITE     1 HELD    queue_process.db          page          1
    80b883ee WAS_WRITE     1 HELD    queue_user.db             page          2
    80b883ee WAS_WRITE     1 HELD    queue_media.db            page          1
    80b883ee WAS_WRITE     1 HELD    queue_usercreated.db      page          2
    80b883ee WAS_WRITE     2 HELD    queue.db                  page        620
    80b883ef dd=56 locks held 0    write locks 0    pid/thread 31279/3063117584 priority 100       expires 02-01-05:22:02.094269000 lk expires 02-01-05:22:02.094269000
    80b883ef WRITE         1 WAIT    queue.db                  page       3417
    80b883f4 dd=53 locks held 4    write locks 4    pid/thread 3880/3062753040 priority 100       expires 02-01-05:22:02.112277000 lk expires 02-01-05:22:02.112277000
    80b883f4 WRITE         1 WAIT    queue_process.db          page          1
    80b883f4 WAS_WRITE     1 HELD    queue_user.db             page          5
    80b883f4 WAS_WRITE     1 HELD    queue_usercreated.db      page         10
    80b883f4 WAS_WRITE     1 HELD    queue_useractive.db       page          1
    80b883f4 WAS_WRITE     2 HELD    queue.db                  page       1589
    80b883f6 dd=52 locks held 1    write locks 1    pid/thread 6752/3063416592 priority 100       expires 02-01-05:22:02.120049000 lk expires 02-01-05:22:02.120049000
    80b883f6 WRITE         1 WAIT    queue_usercreated.db      page         10
    80b883f6 WAS_WRITE     2 HELD    queue.db                  page        359
    80b88401 dd=50 locks held 2    write locks 2    pid/thread 15858/3063584528 priority 100       expires 02-01-05:22:02.176324000 lk expires 02-01-05:22:02.176324000
    80b88401 WRITE         1 WAIT    mediastatistic.db         page          0
    80b88401 WRITE         1 HELD    mediastatistic.db         page     127272
    80b88401 WAS_WRITE     1 HELD    mediastatistic.db         page     127272
    80b88407 dd=48 locks held 0    write locks 0    pid/thread 15053/3063318288 priority 100       expires 02-01-05:22:02.209851000 lk expires 02-01-05:22:02.209851000
    80b88407 WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88408 dd=47 locks held 0    write locks 0    pid/thread 23242/3064022800 priority 100       expires 02-01-05:22:02.213305000 lk expires 02-01-05:22:02.213305000
    80b88408 WRITE         1 WAIT    queue.db                  page        620
    80b88409 dd=46 locks held 0    write locks 0    pid/thread 14254/3064424208 priority 100       expires 02-01-05:22:02.218573000 lk expires 02-01-05:22:02.218573000
    80b88409 WRITE         1 WAIT    queue.db                  page        359
    80b8840b dd=45 locks held 0    write locks 0    pid/thread 3639/3063240464 priority 100       expires 02-01-05:22:02.225444000 lk expires 02-01-05:22:02.225444000
    80b8840b READ          1 WAIT    queue_useractive.db       page          1
    80b8840c dd=44 locks held 0    write locks 0    pid/thread 15783/3063670544 priority 100       expires 02-01-05:22:02.225574000 lk expires 02-01-05:22:02.225574000
    80b8840c WRITE         1 WAIT    mediastatistic.db         page     127272
    80b8840e dd=43 locks held 1    write locks 1    pid/thread 23404/3062658832 priority 100       expires 02-01-05:22:02.232718000 lk expires 02-01-05:22:02.232718000
    80b8840e WRITE         1 WAIT    queue_usercreated.db      page         10
    80b8840e WAS_WRITE     2 HELD    queue.db                  page       2439
    80b88414 dd=40 locks held 0    write locks 0    pid/thread 15532/3062458128 priority 100       expires 02-01-05:22:02.339357000 lk expires 02-01-05:22:02.339357000
    80b88414 WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88415 dd=39 locks held 0    write locks 0    pid/thread 12934/3063731984 priority 100       expires 02-01-05:22:02.346746000 lk expires 02-01-05:22:02.346746000
    80b88415 WRITE         1 WAIT    queue.db                  page        359
    80b88416 dd=38 locks held 2    write locks 2    pid/thread 15896/3063670544 priority 100       expires 02-01-05:22:02.411124000 lk expires 02-01-05:22:02.411124000
    80b88416 WRITE         1 WAIT    mediastatistic.db         page          0
    80b88416 WRITE         1 HELD    mediastatistic.db         page     126767
    80b88416 WAS_WRITE     1 HELD    mediastatistic.db         page     126767
    80b88417 dd=37 locks held 0    write locks 0    pid/thread 14569/3063420688 priority 100       expires 02-01-05:22:02.426556000 lk expires 02-01-05:22:02.426556000
    80b88417 WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88419 dd=36 locks held 1    write locks 1    pid/thread 1345/3063146256 priority 100       expires 02-01-05:22:02.538765000 lk expires 02-01-05:22:02.538765000
    80b88419 READ          1 WAIT    queue_useractive.db       page          1
    80b88419 WAS_WRITE     2 HELD    queue.db                  page       1585
    80b8841e dd=35 locks held 0    write locks 0    pid/thread 29349/3063453456 priority 100       expires 02-01-05:22:02.618734000 lk expires 02-01-05:22:02.618734000
    80b8841e WRITE         1 WAIT    queue.db                  page       3417
    80b8841f dd=34 locks held 0    write locks 0    pid/thread 6200/3063899920 priority 100       expires 02-01-05:22:02.622259000 lk expires 02-01-05:22:02.622259000
    80b8841f WRITE         1 WAIT    queue.db                  page        359
    80b88420 dd=33 locks held 0    write locks 0    pid/thread 10999/3062880016 priority 100       expires 02-01-05:22:02.622284000 lk expires 02-01-05:22:02.622284000
    80b88420 WRITE         1 WAIT    queue.db                  page        359
    80b88421 dd=32 locks held 1    write locks 1    pid/thread 15349/3062720272 priority 100       expires 02-01-05:22:02.629291000 lk expires 02-01-05:22:02.629291000
    80b88421 WRITE         1 WAIT    queue_usercreated.db      page          6
    80b88421 WAS_WRITE     2 HELD    queue.db                  page        309
    80b88422 dd=31 locks held 0    write locks 0    pid/thread 15969/3062982416 priority 100       expires 02-01-05:22:02.632325000 lk expires 02-01-05:22:02.632325000
    80b88422 WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88423 dd=30 locks held 2    write locks 2    pid/thread 21631/3061966608 priority 100       expires 02-01-05:22:02.634340000 lk expires 02-01-05:22:02.634340000
    80b88423 WRITE         1 WAIT    queue_media.db            page          1
    80b88423 WAS_WRITE     1 HELD    queue_usercreated.db      page          6
    80b88423 WAS_WRITE     2 HELD    queue.db                  page       3058
    80b88424 dd=29 locks held 0    write locks 0    pid/thread 1500/3062712080 priority 100       expires 02-01-05:22:02.648949000 lk expires 02-01-05:22:02.648949000
    80b88424 WRITE         1 WAIT    queue.db                  page       1585
    80b88425 dd=28 locks held 0    write locks 0    pid/thread 15274/3063731984 priority 100       expires 02-01-05:22:02.681320000 lk expires 02-01-05:22:02.681320000
    80b88425 WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88427 dd=27 locks held 0    write locks 0    pid/thread 5970/3063367440 priority 100       expires 02-01-05:22:02.722208000 lk expires 02-01-05:22:02.722208000
    80b88427 WRITE         1 WAIT    queue.db                  page        359
    80b88428 dd=26 locks held 0    write locks 0    pid/thread 21321/3063117584 priority 100       expires 02-01-05:22:02.736108000 lk expires 02-01-05:22:02.736108000
    80b88428 WRITE         1 WAIT    queue.db                  page        620
    80b8842a dd=25 locks held 0    write locks 0    pid/thread 14491/3063039760 priority 100       expires 02-01-05:22:02.874833000 lk expires 02-01-05:22:02.874833000
    80b8842a WRITE         1 WAIT    mediastatistic.db         page     127272
    80b8842b dd=24 locks held 20   write locks 19   pid/thread 2067/3064137488 priority 100       expires 02-01-05:22:02.881527000 lk expires 02-01-05:22:02.881527000
    80b8842b WRITE         1 WAIT    queue.db                  page        359
    80b8842b WAS_WRITE     1 HELD    mediareferer.db           page      11187
    80b8842b WAS_WRITE     2 HELD    mediadocument.db          page      91943
    80b8842b WAS_WRITE     2 HELD    mediafile.db              page     182304
    80b8842b WAS_WRITE     2 HELD    mediafile_livestream.db   page          1
    80b8842b WAS_WRITE     1 HELD    mediastatistic.db         page          0
    80b8842b WAS_WRITE     2 HELD    mediastatistic.db         page     127441
    80b8842b WAS_WRITE     1 HELD    media.db                  page      59394
    80b8842b WAS_WRITE     1 HELD    media.db                  page          1
    80b8842b WAS_WRITE     1 HELD    media_personalpublished.db page          1
    80b8842b WAS_WRITE     2 HELD    media_personalpublished.db page          6
    80b8842b WAS_WRITE     1 HELD    media_personallanguagetypepublished.db page          1
    80b8842b WAS_WRITE     2 HELD    media_personallanguagetypepublished.db page          8
    80b8842b WAS_WRITE     1 HELD    media_personaltypepublished.db page          1
    80b8842b WAS_WRITE     2 HELD    media_personaltypepublished.db page          6
    80b8842b WAS_WRITE     1 HELD    media_personallanguagepublished.db page          1
    80b8842b WAS_WRITE     2 HELD    media_personallanguagepublished.db page          6
    80b8842b WAS_WRITE     1 HELD    media_language.db         page          7
    80b8842b WAS_WRITE     1 HELD    media_user.db             page        175
    80b8842b READ          1 HELD    media.db                  page      60382
    80b8842b WAS_WRITE     3 HELD    media.db                  page      60382
    80b8842c dd=23 locks held 2    write locks 2    pid/thread 16079/3062560528 priority 100       expires 02-01-05:22:02.914927000 lk expires 02-01-05:22:02.914927000
    80b8842c WRITE         1 WAIT    mediastatistic.db         page          0
    80b8842c WRITE         1 HELD    mediastatistic.db         page     127104
    80b8842c WAS_WRITE     1 HELD    mediastatistic.db         page     127104
    80b8842d dd=22 locks held 0    write locks 0    pid/thread 15946/3063805712 priority 100       expires 02-01-05:22:02.917872000 lk expires 02-01-05:22:02.917872000
    80b8842d WRITE         1 WAIT    mediastatistic.db         page     127104
    80b8842e dd=21 locks held 0    write locks 0    pid/thread 16391/3062630160 priority 100       expires 02-01-05:22:02.933898000 lk expires 02-01-05:22:02.933898000
    80b8842e WRITE         1 WAIT    mediastatistic.db         page     127104
    80b8842f dd=20 locks held 0    write locks 0    pid/thread 14468/3064334096 priority 100       expires 02-01-05:22:02.980551000 lk expires 02-01-05:22:02.980551000
    80b8842f WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88430 dd=19 locks held 2    write locks 2    pid/thread 15108/3063666448 priority 100       expires 02-01-05:22:03.005311000 lk expires 02-01-05:22:03.005311000
    80b88430 WRITE         1 WAIT    mediastatistic.db         page          0
    80b88430 WRITE         1 HELD    mediastatistic.db         page     126936
    80b88430 WAS_WRITE     1 HELD    mediastatistic.db         page     126936
    80b88431 dd=18 locks held 0    write locks 0    pid/thread 15605/3064194832 priority 100       expires 02-01-05:22:03.005324000 lk expires 02-01-05:22:03.005324000
    80b88431 WRITE         1 WAIT    mediastatistic.db         page     126936
    80b88432 dd=17 locks held 2    write locks 2    pid/thread 15550/3064497936 priority 100       expires 02-01-05:22:03.088119000 lk expires 02-01-05:22:03.088119000
    80b88432 WRITE         1 WAIT    mediastatistic.db         page          0
    80b88432 WRITE         1 HELD    mediastatistic.db         page     126091
    80b88432 WAS_WRITE     1 HELD    mediastatistic.db         page     126091
    80b88433 dd=16 locks held 0    write locks 0    pid/thread 14983/3062826768 priority 100       expires 02-01-05:22:03.110238000 lk expires 02-01-05:22:03.110238000
    80b88433 WRITE         1 WAIT    mediastatistic.db         page     127104
    80b88434 dd=15 locks held 0    write locks 0    pid/thread 14858/3064395536 priority 100       expires 02-01-05:22:03.128270000 lk expires 02-01-05:22:03.128270000
    80b88434 WRITE         1 WAIT    mediastatistic.db         page     127104
    80b88435 dd=14 locks held 0    write locks 0    pid/thread 16143/3063744272 priority 100       expires 02-01-05:22:03.138039000 lk expires 02-01-05:22:03.138039000
    80b88435 WRITE         1 WAIT    mediastatistic.db         page     126767
    80b88436 dd=13 locks held 0    write locks 0    pid/thread 15823/3062839056 priority 100       expires 02-01-05:22:03.151565000 lk expires 02-01-05:22:03.151565000
    80b88436 WRITE         1 WAIT    mediastatistic.db         page     127272
    80b88437 dd=12 locks held 0    write locks 0    pid/thread 15694/3063637776 priority 100       expires 02-01-05:22:03.203599000 lk expires 02-01-05:22:03.203599000
    80b88437 WRITE         1 WAIT    mediastatistic.db         page     127104
    80b88439 dd=11 locks held 2    write locks 2    pid/thread 2077/3062581008 priority 100       expires 02-01-05:22:04.313716000 lk expires 02-01-05:22:04.313716000
    80b88439 WRITE         1 WAIT    mediastatistic.db         page          0
    80b88439 WRITE         1 HELD    mediastatistic.db         page     104797
    80b88439 WAS_WRITE     1 HELD    mediastatistic.db         page     104797
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Locks grouped by object:
    Locker   Mode      Count Status  ----------------- Object ---------------
    [...] snip [...]

    Hello,
    This bug did not raise in BDB 5.1.25 yet.
    BDB 5.1.25 is the first release, that runs stable for two month
    without the need of a `db_recover`. Maybe #18789 ?
    Thanks
    Josef

  • JRockit 1.4.2_04....is this a locking situation ?

    We migrated recently to JRockit VM with Weblogic 7 on multi-cpu mahcine running Linux. After multiple simultaneous calls to a bean, we see that the managed server stops responding ( no OutOfMemory errors - just no response for any http calls ). I was wondering if the following thread dump shows any locking issue ( although there doesnt seem to be any deadlocks )...
    ===== FULL THREAD DUMP ===============
    Thu Mar 17 09:01:00 2005
    "Main Thread" prio=5 id=0x80 pid=22480 waiting
    -- Waiting for notification on: weblogic/t3/srvr/T3Srvr@0x405b25d8[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/t3/srvr/T3Srvr.waitForDeath(T3Srvr.java:1083)@0x2420c414
    ^-- Lock released while waiting: weblogic/t3/srvr/T3Srvr@0x405b25d8[fat lock]
    at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:318)@0x21b4551d
    at weblogic/Server.main(Server.java:32)@0x21b44e52
    --- End of stack trace
    "(Signal Handler)" prio=5 id=0x100 pid=22487 active, daemon
    "(Code Generation Thread 1)" prio=5 id=0x180 pid=22488 active, native_waiting, daemon
    "(Code Optimization Thread 1)" prio=5 id=0x200 pid=22489 active, native_waiting, daemon
    "(GC Main Thread)" prio=5 id=0x280 pid=22490 active, daemon
    "(GC Worker Thread 1)" prio=5 id=0x300 pid=22491 active, native_waiting, daemon
    "(GC Worker Thread 2)" prio=5 id=0x380 pid=22492 active, native_waiting, daemon
    "Finalizer" prio=8 id=0x400 pid=22493 waiting, daemon
    -- Waiting for notification on: java/lang/ref/ReferenceQueue$Lock@0x404cfed8[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af6b85
    at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:111)@0x21af9511
    ^-- Lock released while waiting: java/lang/ref/ReferenceQueue$Lock@0x404cfed8[fat lock]
    at java/lang/ref/ReferenceQueue.remove(ReferenceQueue.java:127)@0x21af93ec
    at java/lang/ref/Finalizer$FinalizerThread.run(Unknown Source)@0x21af939e
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "Reference Handler" prio=10 id=0x480 pid=22494 waiting for pending references, daemon
    at java/lang/ref/Reference.getPending(Native Method)@0x21b146f0
    at java/lang/ref/Reference.access$000(Unknown Source)@0x21b14765
    at java/lang/ref/Reference$ReferenceHandler.run(Unknown Source)@0x21b14670
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "[JRockit] Connection Listener" prio=5 id=0x500 pid=22496 active, daemon
    at jrockit/net/SocketNativeIO.accept(Native Method)@0x22415850
    at jrockit/net/SocketNativeIO.accept(Unknown Source)@0x2241590b
    at java/net/AbstractSocketImpl.accept(Unknown Source)@0x22415755
    ^-- Holding lock: java/net/PlainSocketImpl@0x404ed1f0[thin lock]
    at java/net/ServerSocket.implAccept(ServerSocket.java:448)@0x22415665
    at java/net/ServerSocket.accept(ServerSocket.java:419)@0x2241555c
    at com/jrockit/management/rmp/RmpSocketListener.run(RmpSocketListener.java:170)@0x21b44aea
    at java/lang/Thread.run(Unknown Source)@0x2241550f
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "(Hotspot Detector)" prio=10 id=0x580 pid=22497 active, daemon
    "Thread-1" prio=10 id=0x600 pid=22498 waiting, daemon
    -- Waiting for notification on: java/lang/Object@0x40dd8030[fat lock]
    at jrockit/vm/Threads.waitForSignalWithTimeout(Native Method)@0x21af6a30
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af6c19
    at java/lang/Thread.sleep(Unknown Source)@0x21be0615
    ^-- Lock released while waiting: java/lang/Object@0x40dd8030[fat lock]
    at weblogic/transaction/internal/TransactionManagerImpl$1.run(TransactionManagerImpl.java:1660)@0x2267a1ac
    at java/lang/Thread.run(Unknown Source)@0x2241550f
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '0' for queue: 'default'" prio=5 id=0x680 pid=22499 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40dddca0[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40dddca0[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '1' for queue: 'default'" prio=5 id=0x700 pid=22500 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40dde368[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40dde368[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '2' for queue: 'default'" prio=5 id=0x780 pid=22501 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40dde848[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40dde848[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '3' for queue: 'default'" prio=5 id=0x800 pid=22502 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40dded28[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40dded28[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '4' for queue: 'default'" prio=5 id=0x880 pid=22503 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40ddf208[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40ddf208[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '5' for queue: 'default'" prio=5 id=0x900 pid=22504 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40ddf6e8[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40ddf6e8[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '6' for queue: 'default'" prio=5 id=0x980 pid=22505 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40ddfbc8[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40ddfbc8[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '7' for queue: 'default'" prio=5 id=0xa00 pid=22506 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40de00a8[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40de00a8[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '8' for queue: 'default'" prio=5 id=0xa80 pid=22507 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40de0588[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40de0588[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '9' for queue: 'default'" prio=5 id=0xb00 pid=22508 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40de0a68[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40de0a68[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '10' for queue: 'default'" prio=5 id=0xb80 pid=22509 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40de0f48[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40de0f48[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '11' for queue: 'default'" prio=5 id=0xc00 pid=22510 waiting, daemon
    -- Waiting for notification on: weblogic/kernel/ExecuteThread@0x40de1428[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.wait(Unknown Source)@0x21af96d5
    at weblogic/kernel/ExecuteThread.waitForRequest(ExecuteThread.java:146)@0x2267c946
    ^-- Lock released while waiting: weblogic/kernel/ExecuteThread@0x40de1428[fat lock]
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:172)@0x2267c669
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '12' for queue: 'default'" prio=5 id=0xc80 pid=22511 active, daemon
    at weblogic/socket/PosixSocketMuxer.poll(Native Method)@0x2288c800
    at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:621)@0x2288c534
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:23)@0x2288c483
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:213)@0x2288c451
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:189)@0x2267c697
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '13' for queue: 'default'" prio=5 id=0xd00 pid=22512 blocked, daemon
    -- Blocked trying to get lock: java/lang/Object@0x41140860[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.raceForTheFatLock(Unknown Source)@0x21af50f8
    at jrockit/vm/Locks.lockFat(Optimized Method)@0x24afd67d
    at jrockit/vm/Locks.monitorEnterSlowCase(Optimized Method)@0x24affd5b
    at jrockit/vm/Locks.monitorEnter(Native Method)@0x21af3f24
    at jrockit/vm/Locks.monitorEnterForced(Unknown Source)@0x21bd7fd5
    at jrockit/vm/Locks.monitorEnterUnmatched(Native Method)@0x21af3f30
    at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:617)@0x2288c51c
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:23)@0x2288c483
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:213)@0x2288c451
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:189)@0x2267c697
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    "ExecuteThread: '14' for queue: 'default'" prio=5 id=0xd80 pid=22513 blocked, daemon
    -- Blocked trying to get lock: java/lang/Object@0x41140860[fat lock]
    at jrockit/vm/Threads.waitForSignal(Native Method)@0x21af5020
    at jrockit/vm/Locks.lockFat(Optimized Method)@0x24afd66e
    at jrockit/vm/Locks.monitorEnterSlowCase(Optimized Method)@0x24affd5b
    at jrockit/vm/Locks.monitorEnter(Native Method)@0x21af3f24
    at jrockit/vm/Locks.monitorEnterForced(Unknown Source)@0x21bd7fd5
    at jrockit/vm/Locks.monitorEnterUnmatched(Native Method)@0x21af3f30
    at weblogic/socket/PosixSocketMuxer.processSockets(PosixSocketMuxer.java:617)@0x2288c51c
    at weblogic/socket/SocketReaderRequest.execute(SocketReaderRequest.java:23)@0x2288c483
    at weblogic/kernel/ExecuteThread.execute(ExecuteThread.java:213)@0x2288c451
    at weblogic/kernel/ExecuteThread.run(ExecuteThread.java:189)@0x2267c697
    at java/lang/Thread.startThreadFromVM(Unknown Source)@0x21af92f3
    --- End of stack trace
    Blocked lock chains
    ===================
    Chain 2:
    "ExecuteThread: '14' for queue: 'default'" (id: 0x00000d80) waiting for java/lang/Object@0x41140860 held by:
    "ExecuteThread: '12' for queue: 'default'" (id: 0x00000c80) in chain 1
    Open lock chains
    ================
    Chain 1:
    "ExecuteThread: '13' for queue: 'default'" (id: 0x00000d00) waiting for java/lang/Object@0x41140860 held by:
    "ExecuteThread: '12' for queue: 'default'" (id: 0x00000c80) (active)
    ===== END OF THREAD DUMP ===============

    JRockit usually detects and prints out deadlocks at the end of the thread stack dump. Since you most likely have a support contract, I suggest you open a support case so we can take a look at this.
    Thanks,
    Henrik, JRockit team

Maybe you are looking for

  • Some keys still do not work on my Macbook Pro 13"

    i have a 13" macbook pro running OS Mavericks My laptop was on the bed and i found it with dog pee on the right side of the keyboard. i immediately cleaned the top of the keyboard and turned it upside down so liquid would come out. It was clean and t

  • Decimals in Haley Office Rules

    Hi, we are using version 9.4 of OPA / Haley Office Rules. Rulebases are deployed on the Determination Server, running on IIS6.0 / .NET2.0 / Windows server 2003. Rulebases are invoked via web services, from a .NET 2.0 client. One of the attributes in

  • Function Module : SCMS_BINARY_TO_TEXT

    Hi, I use the follwoing Function Module to convert from Binary to Text.I call it in the following way: DO 10 times. CALL FUNCTION 'SCMS_BINARY_TO_TEXT'   EXPORTING     INPUT_LENGTH          = 255              APPEND_TO_TABLE       = 'X'             W

  • 2 Overlay Creator questions (audio/video)

    I have a video file placed with a controller selected. It works fine in the Content Viewer, but not on the iPad. When tapped on the iPad, the image just flashes on the point of contact but does not activate the video. The other issue regards the Over

  • Update to PS and Bridge failed, corrupt download

    Mac OSX Yosemite. Stuck in a loop trying to succeed with update of PS and Bridge. 204 msg with downloaded file corrupted. Assume there is a download file in a cache somewhere that I can simply zap and the download will happen again. Anyone know where