I've actually changed the IsolationLevel to ReadCommitted, even tried ReadUnCommitted but the same problems still occur.
On Sep 21, 4:29 pm, Jason Meckley <[email protected]> wrote: > I wouldn't recommend disabling transactions. you can set the transaction > level in the RSB configuration. the default is IsolationLevel.Serializable. > There are a number of reasons why you are receiving dead locks. I would even > say is common when devs first start using the Serializable isolation level. > How you resolve this becomes an art. typically querying less data & issuing > fewer queries helps alleviate the problem. > > For example I used to get errors and warnings when lazy loading data within > a consumer. eager loading the data and using NH Futures to reduce the number > of remote DB calls resolved the issue. The next step is query a projection > of the required data. I haven't needed this, but would be required if the > entities were very large and only a subset of information was used in the > actual consumer. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
