Creating a new context instance should work. Querying with a new context should query the database (unless you have turned on the Level 2 cache). The exception indicates that somehow the same underlying connection is being used from different threads to start a transaction. It seems that the same context is being used from multiple threads.
Can you send me some sample code that demonstrates your scenario?
Alternatively you can turn off the OpenAccess connection pool and use the ADO.NET connection pooling by setting the 'BackendConfiguration.ConnectionPool.Pool' property value to 'ADO'.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map