I will try it tomorrow thanks.
A workaround at the moment ist to switch the current database.
Am 28.12.2010 21:05, schrieb Diego Mijelshon:
Have you tried disabling connection pooling?
Diego
On Tue, Dec 28, 2010 at 13:39, Armin Landscheidt
<[email protected] <mailto:[email protected]>> wrote:
Is it possible to force NHibernate logging out from the server?
If I do something like
using(var session = sessionFactory.OpenSession()){
using(var transaction = session.BeginTransaction()){
//fire some queries
transaction.Commit();
}
}
using(var session = sessionFactory.OpenSession()){
using(var transaction = session.BeginTransaction()){
//fire some other queries
transaction.Commit();
}
}
NHibernate does not close the connection after the first
transaction.Commit(). It closes the connection on the second
session.BeginTransaction()
How can I force a logout after using the first session?
--
You received this message because you are subscribed to the Google
Groups "nhusers" group.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:nhusers%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
--
You received this message because you are subscribed to the Google
Groups "nhusers" 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/nhusers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en.
