Saposcol communicates with the "outer world" using the shared memory and reader-writer mechanism. To avoid situations when part of the data
red from the shared memory is from one collection interval and second one from another, there is exclusive lock for writing and for reading.
If there are a lot of readers, it may time-to-time happen that saposcol is not able to lock memory for writing.
This message alone does not mean that you have some problems, this is just a problem that may happen in this case of communication and data exchange within one shared memory segment. But if you for example would have problems with failing calls to retireve data from ST06N transaction
#1692551 - Wrong log entry classification
Known:Warnings and error messages of dev_coll and possible problems with SAPOSCOL
http://scn.sap.com/community/netweaver-administrator/blog/2013/10/08/contain-of-devcoll-and-possible-problems-with-saposcol
SAPOSCOL Log Files
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c4/3a6c67505211d189550000e829fbbd/content.htm