connection pooling

[Greg Matthews]

dear all,   do requests for EJB UserTransaction objects or db connections accessible through a Context get handled in a *queued* manner under orion?, or does it just notifyAll() the worker threads and let them fend for themselves?   we're currently doing our own database connection pooling, about to switch over to UserTransaction objects + using orion's db connection pooling.   i had to modify the database toolkit we are using since it implemented a "free for all" approach to handing out newly freed up connections to worker threads, i.e. notifyAll(), which didn't guarantee that threads received a db connection in the order in which they were requested.   greg