Concurrent vs. Locked Checkouts

As a developer who has used open-source development tools for over 10 years, I have always subscribed to the concept of concurrent checkouts in a team environment.  Locked checkouts have always caused problems - developers checkout a module, and don't check it back in a timely manner, thereby causing delays.  Locks have a way of being lost, causing issues in the repository, etc. etc. Using tools such as CVS and SVN, I have never had an issue using concurrent checkouts.
Can people tell me what method they're using?  I'm assuming that since SAP is so large and so distributed that they use the concurrent model - can someone from SAP verify this?
If you use methods, under what circumstances do you use locked checkouts?
Thanks!

Hi Ken,
In order to maintain the lifecycle of a software component,SAP Has JDI Java dovelopement infrastructure in fact DTR is the one which miantains versioning,CBD builds components and CMS is used to tranfer the product to the main central server ..
for more info follow this URL's
http://help.sap.com/saphelp_nw04/helpdata/en/01/9c4940d1ba6913e10000000a1550b0/content.htm
http://127.0.0.1:4180/help/index.jsp?topic=/com.sap.devmanual.doc.user/16/6c40450311774a8bb16f73e450f634/frameset.htm
You need to install the JDI separately. Go to http://service.sap.com/patches -> Entry by Application Group -> SAP Net Weaver -> SAP NETWEAVER -> SAP NETWEAVER 04 -> NWDI -> JDI 6.40 -> #OS independent
https://www.sdn.sap.com/sdn/downloaditem.sdn?res=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/sap enterprise portal 6.0 sp4 netweaver stack 4 developer sneak preview download.abst
https://media.sdn.sap.com/public/eclasses/nwbcil/Java_Development_Infrastructures_files/Default.htm#nopreload=1
hope this helps you!
Regards,
RK

Similar Messages

  • Resource busy time out oracle message - Concurrency and Locks

    I have a requirement to generate gapless invoice and receipt number in our application. so i have currently used the below approach.
    a. created table with a column to hold the invoice and receipt number sequence value.
    b. whenever transaction gets succeed. i will lock the table which holds the invoice number and receipt number inorder to avoid the sequential number slipages.
    Issue
    1. since the application belongs to online payment through portal by customers, when concurrent users trying to pay and while generating receipt number's, i am facing with "resource busy time out" message frequently. Here i noticed when user1 locks the table to access the receipt number value and session is not committed or rollback and another session user2 trying to access the same resource, in this scenario i am facing this error.
    Frequency of encountering this error is low, but customer was telling us this error is show stopper and affects normal business.
    Is there any alternative solution or method can be applied to overcome this problem?
    Current SQL used in application
    cursor <cursor name> is.
    select <column_name>
    into <variable>
    from <table name>
    for update of wait 5
    update <table name> set <column name> = value + 1
    where current of <cursor name>

    1e0ea4a1-1610-4dec-a44c-4ee1f46ba1a4 wrote:
    I have a requirement to generate gapless invoice and receipt number in our application. so i have currently used the below approach.
    Engage the business and inquire WHY this "requirement" exists. I have personally never seen an audit requirement wherein invoices MUST be devoid of gaps (that's not to say they do not exist, just that I've never seen one
    They certainly must be unique, but that's what a sequence will do for you. If the business absolutely needs gapless information, then they will have to be willing to pay the price which is going to be longer transaction times (as requests queue in a busy system to get this sought after gapless resource). Your job is to explain this to them ... nothing comes without a cost.
    The only thing you can really do (assuming you engage the business and the requirement doesn't change) is ensure the transactions are designed in such a manner that
    1) they complete as fast as possible AND that the locking is done at the latest possible stage of the transaction
    2) there is no user interaction (you cannot allow the users a "review" screen of any sort ... because users get silly sometimes and go for a coffee while reviewing things)
    Cheers,

  • High concurrency optimistic locking

    Hi there,
    We have an EJB method that roughly does the following; we have a number of buckets that may or may not be full. If one or more are not full we want it to find the one with the most space available and add the item there. Our main problem here is that this method can be called upwards of 1000 times per second and we're now looking for an efficient way to solve the concurrency issue of two different calls both thinking bucket X has space left even though one of the two calls will fill it up :
    THREAD 1 : findEmptyBucket() returns BUCKET1 (1 SPOT LEFT)
    THREAD 2 : findEmptyBucket() returns BUCKET1 (1 SPOT LEFT)
    THREAD 1 : addItemToBucket(BUCKET1) <- FULL NOW
    THREAD 2 : addItemToBucket(BUCKET1) <- WRONG
    Since only optimistic locking is available in the spec for some reason I think the "EJB3" approach is basically (pseudoish) :
    while(!succeeded) {  
        try {  
            Bucket b = findEmptyBucket(...); // Will throw OptimisticLockException?  
            addItemToBucket(b, item);  
            succeeded = true;  
        catch(OptimisticLockException e) {}  
    } This seems horribly inefficient for a call that is almost guaranteed to require dozens of retries during peak hours. Is there any way to optimize this in such a way that we don't have to use optimistic locking? We're trying to solve this without using vendor specific solutions but EJB3 seems to lack the necessary functionality. Suggestions definitely welcome, evne if they are "that's the only way to do it" ;)
    Thanks!

    I think the OptimisticLockingException is thrown after-the-fact. So, if the addItemToBucket() method does a commit (flush), it will generate the exception rather than the find method. Otherwise, if there is no explicit commit call, the exception will be thrown when the EJB method that holds the while loop returns.
    If performance is critical, maybe a Stateful SessionBean with a Stateless Facade would work better. Create a Stateless SessionBean with an addItem() method and a reference to a single stateful bean. The implementation of the stateful session bean would be something like the following standalone program. The stateful bean would have an addItem() method too, but would keep track of a pool of resources internally.
    class ItemBucket { Item i; }
    class Item { String data; }
    class NoBucketsAvailableException extends Exception {}
    public class bucket {
        final static int POOL_SIZE = 4;
        ItemBucket[] bucketPool = new ItemBucket[POOL_SIZE];
        Object[] bucketLocks = new Object[POOL_SIZE];
        void initBucketPool() {
         for(int i=0; i<POOL_SIZE; i++)  {
             bucketPool[i] = new ItemBucket();
             bucketLocks[i] = new Object();
        void addItemToEmptyBucket(Item _i) throws NoBucketsAvailableException {
         int i=0;
         for(; i<POOL_SIZE; i++) {
             if( bucketPool.i == null ) { // possible empty bucket
              synchronized(bucketLocks[i]) {
              if( bucketPool[i].i == null ) {  // double checked locking
                   bucketPool[i].i = _i;
         if( i >= POOL_SIZE) { throw new NoBucketsAvailableException(); }
    public static void main(String[] args) {
         bucket app = new bucket();
         app.initBucketPool();
         Item item = new Item();
         item.data = "test";
         try {
         app.addItemToEmptyBucket(item);
         catch(NoBucketsAvailableException exc) {}

  • Concurrency with locks and wait/signal. Is it ok?

    Hello,
    I'm relatively new in concurrency. I've write this code that seems to work, but I'm not sure if there is any error (the concurrency concepts are not still clear for me).
    In the following class "diskFile", I'll start 10 threads executing the class "diskCacheDataOneCall". The question is that the "populateCacheFromDisk" method should wait until 10 threads are finished and, if any thread produces an error, interrupt all threads and finish.
    The code seems to work, but I have some questions like if I should synchronize the static variables Lock and Condition before using them.
    Anyway, I'd like that an "expert" on concurrency tells me if this code is acceptable, or what kind of improvements can do (or, if there is some mistake, how to correct it).
    I've spent many time reading tutorials about concurrency, and this is the result. Really, I'm not sure if I'm doing the things well, that's why I need the opinion of an expert in order to get better on concurrency.
    Thanks in advance.
    public class diskFile
    // Static variables for threading.
    public static Lock lock = null;
    public static Condition cdFinished = null;
    public static int numActiveThreads = 0;
    public static Exception loadException = null;
    // Main function
    public static void populateCacheFromDisk() throws cacheServletException
    ArrayList<Thread> arrThread = new ArrayList<Thread>();
    // Init static variables.
    lock      = new ReentrantLock();
    cdFinished      = lock.newCondition();     
    numActiveThreads = 0;
    loadException = null;
    try
    // Iterate 10 times (for simplicity) ...
    for (int i = 0; i < 10; i++)
    // Create THREAD and store its reference
    Thread thr = new Thread(new diskCacheDataOneCall());
    thr.start();
    arrThread.add(thr);
    // Increment "numActiveThreads"
    lock.lock();
    numActiveThreads++;
    lock.unlock();
    // Her we wait while no error happens and still active threads
    lock.lock();
    while ( (loadException == null) && (numActiveThreads > 0) )
    cdFinished.await();
    // If an error happens in any thread, then interrupt every active thread.
    if (loadException != null)
    for (int i = 0; i < arrThread.size(); i++)
    Thread thr = arrThread.get(i);
    if (thr.isAlive()) thr.interrupt();
    throw loadException;
    catch (Exception e) { throw new cacheServletException(); }
    finally { lock.unlock(); }
    public class diskCacheDataOneCall implements Runnable
    public diskCacheDataOneCall() {}     
    public void run()
    try
         diskFile.getCacheDataFromDiskOneCall(); // Load data from disk.
    // Decrement "numActiveThreads"
         diskFile.lock.lock();
         diskFile.numActiveThreads--;
    catch (Exception e)
    diskFile.lock.lock();
    diskFile.loadException = e;
    finally
    // Always signal and unlock.
    diskFile.cdFinished.signal();
    diskFile.lock.unlock();
    }

    Hello David,
    Sorry but the code does not work. An IllegalMonitorStateException is throwed. Here I show you a simplified version (now with ThreadPoolExecutor):
       // Main class (it triggers "maxActive" threads)
       Lock lock  = new ReentrantLock();
       Condition cdFinished = lock.newCondition();       
       numActiveThreads = 0;
       loadException = null;
       try
        ExecutorService ex = Executors.newFixedThreadPool(numActiveThreads);
        for (int i = 0; i < numActiveThreads; i++) ex.execute(arrTasks.get(i));
        lock.lock();
        while ( (loadException == null) && (numActiveThreads > 0) )
                   cdFinished.await();
        ex.shutdown();
       catch (Exception e) { throw e; }
       finally { lock.unlock(); }
      // Every thread.
      public void run()
       try
        doSomething();
        diskFile.lock.lock();
        diskFile.numActiveThreads--;
       catch (Exception e)
        diskFile.lock.lock();
        diskFile.loadException = cse;
       finally
        diskFile.cdFinished.signal();
        diskFile.lock.unlock();
      }The exception is:
    // Fail in the "signal" (finally section)
    Exception in thread "pool-1-thread-1" java.lang.IllegalMonitorStateException
    at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.signal(AbstractQueuedSynchronizer.java:1666)
    at com.vcfw.cache.cache.disk.diskCacheDataOneCall.run(diskCacheDataOneCall.java:44)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)
    // Fail in the "unlock" (finally section)
    Exception in thread "pool-1-thread-2" java.lang.IllegalMonitorStateException
    at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:125)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1102)
    at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:431)
    at com.vcfw.cache.cache.disk.diskCacheDataOneCall.run(diskCacheDataOneCall.java:43)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)
    Some threads fail executing the signal, and some threads fail executing ythe unlock. An IllegalMonitorStateException seems to mean that the lock was not acquired by the thread, but I'm not able to see the mistake.
    Can you help me?
    Thanks.

  • Thread concurrency - spin lock question

    Hi everyone,
    I want to enforce some concurrency in my code so that only 5 threads are running at a time. This is quite easy to do, but I just want to know if it would be more efficent to have a spin lock like this:
    while( nActiveThreads >= 5 ){ }
    or have some kind of sleep method in the loop so that it's not continually spinning in the loop and only checks every 50 milliseconds.
    while( nActiveThreads > 5 ) {
    try {
    Thread.sleep(50);
    } catch (Exception e) {
    Any thoughts?
    BBB

    I recommend looking at the java.util.concurrent package, specifically at Executors and ExecutorService classes. You can choose from several different types of thread scheduler, telling them how many threads you with them to use.

  • Concurrent DB Locking

    Hi,
    I am using the Berkeley's CDB type to create a database. The access method is BTree. In the application, typically there will be a single writer process that keeps inserting/updating records in this DB. There is another reader process (multi-threaded). Each of the threads in this process opens a READ Cursor on this DB, fetches some records based on certain filters and closes the cursor when done.
    What happens here is that when any of the reader threads opens the Cursor, the Wrter process is blocked, unless the Reader thread closes the Cursor. This means that the Reader creates a database-level Read-lock. How can this be optimized?
    Another question here is that, if any Reader thread is killed, the writer is blocked indefinitely. I know that there should be a dead-lock detector run periodically which will free locks appropriately. But without this dead-lock detector running, isnt there an optimized way of implementing a solution for this?
    Regards,
    Ravi Nathwani

    Hello,
    From the documention:
    http://www.oracle.com/technology/documentation/berkeley-db/db/ref/cam/intro.html
    Read cursors may open and perform reads without blocking
    while a write cursor is extant. However, any attempts to
    actually perform a write, either using the write cursor
    or directly using the DB->put or DB->del methods, will block
    until all read cursors are closed. This is how the
    multiple-reader/single-writer semantic is enforced, and prevents
    reads from seeing an inconsistent database state that may be an
    intermediate stage of a write operation.
    This sounds like your situation.
    Two of the sequences which can cause a thread to block itself
    indefinitely are:
    1. Keeping a cursor open while issuing a DB->put or
    DB->del access method call.
    2. Not testing Berkeley DB error return codes (if any
    cursor operation returns an unexpected error, that cursor
    must still be closed).
    Could you be running into these?
    Thanks,
    Sandra

  • Regarding Lock

    Hi
    I have a select statement which is being excessed by 2 processes at the same time and is showing a dead lock error when second process executes it . Please let me know how to use parallel process in a sql my query is
    select * from xyz ;
    I have tried using FOR UPDATE also and it didnt work

    > IMPORTANT: A select for update will never cause a dead lock.
    <p>
    Wrong. That should have been written like this:<br>
    <h3>IMPORTANT: A select for update will never cause a dead lock!!!!</h3>
    <p>
    <p>
    > Voilà, that is the solution.
    <p>
    Not really - that is the identification of the problem. The solution is to write code that groks how concurrency and locking work in Oracle. Which is why reading the Oracle® Database Application Developer's Guide - Fundamentals is mandatory for all Oracle developers.
    <p>
    If you write code that runs against or on an Oracle instance.. and you have not read and understood this manual.. you only have yourself to blame for all the problems and frustrations you will have using Oracle.

  • How to build a lock escalation tree?

    Hello!
    Concurrent users lock many rows in different tables. Sometimes
    one session waits to lock row, which is locked by another
    session.
    Locks are made by SQL statements.
    I would like to present tree of SQL statements which lock (first
    level) and as children SQL - statements waiting for release lock
    by their parents.
    It would be very helpul in finding dependencies and app places,
    where deadlock can occur.
    Do you know system SQL statement or tool, which could produce
    result I need?
    TIA,
    Witek

    I modified the script I posted earlier to include the waiters SQL
    statement. You'll have to verify that this is what you're looking
    for and that it's correct. I did some simple testing and it
    seemed to work.
    set term off;
    set null ~;
    set arraysize 10
    drop table lock_holders;
    drop table dba_locks_temp;
    create table dba_locks_temp as select * from dba_locks;
    create table lock_holders as
    select w.session_id waiting_session,
    h.session_id holding_session,
    w.lock_type,
    h.mode_held,
    w.mode_requested,
    w.lock_id1,
    w.lock_id2,
    a.sql_text sql_stmnt
    from dba_locks_temp w, dba_locks_temp h, v$session s, v$sqltext
    a
    where h.blocking_others = 'Blocking'
    and h.mode_held != 'None'
    and h.mode_held != 'Null'
    and w.mode_requested != 'None'
    and w.lock_type = h.lock_type
    and w.lock_id1 = h.lock_id1
    and w.lock_id2 = h.lock_id2
    and w.session_id=s.sid(+)
    and s.sql_address = a.address
    and s.status = 'ACTIVE'
    and s.type !='BACKGROUND'
    order by a.address
    ,a.piece;
    commit;
    drop table dba_locks_temp;
    insert into lock_holders
    select holding_session, null, 'None', null, null, null, null,
    null
    from lock_holders
    minus
    select waiting_session, null, 'None', null, null, null, null,
    null
    from lock_holders;
    commit;
    /* set charwidth 17; */
    set wrap off;
    set term on;
    select substr(lpad(' ',3*(level-1)) ||
    substr(waiting_session,1,10),1,20)
    waiting_session, sql_stmnt
    from lock_holders
    connect by prior waiting_session = holding_session
    start with holding_session is null;
    set term off;
    drop table lock_holders;
    set wrap on;
    set term on;
    Here's the output it generated from a test I ran:
    WAITING_SESSION SQL_STMNT
    9 ~
    11 update emp set acct_segment1='1111111',
    acct_segment2='2222222',
    11 acct_segment3='3333333',
    acct_segment4='4444444', acct_segment5
    11 ='5555555', acct_segment6='6666666' where
    employee='AGLICK'
    If you wanted you could also add username and osuser from
    v$session to get the users Oracle userid and their network id.

  • Can not get exclusive lock on the shared drive of Azure file storage

    One of my application need exclusive access on the data folder where it writes the data.
    I have setup data folder in Z drive which is shared drive of Azure File system.
    The application is not able to get the exclusive access on the data folder and throws IO exception.
    Is that not possible with shared drive of azure file system

    Hi Subodh,
    You could refer the following link for details on how pessimistic concurrency (Exclusive lock) managed in Azure Storage:
    http://azure.microsoft.com/blog/2014/09/08/managing-concurrency-in-microsoft-azure-storage-2/
    Please be advised that an Exclusive lock on an Azure File Share is not possible using REST Protocol and need to be done using the SMB Protocol.
    You could refer the following link for details on how to manage SMB File locking:
    https://msdn.microsoft.com/en-us/library/azure/dn194265.aspx?f=255&MSPPError=-2147217396
    Hope this helps.
    Regards,
    Malar.

  • Can multiple threads write to the database?

    I am a little confused from the statement in the documentation: "Berkeley DB Data Store does not support locking, and hence does not guarantee correct behavior if more than one thread of control is updating the database at a time."
    1. Can multiple threads write to the "Simple Data Store"?
    2. Considering the sample code below which writes to the DB using 5 threads - is there a possibility of data loss?
    3. If the code will cause data loss, will adding DB_INIT_LOCK and/or DB_INIT_TXN in DBENV->open make any difference?
    #include "stdafx.h"
    #include <stdio.h>
    #include <windows.h>
    #include <db.h>
    static DB *db = NULL;
    static DB_ENV *dbEnv = NULL;
    DWORD WINAPI th_write(LPVOID lpParam)
    DBT key, data;
    char key_buff[32], data_buff[32];
    DWORD i;
    printf("thread(%s) - start\n", lpParam);
    for (i = 0; i < 200; ++i)
    memset(&key, 0, sizeof(key));
    memset(&data, 0, sizeof(data));
    sprintf(key_buff, "K:%s", lpParam);
    sprintf(data_buff, "D:%s:%8d", lpParam, i);
    key.data = key_buff;
    key.size = strlen(key_buff);
    data.data = data_buff;
    data.size = strlen(data_buff);
    db->put(db, NULL, &key, &data, 0);
    Sleep(5);
    printf("thread(%s) - End\n", lpParam);
    return 0;
    int main()
    db_env_create(&dbEnv, 0);
    dbEnv->open(dbEnv, NULL, DB_CREATE | DB_INIT_MPOOL | DB_THREAD, 0);
    db_create(&db, dbEnv, 0);
    db->open(db, NULL, "test.db", NULL, DB_BTREE, DB_CREATE, 0);
    CreateThread(NULL, 0, th_write, "A", 0, 0);
    CreateThread(NULL, 0, th_write, "B", 0, 0);
    CreateThread(NULL, 0, th_write, "B", 0, 0);
    CreateThread(NULL, 0, th_write, "C", 0, 0);
    th_write("C");
    Sleep(2000);
    }

    Here some clarification about BDB Lock and Multi threads behavior
    Question 1. Can multiple threads write to the "Simple Data Store"?
    Answer 1.
    Please Refer to http://docs.oracle.com/cd/E17076_02/html/programmer_reference/intro_products.html
    A Data Store (DS) set up
    (so not using an environment or using one, but without any of the DB_INIT_LOCK, DB_INIT_TXN, DB_INIT_LOG environment regions related flags specified
    each corresponding to the appropriate subsystem, locking, transaction, logging)
    will not guard against data corruption due to accessing the same database page and overwriting the same records, corrupting the internal structure of the database etc.
    (note that in the case of the Btree, Hash and Recno access methods we lock at the database page level, only for the Queue access method we lock at record level)
    So,
    if You want to have multiple threads in the application writing concurrently or in parallel to the same database You need to use locking (and properly handle any potential deadlocks),
    otherwise You risk corrupting the data itself or the database (its internal structure).
    Of course , If You serialize at the application level the access to the database, so that no more one threads writes to the database at a time, there will be no need for locking.
    But obviously this is likely not the behavior You want.
    Hence, You need to use either a CDS (Concurrent Data Store) or TDS (Transactional Data Store) set up.
    See the table comparing the various set ups, here: http://docs.oracle.com/cd/E17076_02/html/programmer_reference/intro_products.html
    Berkeley DB Data Store
    The Berkeley DB Data Store product is an embeddable, high-performance data store. This product supports multiple concurrent threads of control, including multiple processes and multiple threads of control within a process. However, Berkeley DB Data Store does not support locking, and hence does not guarantee correct behavior if more than one thread of control is updating the database at a time. The Berkeley DB Data Store is intended for use in read-only applications or applications which can guarantee no more than one thread of control updates the database at a time.
    Berkeley DB Concurrent Data Store
    The Berkeley DB Concurrent Data Store product adds multiple-reader, single writer capabilities to the Berkeley DB Data Store product. This product provides built-in concurrency and locking feature. Berkeley DB Concurrent Data Store is intended for applications that need support for concurrent updates to a database that is largely used for reading.
    Berkeley DB Transactional Data Store
    The Berkeley DB Transactional Data Store product adds support for transactions and database recovery. Berkeley DB Transactional Data Store is intended for applications that require industrial-strength database services, including excellent performance under high-concurrency workloads of read and write operations, the ability to commit or roll back multiple changes to the database at a single instant, and the guarantee that in the event of a catastrophic system or hardware failure, all committed database changes are preserved.
    So, clearly DS is not a solution for this case, where multiple threads need to write simultaneously to the database.
    CDS (Concurrent Data Store) provides locking features, but only for multiple-reader/single-writer scenarios. You use CDS when you specify the DB_INIT_CDB flag when opening the BDB environment: http://docs.oracle.com/cd/E17076_02/html/api_reference/C/envopen.html#envopen_DB_INIT_CDB
    TDS (Transactional Data Store) provides locking features, adds complete ACID support for transactions and offers recoverability guarantees. You use TDS when you specify the DB_INIT_TXN and DB_INIT_LOG flags when opening the environment. To have locking support, you would need to also specify the DB_INIT_LOCK flag.
    Now, since the requirement is to have multiple writers (multi-threaded writes to the database),
    then TDS would be the way to go (CDS is useful only in single-writer scenarios, when there are no needs for recoverability).
    To Summarize
    The best way to have an understanding of what set up is needed, it is to answer the following questions:
    - What is the data access scenario? Is it multiple writer threads? Will the writers access the database simultaneously?
    - Are recoverability/data durability, atomicity of operations and data isolation important for the application? http://docs.oracle.com/cd/E17076_02/html/programmer_reference/transapp_why.html
    If the answers are yes, then TDS should be used, and the environment should be opened like this:
    dbEnv->open(dbEnv, ENV_HOME, DB_CREATE | DB_INIT_MPOOL | DB_INIT_LOCK | DB_INIT_TXN | DB_INIT_LOG | DB_RECOVER | DB_THREAD, 0);
    (where ENV_HOME is the filesystem directory where the BDB environment will be created)
    Question 2. Considering the sample code below which writes to the DB using 5 threads - is there a possibility of data loss?
    Answer 2.
    Definitely yes, You can see data loss and/or data corruption.
    You can check the behavior of your testcase in the following way
    1. Run your testcase
    2.After the program exits
    run db_verify to verify the database (db_verify -o test.db).
    You will likely see db_verify complaining, unless the thread scheduler on Windows weirdly starts each thread one after the other,
    IOW no two or ore threads write to the database at the same time -- kind of serializing the writes
    Question 3. If the code will cause data loss, will adding DB_INIT_LOCK and/or DB_INIT_TXN in DBENV->open make any difference?
    Answer 3.
    In Your case the TDS should be used, and the environment should be opened like this:
    dbEnv->open(dbEnv, ENV_HOME, DB_CREATE | DB_INIT_MPOOL | DB_INIT_LOCK | DB_INIT_TXN | DB_INIT_LOG | DB_RECOVER | DB_THREAD, 0);
    (where ENV_HOME is the filesystem directory where the BDB environment will be created)
    doing this You have proper deadlock handling in place and proper transaction usage
    so
    You are protected against potential data corruption/data loss.
    see http://docs.oracle.com/cd/E17076_02/html/gsg_txn/C/BerkeleyDB-Core-C-Txn.pdf
    Multi-threaded and Multi-process Applications
    DB is designed to support multi-threaded and multi-process applications, but their usage
    means you must pay careful attention to issues of concurrency. Transactions help your
    application's concurrency by providing various levels of isolation for your threads of control. In
    addition, DB provides mechanisms that allow you to detect and respond to deadlocks.
    Isolation means that database modifications made by one transaction will not normally be
    seen by readers from another transaction until the first commits its changes. Different threads
    use different transaction handles, so this mechanism is normally used to provide isolation
    between database operations performed by different threads.
    Note that DB supports different isolation levels. For example, you can configure your
    application to see uncommitted reads, which means that one transaction can see data that
    has been modified but not yet committed by another transaction. Doing this might mean
    your transaction reads data "dirtied" by another transaction, but which subsequently might
    change before that other transaction commits its changes. On the other hand, lowering your
    isolation requirements means that your application can experience improved throughput due
    to reduced lock contention.
    For more information on concurrency, on managing isolation levels, and on deadlock
    detection, see Concurrency (page 32).

  • Errors executing bulk query when updating a Sharepoint Linked List from Access

    Hi all,
    I have a Sharepoint list that is a Linked List with MS Access. It has just under 5,000 items (4,864), thus meaning it avoids the reduction in functionality lists of greater than 5,000 items have.
    Among the list are five calculated columns. These take the information from another column (different employee numbers), and by using a formula produce a clickable link to my company's Directory page, where that particular employee's info is displayed. I'm
    not sure if these five columns are relevant to my query, but I'm mentioning them in case.
    My problem is this: Frequently when I run any query on the list that updates the list, I get this error: "There were errors executing the bulk query or sending the data to the server. Reconnect the tables to resolve the
    conflicts or discard the pending changes".
    When I review the errors, it says they conflict with errors a previous user made (with that previous user being me). It frequently highlights several columns, despite the info in them being identical, and the calculated columns (with the original showing
    the value they contained and the new showing #VALUE! (as Access can't display the formulas).
    However, if I click Retry All Changes, all the update stick and everything seems fine. Why is this happening? It's proving very annoying and is really stopping the automation of my large number of queries. A list of 5000 items isn't particular big (and they've
    got roughly 100 columns, although I didn't think that was too large either, given Excel's 200+ column limit).
    Is this due to poor query design and SQL? Is this due to connectivity issues (which I doubt, as my line seems perfect)? Is this due to Access tripping over itself and not executing the update on each row in the table, but rather executing them concurrently
    and locking itself up? I'm at wit's end about it and really need to get this sorted.
    Thanks in advance for any suggestions.

    Hi amartin903,
    According to your description, my understanding is that you got an error when you used a linked list from Access.
    The table that you are updating is a linked table that does not have a primary key or a unique index. Or, the query or the form is based on a linked table that does not have a primary key or a unique index. Please add the primary key or a unique index.
    Here is a similar post, please take a look at:
    http://social.technet.microsoft.com/Forums/en-US/545601e9-a703-4a02-8ed9-199f1ce9dac8/updating-sharepoint-list-from-access?forum=sharepointdevelopmentlegacy
    I hope this helps.
    Thanks,
    Wendy
    Wendy Li
    TechNet Community Support

  • Primary key issue with adf Entry Form.

    Hi All,
    i'm using jdev version 11.1.1.5.0
    use case: i have create simple entry form based on Eo and Vo using database table like student(enrollment no,name address)
    where enrollment no is primary key.
    so when i have create a record i have set enrollment no in entity impl class of this eo create method using some logic based on my need like(20130001)
    for that i have read highest no from database field and assign to enrollment no field when user create record.
    so when user create record second time then enrollment no is 20130002. and other detail like name and address user fill and commit record. and it is fine.
    but problem is that when two user access same form at a time and create record so both have get same primary key like 20130003 because in current time in database maximum value is 20130002.
    so which user  commit record first it record will save on database and second user get error message because of primary key violation.
    so my question is that where we generate primary key value for record so when multiple user access form have get different primary key value. and in my use case i can't use sequence and any autoincrement no
    because i have patter for primary key.
    Thanks in Advance
    Manish

    Hi,
    Dimitar and Frank
    thank for reply.
    How can i apply non-concurrent DB lock can you please explain.(because lock method on entity impl not work when user create new row as per documentation)
    http://docs.oracle.com/cd/B14099_19/web.1012/b14022/oracle/jbo/server/EntityImpl.html#lock__
    i have write following line of code in entity impl class to set primary key value(reqid)-
        @Override
        protected void prepareForDML(int i, TransactionEvent transactionEvent) {
             super.prepareForDML(i, transactionEvent);
            this.setReqid(genReqid());
        public String genReqid() {
            String reqby = this.getReqby();
            String qry =
                "SELECT nvl(MAX(TO_NUMBER(SUBSTR(REQID,7))),0)+1  FROM STM_REQHDR WHERE REQBY=? AND REQTYPE<>'M' and substr(reqid,1,2)<>'MT' AND SUBSTR(REQID,1,3)<>'PAY'";
            PreparedStatement ps = null;
            String no = "";
            try {
                ps = getDBTransaction().createPreparedStatement(qry, 0);
                ps.setString(1, reqby);
                ResultSet rs = ps.executeQuery();
                if (rs.next()) {
                    no = rs.getString(1);
                ps.close();
            } catch (Exception e) {
                System.out.println("Exception in Gen req id ==>" + e);
            String reqno = reqby + String.format("%6s", no).replace(' ', '0');
            return reqno;
    but when i run form in debug mode and two user commit concurrent manner only one time code block is executed who first commit. and second user got error message.
    thanks
    Manish

  • Macosx with a lot of disk activity

    This is the console log which is full of entries. Is it normal?
    3/20/13 12:28:28.457 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-969"
    3/20/13 12:28:28.457 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-421"
    3/20/13 12:28:28.458 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-563"
    3/20/13 12:28:28.458 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-603"
    3/20/13 12:28:28.458 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-948"
    3/20/13 12:28:28.459 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-745"
    3/20/13 12:28:28.459 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-887"
    3/20/13 12:28:28.459 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-927"
    3/20/13 12:28:28.460 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-684"
    3/20/13 12:28:28.460 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-724"
    3/20/13 12:28:28.460 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-481"
    3/20/13 12:28:28.460 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-521"
    3/20/13 12:28:28.461 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-663"
    3/20/13 12:28:28.461 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-703"
    3/20/13 12:28:28.461 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-845"
    3/20/13 12:28:28.462 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-987"
    3/20/13 12:28:28.462 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-784"
    3/20/13 12:28:28.462 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-824"
    3/20/13 12:28:28.463 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-581"
    3/20/13 12:28:28.463 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-621"
    3/20/13 12:28:28.463 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-763"
    3/20/13 12:28:28.464 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-803"
    3/20/13 12:28:28.464 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-945"
    3/20/13 12:28:28.464 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-884"
    3/20/13 12:28:28.465 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-924"
    3/20/13 12:28:28.465 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-681"
    3/20/13 12:28:28.465 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-721"
    3/20/13 12:28:28.466 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-863"
    3/20/13 12:28:28.466 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-50"
    3/20/13 12:28:28.466 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-903"
    3/20/13 12:28:28.467 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-984"
    3/20/13 12:28:28.467 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-781"
    3/20/13 12:28:28.467 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-821"
    3/20/13 12:28:28.468 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-963"
    3/20/13 12:28:28.468 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-881"
    3/20/13 12:28:28.468 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-921"
    3/20/13 12:28:28.469 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-981"
    3/20/13 12:28:28.470 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-179"
    3/20/13 12:28:28.471 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-219"
    3/20/13 12:28:28.471 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-158"
    3/20/13 12:28:28.471 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-137"
    3/20/13 12:28:28.472 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-279"
    3/20/13 12:28:28.472 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-319"
    3/20/13 12:28:28.472 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-258"
    3/20/13 12:28:28.473 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-197"
    3/20/13 12:28:28.473 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-237"
    3/20/13 12:28:28.473 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-379"
    3/20/13 12:28:28.474 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-419"
    3/20/13 12:28:28.474 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-358"
    3/20/13 12:28:28.474 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-297"
    3/20/13 12:28:28.474 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-337"
    3/20/13 12:28:28.475 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-479"
    3/20/13 12:28:28.475 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-519"
    3/20/13 12:28:28.476 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-113"
    3/20/13 12:28:28.476 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-458"
    3/20/13 12:28:28.476 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-255"
    3/20/13 12:28:28.477 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-397"
    3/20/13 12:28:28.477 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-437"
    3/20/13 12:28:28.477 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-194"
    3/20/13 12:28:28.478 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-234"
    3/20/13 12:28:28.478 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-579"
    3/20/13 12:28:28.479 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-619"
    3/20/13 12:28:28.479 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-173"
    3/20/13 12:28:28.479 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-213"
    3/20/13 12:28:28.480 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-558"
    3/20/13 12:28:28.480 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-355"
    3/20/13 12:28:28.481 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-497"
    3/20/13 12:28:28.481 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-537"
    3/20/13 12:28:28.481 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-294"
    3/20/13 12:28:28.481 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-334"
    3/20/13 12:28:28.482 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-679"
    3/20/13 12:28:28.482 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-719"
    3/20/13 12:28:28.482 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-273"
    3/20/13 12:28:28.483 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-313"
    3/20/13 12:28:28.483 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-658"
    3/20/13 12:28:28.483 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-455"
    3/20/13 12:28:28.484 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-597"
    3/20/13 12:28:28.484 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-637"
    3/20/13 12:28:28.484 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-394"
    3/20/13 12:28:28.485 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-434"
    3/20/13 12:28:28.485 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-191"
    3/20/13 12:28:28.485 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-779"
    3/20/13 12:28:28.486 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-231"
    3/20/13 12:28:28.486 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-819"
    3/20/13 12:28:28.486 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-373"
    3/20/13 12:28:28.487 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-413"
    3/20/13 12:28:28.487 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-758"
    3/20/13 12:28:28.487 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-555"
    3/20/13 12:28:28.488 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-697"
    3/20/13 12:28:28.488 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-737"
    3/20/13 12:28:28.488 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-494"
    3/20/13 12:28:28.489 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-534"
    3/20/13 12:28:28.489 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-291"
    3/20/13 12:28:28.489 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-879"
    3/20/13 12:28:28.490 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-331"
    3/20/13 12:28:28.490 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-919"
    3/20/13 12:28:28.490 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-473"
    3/20/13 12:28:28.490 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-513"
    3/20/13 12:28:28.491 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-858"
    3/20/13 12:28:28.491 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-655"
    3/20/13 12:28:28.491 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-797"
    3/20/13 12:28:28.492 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-837"
    3/20/13 12:28:28.492 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-594"
    3/20/13 12:28:28.492 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-634"
    3/20/13 12:28:28.493 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-391"
    3/20/13 12:28:28.493 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-979"
    3/20/13 12:28:28.493 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-431"
    3/20/13 12:28:28.494 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-573"
    3/20/13 12:28:28.494 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-613"
    3/20/13 12:28:28.494 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-958"
    3/20/13 12:28:28.495 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-755"
    3/20/13 12:28:28.495 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-897"
    3/20/13 12:28:28.495 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-937"
    3/20/13 12:28:28.496 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-694"
    3/20/13 12:28:28.496 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-734"
    3/20/13 12:28:28.496 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-491"
    3/20/13 12:28:28.496 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-531"
    3/20/13 12:28:28.497 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-673"
    3/20/13 12:28:28.498 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-713"
    3/20/13 12:28:28.498 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-855"
    3/20/13 12:28:28.498 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-997"
    3/20/13 12:28:28.499 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-794"
    3/20/13 12:28:28.499 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-834"
    3/20/13 12:28:28.499 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-591"
    3/20/13 12:28:28.499 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-631"
    3/20/13 12:28:28.500 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-773"
    3/20/13 12:28:28.500 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-813"
    3/20/13 12:28:28.500 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-955"
    3/20/13 12:28:28.501 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-894"
    3/20/13 12:28:28.501 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-934"
    3/20/13 12:28:28.501 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-691"
    3/20/13 12:28:28.502 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-731"
    3/20/13 12:28:28.502 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-873"
    3/20/13 12:28:28.502 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-913"
    3/20/13 12:28:28.503 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-994"
    3/20/13 12:28:28.503 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-791"
    3/20/13 12:28:28.503 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-831"
    3/20/13 12:28:28.504 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-973"
    3/20/13 12:28:28.504 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-891"
    3/20/13 12:28:28.504 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-931"
    3/20/13 12:28:28.505 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-991"
    3/20/13 12:28:28.506 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1199"
    3/20/13 12:28:28.507 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1089"
    3/20/13 12:28:28.507 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1098"
    3/20/13 12:28:28.507 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1169"
    3/20/13 12:28:28.508 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1059"
    3/20/13 12:28:28.508 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1178"
    3/20/13 12:28:28.508 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1068"
    3/20/13 12:28:28.509 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1249"
    3/20/13 12:28:28.509 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1139"
    3/20/13 12:28:28.509 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1187"
    3/20/13 12:28:28.510 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1029"
    3/20/13 12:28:28.510 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1077"
    3/20/13 12:28:28.510 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1258"
    3/20/13 12:28:28.511 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1148"
    3/20/13 12:28:28.511 PM
    Numbers[819]
    NameKeyHashSet and ObjectHashMap out of sync: object map entry for __NSDictionaryI 0x5659a70 references name "NSMutableDictionary-38" instead of "NSMutableDictionary-1038"
    3/20/13 12:28:28.511 PM
    Numbers[819]
    *** process 819 exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    3/20/13 12:28:36.229 PM
    WindowServer[128]
    CGXDisableUpdate: UI updates were forcibly disabled by application "Numbers" for over 1.00 seconds. Server has re-enabled them.
    3/20/13 12:28:37.828 PM
    WindowServer[128]
    reenable_update_for_connection: UI updates were finally reenabled by application "Numbers" after 2.60 seconds (server forcibly re-enabled them after 1.00 seconds)
    3/20/13 12:28:53.964 PM
    com.apple.launchd[1]
    (com.apple.coremedia.videodecoder[2893]) Exit timeout elapsed (20 seconds). Killing
    3/20/13 12:29:36.456 PM
    com.apple.usbmuxd[20]
    _heartbeat_failed heartbeat detected detach for device 0x32-192.168.1.8:0!
    3/20/13 12:30:12.366 PM
    mdworker[3358]
    Unable to talk to lsboxd
    3/20/13 12:30:12.445 PM
    sandboxd[3359]
    ([3358]) mdworker(3358) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:30:12.000 PM
    kernel[0]
    Sandbox: sandboxd(3359) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:32:04.036 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c92700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.AddressBook.PushNotification-user=501 darkWakeEnabled-env=production
    3/20/13 12:32:04.037 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c92700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.AddressBook.PushNotification-user=501 darkWakeEnabled-env=production
    3/20/13 12:32:04.037 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c92700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.AddressBook.PushNotification-user=501 darkWakeEnabled-env=production
    3/20/13 12:32:13.664 PM
    mdworker[3368]
    Unable to talk to lsboxd
    3/20/13 12:32:13.744 PM
    sandboxd[3369]
    ([3368]) mdworker(3368) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:32:14.000 PM
    kernel[0]
    Sandbox: sandboxd(3369) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:34:05.000 PM
    kernel[0]
    CODE SIGNING: cs_invalid_page(0x1000): p=3373[GoogleSoftwareUp] clearing CS_VALID
    3/20/13 12:34:46.637 PM
    WindowServer[128]
    CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    3/20/13 12:34:46.638 PM
    loginwindow[39]
    find_shared_window: WID -1
    3/20/13 12:34:46.638 PM
    loginwindow[39]
    CGSGetWindowTags: Invalid window 0xffffffff
    3/20/13 12:34:46.638 PM
    loginwindow[39]
    find_shared_window: WID -1
    3/20/13 12:34:46.638 PM
    loginwindow[39]
    CGSSetWindowTags: Invalid window 0xffffffff
    3/20/13 12:34:46.655 PM
    loginwindow[39]
    ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
    3/20/13 12:34:46.966 PM
    WindowServer[128]
    Created shield window 0x30a for display 0x04271b00
    3/20/13 12:34:46.967 PM
    WindowServer[128]
    device_generate_desktop_screenshot: authw 0x7fd1a8e73240(2000), shield 0x7fd1a8e9e3e0(2001)
    3/20/13 12:34:46.997 PM
    WindowServer[128]
    device_generate_lock_screen_screenshot: authw 0x7fd1a8e73240(2000), shield 0x7fd1a8e9e3e0(2001)
    3/20/13 12:36:14.916 PM
    mdworker[3374]
    Unable to talk to lsboxd
    3/20/13 12:36:14.999 PM
    sandboxd[3375]
    ([3374]) mdworker(3374) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:36:15.000 PM
    kernel[0]
    Sandbox: sandboxd(3375) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:39:18.591 PM
    com.apple.usbmuxd[20]
    _heartbeat_failed heartbeat detected detach for device 0x33-192.168.1.8:0!
    3/20/13 12:40:16.162 PM
    mdworker[3378]
    Unable to talk to lsboxd
    3/20/13 12:40:16.240 PM
    sandboxd[3379]
    ([3378]) mdworker(3378) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:40:16.000 PM
    kernel[0]
    Sandbox: sandboxd(3379) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:41:06.703 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fd1a8e73240(2000), shield 0x7fd1a8e9e3e0(2001), lock state 3
    3/20/13 12:41:06.703 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: err 0x0
    3/20/13 12:41:06.706 PM
    WindowServer[128]
    Created shield window 0x30b for display 0x003f003d
    3/20/13 12:41:06.706 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fd1a8e73240(2002), shield 0x7fd1a8e9e3e0(2001), lock state 3
    3/20/13 12:41:06.706 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: err 0x0
    3/20/13 12:42:27.700 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:42:27.702 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:42:27.706 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:42:27.706 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:44:10.509 PM
    WindowServer[128]
    CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    3/20/13 12:44:10.510 PM
    loginwindow[39]
    find_shared_window: WID -1
    3/20/13 12:44:10.510 PM
    loginwindow[39]
    CGSGetWindowTags: Invalid window 0xffffffff
    3/20/13 12:44:10.510 PM
    loginwindow[39]
    find_shared_window: WID -1
    3/20/13 12:44:10.510 PM
    loginwindow[39]
    CGSSetWindowTags: Invalid window 0xffffffff
    3/20/13 12:44:10.526 PM
    loginwindow[39]
    ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
    3/20/13 12:44:10.741 PM
    WindowServer[128]
    Created shield window 0x30f for display 0x04271b00
    3/20/13 12:44:10.741 PM
    WindowServer[128]
    device_generate_desktop_screenshot: authw 0x7fd1a8e393e0(2000), shield 0x7fd1a8ca4410(2001)
    3/20/13 12:44:10.765 PM
    WindowServer[128]
    device_generate_lock_screen_screenshot: authw 0x7fd1a8e393e0(2000), shield 0x7fd1a8ca4410(2001)
    3/20/13 12:44:17.466 PM
    mdworker[3391]
    Unable to talk to lsboxd
    3/20/13 12:44:17.545 PM
    sandboxd[3392]
    ([3391]) mdworker(3391) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:44:17.000 PM
    kernel[0]
    Sandbox: sandboxd(3392) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:48:18.677 PM
    mdworker[3397]
    Unable to talk to lsboxd
    3/20/13 12:48:18.758 PM
    sandboxd[3398]
    ([3397]) mdworker(3397) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:48:19.000 PM
    kernel[0]
    Sandbox: sandboxd(3398) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:48:59.270 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fd1a8e393e0(2000), shield 0x7fd1a8ca4410(2001), lock state 3
    3/20/13 12:48:59.271 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: err 0x0
    3/20/13 12:48:59.274 PM
    WindowServer[128]
    Created shield window 0x310 for display 0x003f003d
    3/20/13 12:48:59.274 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fd1a8e393e0(2002), shield 0x7fd1a8ca4410(2001), lock state 3
    3/20/13 12:48:59.274 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: err 0x0
    3/20/13 12:49:04.481 PM
    com.apple.usbmuxd[20]
    _heartbeat_failed heartbeat detected detach for device 0x34-192.168.1.8:0!
    3/20/13 12:50:26.733 PM
    lsboxd[849]
    @AE relay 4755524c:4755524c
    3/20/13 12:50:34.487 PM
    WebProcess[3406]
    objc[3406]: Object 0x7feb9241c8f0 of class NSUserDefaults autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
    3/20/13 12:51:05.798 PM
    SystemUIServer[823]
    [QL] Can't get plugin bundle info at XTUM/ -- file://localhost/
    3/20/13 12:51:06.142 PM
    quicklookd[3409]
    [QL] Can't get plugin bundle info at XTUM/ -- file://localhost/private/tmp/
    3/20/13 12:51:06.463 PM
    SystemUIServer[823]
    [QL] Can't get plugin bundle info at XTUM/ -- file://localhost/
    3/20/13 12:51:10.273 PM
    VDCAssistant[3413]
    AVF encoder error: fail to create accelerator instance
    3/20/13 12:51:10.452 PM
    FaceTime[3411]
    12:51:10.450193 com.apple.AVConference: -isWidescreen: Built-in iSight supports (1280x720) @30.000030 '2vuy'
    3/20/13 12:51:12.856 PM
    com.apple.SecurityServer[26]
    Killing auth hosts
    3/20/13 12:51:12.856 PM
    com.apple.SecurityServer[26]
    Session 100073 destroyed
    3/20/13 12:51:12.904 PM
    com.apple.SecurityServer[26]
    Session 100079 created
    3/20/13 12:52:40.681 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:52:40.682 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:52:40.683 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:52:40.685 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:53:16.211 PM
    com.apple.XType.FontHelper[3422]
    FontHelper:  message received. (<dictionary: 0x7fdb5b41d180> { count = 2, contents =
    "query" => <string: 0x7fdb5b41d2e0> { length = 100, contents = "com_apple_ats_name_postscript == "serif" && kMDItemContentTypeTree != com.adobe.postscript-lwfn-font" }
    "restricted" => <bool: 0x7fff7cdba320>: true
    3/20/13 12:53:16.211 PM
    com.apple.XType.FontHelper[3422]
    AutoActivation:  scopes (
        "/Library/Application Support/Apple/Fonts"
    3/20/13 12:53:20.318 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:53:20.319 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:53:20.320 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:53:20.320 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:54:26.666 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:54:26.667 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:54:26.668 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:54:26.670 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:55:16.813 PM
    mdworker[3423]
    Unable to talk to lsboxd
    3/20/13 12:55:16.000 PM
    kernel[0]
    Sandbox: sandboxd(3424) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 12:55:16.898 PM
    sandboxd[3424]
    ([3423]) mdworker(3423) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:56:16.648 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:56:16.649 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:56:16.649 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:56:16.651 PM
    apsd[56]
    <APSConnectionNotificationQueue: 0x7fd078c94700>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
    3/20/13 12:56:34.086 PM
    WindowServer[128]
    CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    3/20/13 12:56:34.087 PM
    loginwindow[39]
    find_shared_window: WID -1
    3/20/13 12:56:34.087 PM
    loginwindow[39]
    CGSGetWindowTags: Invalid window 0xffffffff
    3/20/13 12:56:34.087 PM
    loginwindow[39]
    find_shared_window: WID -1
    3/20/13 12:56:34.087 PM
    loginwindow[39]
    CGSSetWindowTags: Invalid window 0xffffffff
    3/20/13 12:56:34.104 PM
    loginwindow[39]
    ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
    3/20/13 12:56:34.372 PM
    WindowServer[128]
    Created shield window 0x328 for display 0x04271b00
    3/20/13 12:56:34.372 PM
    WindowServer[128]
    device_generate_desktop_screenshot: authw 0x7fd1a8c7c270(2000), shield 0x7fd1a8e7dea0(2001)
    3/20/13 12:56:34.410 PM
    WindowServer[128]
    device_generate_lock_screen_screenshot: authw 0x7fd1a8c7c270(2000), shield 0x7fd1a8e7dea0(2001)
    3/20/13 12:58:39.663 PM
    AddressBookSourceSync[3430]
    *** -[IADomainCache init]: IA domains cache is out of date.
    3/20/13 12:58:41.653 PM
    AddressBookSourceSync[3430]
    -[ABPerson valueForProperty:com.apple.Messages.FontSize] - unknown property. This warning will be displayed only once per unknown property, per session.
    3/20/13 12:58:41.658 PM
    AddressBookSourceSync[3430]
    -[ABPerson valueForProperty:com.apple.Messages.FontColor] - unknown property. This warning will be displayed only once per unknown property, per session.
    3/20/13 12:58:41.660 PM
    AddressBookSourceSync[3430]
    -[ABPerson valueForProperty:com.apple.Messages.BalloonColor] - unknown property. This warning will be displayed only once per unknown property, per session.
    3/20/13 12:58:41.661 PM
    AddressBookSourceSync[3430]
    -[ABPerson valueForProperty:com.apple.Messages.FontFamily] - unknown property. This warning will be displayed only once per unknown property, per session.
    3/20/13 12:58:48.039 PM
    com.apple.usbmuxd[20]
    _heartbeat_failed heartbeat detected detach for device 0x35-192.168.1.8:0!
    3/20/13 12:59:18.108 PM
    mdworker[3434]
    Unable to talk to lsboxd
    3/20/13 12:59:18.192 PM
    sandboxd[3435]
    ([3434]) mdworker(3434) deny mach-lookup com.apple.ls.boxd
    3/20/13 12:59:18.000 PM
    kernel[0]
    Sandbox: sandboxd(3435) deny mach-lookup com.apple.coresymbolicationd
    3/20/13 1:02:58.486 PM
    WindowServer[128]
    handle_will_sleep_auth_and_shield_windows: releasing authw 0x7fd1a8c7c270(2000), shield 0x7fd1a8e

    Yes, you are in true.
    But, I can't understand it. Weblogic allow to execute a number of threads that
    couldn't go far in execution (they haven't resources) ... and maintains them runnable.
    But, the thread that could progress in their execution (they have the resources)
    aren't runnables ...
    The only solution is the one you say ... but I think the way weblogic schedules
    the execute threads isn't a good way.
    Thanks
    "Adam Messinger" <[email protected]> wrote:
    >
    "jlglez" <[email protected]> wrote in message
    news:3b9899a4$[email protected]..
    Ok. I have a problem with concurrency and locks with weblogic ... hereis
    my thread
    dump:
    Number of Threads of my Server: 15
    Number of Threads of my Application: 25
    LDAPPool: 5
    Yes, I know the second is bigger than the first. I try to create anscenario of
    a number of apps over the same server.It looks like the majority of your threads are waiting while attempting
    to
    get an LDAP connection. Make that pool bigger (same size as number of
    execute threads).
    Cheers!
    Adam

  • Best way to share aperture library over network on two computers?

    I've read several posts about doing this and most recommend using an external HD and just hot swapping. However, is their not a better alternative? Can I not share my library over the network, or just remote connect to the other computer?
    Thanks for the help!

    Hi Terence and Leonie,
    You can run several Aperture on the same computer as long as all Aperture are using distinct libraries.
    What Aperture does is to create a simple lock file in <your Aperture library>.aplibrary/Database/apdb The lock file contains the PID of the process. So not two Aperture could open the same library (although I don't know how good they have manage the concurrent creation, locking, verification of this lock, this is a typical and difficult software engineering problem)
    Anyway, I have not said that Aperture supports concurrent editing. That a file is a database or a simple text file, you have basically the same issues on network or in concurrent environment. So if the folder structure holds simple, flat text file or xml object or databases, it is still a bunch of files (this is a UNIX system by the way ).
    Aperture contains more than one SQLlite file, there are some at the root folder, some under Database/apdb etc. there are also XML files that could be used as database.
    Anyhow, editing a file (SQLlite, XML, txt, doc, etc.) either on a share or locally is plain similar. The drive can fail too, although much less likely than the network.
    Network file edition can have a few shortcomings, but nothing that when known can be blocking.
    Locking files over the network can however be tricky and depends largely on the network protocol used (NFS, SMB/CIFS or AFP just to name a few). In addition, if you import files from /Users/foo/Photos in Aperture (without copying them within Aperture), they might not be visible from another computer or only the previews, as the path /Users/foo/Photos is not "visible" from the other computer.
    What really is a problem when you put a file not locally is the file system type and its features. HFS+ supports extended attributes (metadata), many other file systems support these but the API (how the software, such as Aperture, access this feature) might not be similar, in addition the amount of metadata or their structure might differ from file system to another. And this is where you might lose information.
    A tool like Dropbox is pretty good at maintaining the metadata across different computers, and it has been adapted to do so for OS X specifically (and also for Linux and Windows).
    The second problem is if you would have a Mac and share via SMB (the Windows share network protocol, aka CIFS on recent Windows versions) the library, SMB might not support the reading and writing of HFS+ metadata, thus data loss might occur.
    Apple is just warning us of all these shortcomings, and advise to use local storage formatted as HFS+. Because even a local external disk formatted as NTFS or other file system could be a problem.
    However, power users who understand the risks and limitations of a network share (in general) can create a disk image on a share (even if it is SMB). As for OS X, once the disk image is mounted, it is just like any other local hard disk, it is just "slower" especially latency wise. OS X supports perfectly disk image mounted on a share, it takes care of properly synchronising it.
    Of course, due to the nature of the link between the application data and where they are stored, in case of application or OS crash, the amount of data loss could be greater than when the data are held locally.
    I hope this clarify better my post.
    Note: another shortcoming of having it on the network is: Aperture lock the library by creating a file with a process ID. If the same library is opened from another computer on the network, this other Aperture instance might see the lock file and could perhaps not find the corresponding running process. This Aperture instance might then decide to ignore the lock and proceed with opening the library. This might have some consequences.
    But I haven't developed Aperture so I don't know how it would behave

  • What is multi threading?

    Hi all,
    What is multi threading? How to implement multi threading in ABAP?
    Regards,
    Bryan

    Hi
    How the vision connector framework works
    The connector interacts with an SAP application using connector modules. The connector modules make calls to SAP's Native Interfaces and pass data (business object or event data) to and from an SAP application. The connector's flexible design enables different modules to be used for different tasks such as initializing the connector with the SAP application or passing business object data.
    Communication between the connector and an SAP application
    The connector uses SAP's Remote Function Call (RFC) library to communicate with an SAP application. SAP's RFC API allows external programs to call ABAP function modules within an SAP application.
    Processing business objects
    The connector is metadata driven. Metadata, in the WebSphere business integration system, is application-specific data that is stored in business objects and that assists a connector module in its interaction with the application. A metadata-driven connector module handles each business object that it supports based on metadata encoded in the business object definition rather than on instructions hard-coded in the connector module.
    Business object metadata includes the structure of a business object, the settings of its attribute properties, and the content of its application-specific information. Because connector modules are metadata driven, they can handle new or modified business objects without requiring modifications to the connector-module code.
    The vision connector framework uses the value of the verb application-specific information in the top-level business object to call the appropriate connector module to process the business object. The verb application-specific information provides the classname of the connector module.
    The verb application-specific information of most top-level business objects must identify the classname of the connector module. The syntax of this verb application-specific information is:
    AppSpecificInfo = PartialPackageName.ClassName,
    For example,
    AppSpecificInfo = sap.sapextensionmodule.VSapBOHandler,
    In this example, sap.sapextensionmodule is the partial package name, and VSapBOHandler is the classname. The full package name includes the com.crossworlds.connectors prefix, which the WebSphere business integration system adds to the name automatically. In other words, the full text of the example is:
    com.crossworlds.connectors.sap.sapextensionmodule.VSapBOHandler
    Note:
    The verb application-specific information of most top-level business objects must use a comma (,) delimiter after the connector classname. However, the Server verb, which is used by the RFC Server Module, is delimited instead by a semi-colon (;). For information about the Server verb, see How the RFC Server Module works and Supported verbs.
    You need not specify the package name and classname for the verb application-specific information if the business object is used:
    by the ALE Module to process application events; however, when you use the ALE Module to process service call requests, you must specify the package name and classname
    by the ABAP Extension Module, which uses the default business object handler (sap.sapextensionmodule.VSapBOHandler)
    Important:
    Customer-generated connector modules that process business objects for the RFC Server Module must specify a full package name, which must begin with bapi. For example, bapi.client.Bapi_customer_getdetail2. The full package name in this example is bapi.client, and the classname is Bapi_customer_getdetail2.
    Most business object processing is specific to each connector module. By default the connector uses the ABAP Extension Module. For more information on business object processing for the ABAP Extension Module, see Installing and customizing the ABAP Extension Module and Business object data routing to ABAP handlers. .
    For more information on specifying verb application-specific information for the ALE Module, see Event processing and Processing multiple IDocs with a wrapper business object.
    Processing multiple concurrent interactions
    The Adapter Framework can create separate threads for processing an application event and a business object request. When processing multiple requests from the integration broker, it can create multiple threads to handle multiple business object requests. For example, when InterChange Server is the integration broker, the connector can receive multiple business object requests from multiple collaborations or from a multi-threaded collaboration.
    Figure 4 illustrates the multi-threading architecture.
    Figure 4. Multi-Threading Architecture of the Connector for SAP
    Event processing
    The connector performs the following steps when handling a poll call:
    The Adapter Framework creates a single dedicated thread to handle poll calls. This thread calls the pollForEvents() method of the vision connector framework at the frequency specified in the PollFrequency configuration property.
    The thread polls SAP, which uses a dialog process to locate and return the event.
    Note:
    If the connector's MaxNumberOfConnections configuration property evaluates to a number greater than 1, the vision connector framework dedicates a connection to SAP for polling. If MaxNumberOfConnections evaluates to 1, event and service-call request processing share a single connection to SAP.
    The polling thread dies only when the connector shuts down.
    Note:
    Because the RFC Server connector agent pushes events out of SAP instead of polling for events, it spawns its own threads instead of using threads created by the connector framework. Because the ALE connector agent uses the RFC Server connector agent to access events, it also spawns its own threads instead of using threads created by the connector framework when it processes events.
    Request processing
    Independently of polling, the Adapter Framework can create multiple request-processing threads, one for each request business object. Each request thread instantiates the appropriate business object handler.
    For example, when processing business object requests from InterChange Server, the number and type of business object handlers depends on the number and type of the collaborations sending the requests:
    If multiple collaborations send business objects, each request thread instantiates a business object handler of the appropriate type.
    If a multi-threaded collaboration sends multiple business objects of the same type, the request threads instantiate an equal number of business object handlers of that type.
    If the connector's MaxNumberOfConnections configuration property evaluates to a number greater than 1, the vision connector framework dedicates one connection to SAP for polling and allocates the remaining connections to a pool used only for request processing.
    As illustrated in Figure 4, the connector performs the following steps when handling a business object request:
    The Adapter Framework creates a separate thread for each business object request. Each thread calls the doVerbFor() method of the Vision business object handler.
    If the connector's MaxNumberOfConnections configuration property evaluates to a number greater than 1, the Vision business object handler checks the vision connector framework's connection pool to determine if a connection handle is available.
    If the handle is available, the thread sends the request to SAP, which uses a dialog process to handle the request.
    If the handle is not available, the thread waits until one becomes available. Thread sequencing determines the order in which each business object handler thread claims or waits for an available connection handle.
    If the connector's MaxNumberOfConnections configuration property evaluates to 1, the Vision business object handler shares a connection with event processing.
    SAP releases the dialog process after it completes processing and sends a return code.
    The connector releases the connection handle after it receives the return code from SAP.
    Setting the number of available connections
    Use the MaxNumberOfConnections configuration property to specify the maximum number of connection handles available. The number of connections cannot exceed the number of dialog processes.
    SAP locks the dialog process while processing an interaction, releasing it only when the interaction completes. Therefore, multiple concurrent requests lock an equal number of dialog processes until processing finishes.
    Important:
    Before setting a value for MaxNumberOfConnections, contact your SAP BASIS administrator to determine an appropriate value to maximize throughput without negatively affecting performance on the application server.
    Support for multiple connections
    By default the connector supports multiple-threads.
    <b>
    REWARD IF USEFULL</b>

Maybe you are looking for