Global privilege lock possible?
The little lock icon that appears when I, for example, set certain system preferences, is a good thing.
I would like the comfort of knowing that I've got all of these locks locked.... I've already noticed some that I've inadvertently left open....My Bad!
Is there a way to ask the system to lock all of these that are currently open? ... or see a list of all that are open?
Is it possible ask the system to relock these features automatically upon exiting the dialog .... or at least issue a warning that I'm about to do something dumb ... securitywise.
MacPro Mac OS X (10.4.8)
You are right - the system automatically locks the lock icon when you exit the systems preference>security dialog.
But try this:
-log in with administrative privileges
-in the finder, get info on the system folder
-in the system info dialog, open up Ownership & Permissions>Details
-you will see a little lock - it's probably locked ... so open it (you may have to use your password)
-now close the system info dialog and then reopen it
-the little lock should still be unlocked (it is on my Tiger mac)
I prefer to make sure that I leave all such locks locked ... but I do not know if I accidentally left any open... I'm looking for a way to either globaly lock all of these ...or at least efficiently search for all of the ones that are open ... so that I can lock them.
Seems like prudent security protocol to me.
Oh! and by the way. If you try my little procedure above, don't forget to go back and lock the Ownership&Permissions>Details in the system folder
MacPro Mac OS X (10.4.8)
Similar Messages
-
Global Error Handling - Possible?
Hi there!
Does anyone know if it's possible to catch unhandled errors
that occur in a flex application globally?
The Application.error event allows you to capture Error
Events that arise when communication with the outside world fails
for one reason or another, but as much as I've googled I haven't
been able to find anything for capturing coding errors such as
nullpointers etc. at runtime without wrapping every single line of
code with a try-catch.
In an ideal world I would like to catch these errors and
report them for logging on the server. Has anyone managed to
achieve this without resorting to try-catch-spamming?
The Flex-application in question is a central part of an
e-commerse system so it's rather silly that live errors remain
largely untracked...
Your thoughts would be highly appreciated!Hi,
Try referring the below links...
http://www.summa-tech.com/blog/2010/01/04/global-error-handling-in-flex/
http://livedocs.adobe.com/flex/3/html/help.html?content=11_Handling_errors_06.html
You have one sample demo with source in first link.
Hope this will be helpful.
If this post answers your question or helps, please kindly mark it as such.
Thanks,
Bhasker Chari -
Global timeline stretch possible??
Is there a way to do a global timeline stretch in CS4 ?
Basically I need to change the animation speed from 12 fps to 25 fps - but I dont wont the movie to play twice as fast, and I don't want to have to manually move each key frame to fix it because it will take forever!
Helpppppppppp!!
UPDATE:
Maybe Flash has never made this an option because I see several people asking this same question as far back as 2006 and no one has responded with a solution. You would think Adobe would have figured this one out by now.The stretch functionality is only for spans of frames, not an entire timeline. For new motion tweens and IK (likely the new feature being discussed),
dragging the end will stretch the span (shift drag extends the span). This is possible in older versions of Flash for static and classic tween frames by holding Ctrl then dragging when you see the arrows.
This is not available built-in for an entire timeline. Retiming a timeline is definitely a known enhancement request, something I'd use myself, and hopefully something that can be scheduled for a future release. Until then a JSFL would need to be found and used. -
Hi,
I want to read some strings from a file, and using these strings
I want to initialise an object. Now I want that, this object
should only have one instance, hence all the objects, which want to
access it, should treat it as Global object. Could anybody suggest something?
gaurav_k1Hi,
I want to read some strings from a file, and using
these strings
I want to initialise an object. Now I want that, this
object
should only have one instance, hence all the objects,
which want to
access it, should treat it as Global object. Could
anybody suggest something?
gaurav_k1Hi
u can solve your single instance problem like this
in your class declare your constructor to be private.
create a static method (factory method)in which this private constructor is called.
and from this method return that object.
now to restrict the class from having more than one instances declare a static integer variable,initiallize it with value 0.
in your factory method check the value of this variable,
if its 0 create an instance and increment the integer variable to 1.
if its 1 return null.
this will restrict your class.
hope a part of ur problem is solved.
bye -
Optimistic Locking - Possible bug with Weblogic
After extensive testing of a j2ee application Im involved with, it would appear their exists a problem with using Weblogic's Optimistic Concurrency (OL) mechanism.
The exact problem is as follows:
The ejbCreate and ejbRemove methods of a particular entity bean are as follows:
public abstract class ProductBean implements javax.ejb.EntityBean {
ejbCreate(){
FolderEntityHome folderEH = FolderComponent.getFolderEntityHome();
folderEH.create(getId());
ejbRemove(){
FolderEntityHome folderEH = FolderComponent.getFolderEntityHome();
try {
FolderBean folderEH.findByProductId(getId());
catch(InvalidAccessRightsException iare)
throw new RemoveException();
Previously before OL was added when a RemoveException was thrown, this would cause the ejbRemove exception to fail, thus both the product and folder would still exist.
After adding OL, when an InvalidAccessRightsException occurs giving rise to a RemoveException being thrown, weblogic simply ignores the RemoveException and deletes the Product even though the Folder could not be deleted. This causes system errors when users try to access the folder which contains a link to a product which no longer exists!
Is anyone aware of this particular problem? Is it indeed a bug with Weblogic? For clarity, I believe I am using version 8.1 and the way in which I have implemented OL is to use an additional version column in the underlying tables for all entity beans.In case anyone's interested, it appears from further testing that the problem I've been having in the way the RemoveException behaves is down to the difference in which version 6.0 treats this exception compared to version 8.1!
In version 6.0, if you threw a RemoteException at any point in the ejbRemove(), the entity would not be removed!
In version 8.1, something wierd happens. If a RemoteException() is thrown in the ejbRemove() and sometime during the same transaction at the point of commit, the entity on which the exception is thrown is attempted to be accessed (through a finder), then the entity continues to be deleted! If on the other hand, a RemoveException is thrown and no access/modification is attempted on that entity within the same transaction, then at the point of commit, the entity is not removed!
Seems this is indeed a problem which needs to be addressed in future releases.
Message was edited by:
rotan_imretxe
Message was edited by:
rotan_imretxe -
Locking "Portal Administrators" out of items in a content area
I have a content area that will contain sensitive documents.
I've been asked to find out whether security can be set up so
that only a certain group of users can access the content area.
This includes locking out the portal administrators from seeing
these items. Is this possible and how can it be done?
Thanks!
Esther PoulsenYou will always need a couple of users that can function as
Portal superusers/administrators. That said, most
administrative tasks can be delegated and decentralized so that
only these few administrators have completely global
privileges. One of the key purposes of content areas is to
partition security among your users.
Regards,
Jerry -
CUA SU10 issue with users getting locked
I did some role change using SU10 on CUA central system for 200 users. 45 of the users got locked with global admin lock in the child system for which I made the role changes. These user locks are shown in the child system change documents log as changes by the CUA RFC user. I have this problem everytime I use su10. Why does this happen? What can I do about it? Thanks, KT
Hi Todd,
propably you have some inconsistencies in your landscape....
the cause of such 'unwanted' effects is the fact that if you change a user in your CUA central system, the whole user information is picked, then edited with you changes and afterwards distributed to all child systems.
So what I could imagine in your example is as follows:
User has a global lock in central system already, the particular child system did not have that information (user is still unlocked there). Several causes are possible, for instance the lock idoc did not get processed, Child system was not available/connected to CUA when the lock had been set,......).
At the next update of that user (assign a role), the lock information from the central system is pushed to that child.
Why?
Because the design is to assure data consistency between central and child system. Therefore all the user information from central system is pushed to child at any user change. (that is also why you will see in SCUL 3 idocs for each user change (also user and profile idocs are pushed, even if you have changed the role assignement only).
So what you could check is, if that users got the lock flag (128) already in the past somewhen.
b.rgds, Bernhard -
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,
RamaHi,
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 -
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 -
Cursors throwing Unexpected lock status: 6
I am using a Berkeley DB instance and have a multithreaded clients each performing various types of operations on the database. In general there are three types of operations being performed, reads, writes (which use RMW locks), and (non-transactional) cursors. After some time my application dumps the following:
Unexpected lock status: 6
PANIC: Invalid argument
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__os_stack+0x2b) [0xb7ef085f]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__os_abort+0x1d) [0xb7eecbb1]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__env_panic+0xa8) [0xb7e80b8e]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__lock_get_internal+0x1855) [0xb7e2e925]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__lock_vec+0x167) [0xb7e2bd3c]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__db_lget+0x45c) [0xb7e8bfe2]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so [0xb7d850a5]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so [0xb7d816ce]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__dbc_get+0x598) [0xb7e76a29]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__dbc_get_pp+0x11f) [0xb7e870ec]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(_ZN3Dbc3getEP3DbtS1_j+0x3f) [0xb7d71feb]
...(non-berkeley db layers)...
/lib/tls/i686/cmov/libpthread.so.0 [0xb7a2350f]
/lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7b20a0e]
Aborted
In studying the core dumps and doing some testing this behavior only occurs when cursors are used, when those operations are removed the error no longer manifests itself so either the cursor is the issue, or how the cursors are interacting with other operations. Below is a sample of cursor code being run:
void run_cursor()
Dbc *curp = NULL;
int ret;
try
int i = 0;
Dbt key(&i,sizeof(int));
Dbt data(buffer, 0);
data.set_flags(DB_DBT_USERMEM);
data.set_ulen(MAX_BUFFER_SIZE);
db->cursor(NULL, &curp, 0);
while ((ret = curp->get(&key, &data, DB_NEXT)) == 0) {
//keep a list of all the keys in the db
keys.push_back(i);
if (ret != DB_NOTFOUND) {
cerr << "Cursor Error" << endl;
curp->close();
catch (DbException &ex) {
cout << ex.what() << endl;
if( curp != NULL )
curp->close();
I have tried wrapping the cursor in a transaction and it seems to worsen the issue (it happens more frequently). In all methods I am printing error messages when exceptions are thrown by the database (e.g. DbExceptions) and the program prints no errors so I do not believe it is a side effect of some other error. Here is the relevant parts of the case where is RMW lock is used:
void update()
DbTxn *txn = NULL;
try
env->txn_begin(NULL, &txn, 0);
int id;
Dbt key( &id, sizeof(int) );
Dbt value(buffer, 0);
value.set_flags(DB_DBT_USERMEM);
value.set_ulen(MAX_BUFFER_SIZE);
int err = db->get(txn, &key, &value, DB_RMW);
if( err == DB_NOTFOUND )
cerr << "Error trying to read key" << endl;
txn->abort(0);
return;
//code to modify the value here
db->put(txn, &key, &value, 0);
txn->commit(0);
} catch (DbDeadlockException &de) {
cout << de.what() << endl;
if( txn != NULL )
txn->abort();
Just in case it helps, here is the output of db_stat -CA on the database after it has crashed:
Default locking region information:
12 Last allocated locker ID
0x7fffffff Current maximum unused locker ID
9 Number of lock modes
5000 Maximum number of locks possible
5000 Maximum number of lockers possible
1000 Maximum number of lock objects possible
1 Number of lock object partitions
6 Number of current locks
9 Maximum number of locks at any one time
4 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
11 Number of current lockers
13 Maximum number of lockers at any one time
3 Number of current lock objects
9 Maximum number of lock objects at any one time
2 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
3786734 Total number of locks requested
3786664 Total number of locks released
0 Total number of locks upgraded
1 Total number of locks downgraded
7089 Lock requests not available due to conflicts, for which we waited
61 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
1000000 Transaction timeout value
0 Number of transactions that have timed out
1MB 592KB 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%)
165 The number of region locks that required waiting (0%)
2 Maximum hash bucket length
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock REGINFO information:
Lock Region type
5 Region ID
__db.005 Region name
0xb781b000 Original region address
0xb781b000 Region address
0xb781b0c0 Region primary address
0 Region maximum allocation
0 Region allocated
Region allocations: 11006 allocations, 0 failures, 0 frees, 1 longest
Allocations by power-of-two sizes:
1KB 11003
2KB 0
4KB 0
8KB 0
16KB 1
32KB 0
64KB 1
128KB 1
256KB 0
512KB 0
1024KB 0
REGION_JOIN_OK Region flags
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock region parameters:
104 Lock region region mutex [165/7025066 0% 5979/3075574672]
8191 locker table size
1031 object table size
600 obj_off
62608 locker_off
0 need_dd
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock conflict matrix:
0 0 0 0 0 0 0 0 0
0 0 1 0 1 0 1 0 1
0 1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0 0
0 1 1 0 0 0 0 1 1
0 0 1 0 0 0 0 0 1
0 1 1 0 0 0 0 1 1
0 0 1 0 1 0 1 0 0
0 1 1 0 1 1 1 0 1
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by lockers:
Locker Mode Count Status ----------------- Object ---------------
4 dd= 9 locks held 1 write locks 0 pid/thread 5979/3080828608
4 READ 1 HELD ./db.db handle 0
5 dd= 8 locks held 0 write locks 0 pid/thread 5979/3072416656
6 dd= 7 locks held 0 write locks 0 pid/thread 5979/3073469328
7 dd= 6 locks held 0 write locks 0 pid/thread 5979/3073469328
8 dd= 5 locks held 0 write locks 0 pid/thread 5979/3073469328
9 dd= 4 locks held 0 write locks 0 pid/thread 5979/3072416656
a dd= 3 locks held 1 write locks 0 pid/thread 5979/3073469328
a READ 1 WAIT ./db.db page 21
a READ 2 HELD ./db.db page 20
b dd= 2 locks held 1 write locks 0 pid/thread 5979/3075574672
b READ 1 WAIT ./db.db page 21
b READ 2 HELD ./db.db page 20
c dd= 1 locks held 0 write locks 0 pid/thread 5979/3075574672
800054d9 dd= 0 locks held 1 write locks 1 pid/thread 5979/3074522000expires 05-05-12:41:36.048050000
800054d9 WRITE 2 HELD ./db.db page 21
800054da dd= 0 locks held 0 write locks 0 pid/thread 5979/3072416656
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by object:
Locker Mode Count Status ----------------- Object ---------------
800054d9 WRITE 2 HELD ./db.db page 21
a READ 1 WAIT ./db.db page 21
b READ 1 WAIT ./db.db page 21
a READ 2 HELD ./db.db page 20
b READ 2 HELD ./db.db page 20
4 READ 1 HELD ./db.db handle 0
The number of locks and lockers is somewhat low at 5,000 each, this was intentional since the same error occurs with larger numbers of locks/lockers it simply takes longer to occur. I have reviewed this output and nothing out of the ordinary seems to be occurring as far as I can tell.
Any additional insight would be appreciated.Thanks to both of you for your suggestions.
I have still noticing the same issue with very similar output etc so I wont repost that. After running it some more I have started seeing another error message, it looks like its very similar and hopefully with make the issue more clear.
Here is the output of the error file:
TAS unlock failed: lock already unlocked
PANIC: Permission denied
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__os_stack+0x2b) [0xb7ee585f]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__os_abort+0x1d) [0xb7ee1bb1]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__env_panic+0xa8) [0xb7e75b8e]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__db_tas_mutex_unlock+0xa5) [0xb7d72245]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so [0xb7e27d04]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__lock_detect+0x129) [0xb7e268bf]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__lock_get_internal+0x1434) [0xb7e23504]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__lock_vec+0x167) [0xb7e20d3c]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__db_lget+0x45c) [0xb7e80fe2]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so [0xb7d7a0a5]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so [0xb7d766ce]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__dbc_get+0x598) [0xb7e6ba29]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(__dbc_get_pp+0x11f) [0xb7e7c0ec]
/usr/local/BerkeleyDB.4.7/lib/libdb_cxx-4.7.so(_ZN3Dbc3getEP3DbtS1_j+0x3f) [0xb7d66feb]
...(user code stack layers)...
/lib/tls/i686/cmov/libpthread.so.0 [0xb79a950f]
/lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb7a9ea0e]
Here is the output of the waits for table:
Waiter: Waiting on:
80002249/50: 957608
6/50: 80002249 957208
Waitsfor array
Waiter: Waiting on:
8000224a/28: 957288
a/28: 8000224a 957608
Waitsfor array
Waiter: Waiting on:
8000224c/22: 957608
6/22: 8000224c 957368
Waitsfor array
Waiter: Waiting on:
8000224c/22: 957608
6/22: 8000224c 957368
4/22: 8000224c 957048
Waitsfor array
Waiter: Waiting on:
8000224d/25: 957528
7/25: 8000224d 957608
Waitsfor array
Waiter: Waiting on:
8000224d/25: 957528
7/25: 8000224d 957608
6/25: 8000224d 957208
Waitsfor array
Waiter: Waiting on:
8000224d/25: 957528
7/25: 8000224d 957608
6/25: 8000224d 957208
4/25: 8000224d 957288
Waitsfor array
Waiter: Waiting on:
80002251/10: 957048
a/10: 80002251 957128
Waitsfor array
Waiter: Waiting on:
80002257/39: 80002254 957368
80002254/39: 957288
Waitsfor array
Waiter: Waiting on:
80002258/14: 957048
4/14: 80002258 957608
Waitsfor array
Waiter: Waiting on:
80002258/14: 957048
8/14: 80002258 957208
4/14: 80002258 957608
Waitsfor array
Waiter: Waiting on:
80002259/39: 80002257 957448
80002258/14: 957048
80002257/39: 957368
8/14: 80002258 957208
4/14: 80002258 957608
Waitsfor array
Waiter: Waiting on:
80002259/39: 957448
8/39: 80002259 957288
7/39: 80002259 957048
6/39: 80002259 957528
Waitsfor array
Waiter: Waiting on:
80002259/0: 0
80002257/0: 0
Waitsfor array
Waiter: Waiting on:
8000225a/40: 956968
7/40: 8000225a 956888
Waitsfor array
Waiter: Waiting on:
8000225a/40: 956968
7/40: 8000225a 956888
4/40: 8000225a 957608
It looks like there is a similar pattern here at the end with the two entries waiting on zero ("80002259/0: 0 80002257/0: 0"), which is why I suspect its the same error just manifesting itself in a slightly different manner.
I am using lock detection, I currently have it set to use DB_LOCK_MAXLOCKS, I have tried others as well with not change in behavior.
Most of my transaction code takes the following form, so if the get is successful (the id exists) then the data is updated and written back to the database. If an exception is thrown then it is caught and the transaction is aborted. As far as I can tell this should not leave and transaction handles left open or anything along those lines as the error message suggests.
void do_txn()
DbTxn *txn = NULL;
try
db->txn_begin(NULL, &txn, 0);
Data d;
//does a db->get using the txn pointer and a DB_RMW lock
//returns do_get returns false if the id does not exist
bool success = do_get(id, &d, txn);
if( !success )
txn->abort();
return;
//update data as necessary
//does a db->put using the txn pointer
do_put(id, &d, txn);
txn->commit(0);
} catch (DbDeadlockException &de) {
cout << de.what() << endl;
if( txn != NULL )
txn->abort();
} -
JNDI tree replicated to an external global naming service
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume BedardYes, you can use federation do achieve this but remember federation is
just putting a refence that points to the original JNDI provider and
doesn't really give you replication of the entire JNDI namespace.
Guillaume Bedard wrote:
Hi!
Can you elaborate as to what makes it impossible?
What if we "federate" the two clusters, which have their
own autonomous naming systems, by binding a reference to
these naming systems in another naming service?
Thanks,
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
No
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3cab4a00$[email protected]..
More specifically, I would like be able to join two clusters
(each having their own cluster-wide replicated naming tree)
by replicating their bindings into a global naming tree,
possibly hosted by a dedicated "jndi" server.
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
My immediate response would be 'No', but I am confused as to what
are
you
trying to achieve?
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3ca9cd9c$[email protected]..
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard -
How can 2 non-global zones share a singe ethernet?
This may be a very basic question. I am new the this board and trying to learn more about the Solaris Zone.
I am trying to find out whether sharing an ethernet card between two non-global zones is possible.
Where can I get additional infor on this topic?
Thanks,I just found the answer to my question. Thanks, Can you post a link to where you found the answer?
Birdman >>I'm not exactly sure what he found, but you might try this link, to the zones documentation:
http://docs.sun.com/db/doc/817-1592/6mhahuos1?a=view#z.admin.ov-12
The answer to the question is "yes" you can do this, and in fact it is somewhat trivial. We've long had a feature in Solaris called "logical network interfaces". This allows multiple logical interfaces to be defined atop a single physical one. Zones uses this feature and creates logical interfaces atop a single virtual interface. You can even have multiple network interfaces assigned to the same zone, without any problem.
-dp -
Enregistrer variables globales
Bonjour,
Dans les variables globales, il est possible d'attribuer une valeur par défaut.
Est-il possible de changer cette valeur par défaut ? En fait, je souhaiterais, chaque fois que je rentre une valeur dans une variable globale, que cette valeur devienne celle par défaut.
Merci d'avance.Oui c'est possible.
Comme toute valeur par defaut, tu peux soit le faire a partir du controle en cliquant du bouton droit de la sourie et choisir que cette valeur soit par defaut.
Ou a travers le menu d'edition et choisir de mettre toutes les valeurs a defaut.
Dans les 2 cas, il faut sauvegarder le fichier.
Pour accomplir de meme pendant que le VI roule, il faut utiliser des "property nodes" (je ne me souviens pas du terme francais - desole). Il faut encore une fois utiliser (si je me souviens bien) un "invoke node" afin de sauvegarder le VI globale apresavoir defini les valeurs par defaut.
R -
Change Query Area from Standard to Global
Hi,
I am trying to change the queryarea from standard to global. is it possible to do this or vice versa?
Thnaks in advance
Regards
Rakshanhi Rakshan,
you can do this with program RSAQR3TR.
hope this helps
ec -
Is it possible to ignore postings from specific users
Hello,
is it possible to create a "black list" that will filter out postings from specific users?
Regards
ThomasIntriguingly this answer seems to suggest a global one is possible.
Is it like Survivor and we get to vote who goes on it?
Maybe you are looking for
-
Change documents cannot be generated
When trying to approve an admin charm we are getting warning : change documents cannot be generated Diagnosis Change Documents cannot be generated. System Response The status is reset, the action is canceled. Procedure Your Change Request Document co
-
BAPI or USER EXIT for MIRO: Change PO reference amount (on-line)
Hi, I need to find a BAPI or USER EXIT for TX MIRO to change/modify the PO reference amount for the selected positions (using the given checkbox) just after selecting them (when pressing ENTER). Any ideas? Thanks.
-
Hi All, Is there anyway by which I can get the output of a query in a browser? Regarrds, Amit
-
I am new to LR 1.3.1. I am using Windows Vista. I have been away from photo editing and decided to jump back in with LR. I have the following questions/issues: I have saved files from camera onto a cd. I then imported the pics to LR. I then did neces
-
Simultaneous Radius & TACACS+ Support on WLC
I currently have my controller configured in my Cisco Secure ACS (ver 3.3) as a Radius NAS. This is for the wireless clients authenticate using PEAP. Now I would like to setup my controller to use TACACS+ for management. I see where to configure it o